public inbox for libstdc++-cvs@sourceware.org
help / color / mirror / Atom feed
From: Alexandre Oliva <aoliva@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org, libstdc++-cvs@gcc.gnu.org
Subject: [gcc r14-10015] [libstdc++] define zoneinfo_dir_override on vxworks
Date: Thu, 18 Apr 2024 11:14:40 +0000 (GMT)	[thread overview]
Message-ID: <20240418111440.D1CC63858D37@sourceware.org> (raw)

https://gcc.gnu.org/g:da3504ae4d1e6872585b1107a4932efd3824e943

commit r14-10015-gda3504ae4d1e6872585b1107a4932efd3824e943
Author: Alexandre Oliva <oliva@adacore.com>
Date:   Thu Apr 18 08:00:52 2024 -0300

    [libstdc++] define zoneinfo_dir_override on vxworks
    
    VxWorks fails to load kernel-mode modules with weak undefined symbols.
    In RTP mode modules, that undergo final linking, weak undefined
    symbols are not a problem.
    
    This patch adds kernel-mode VxWorks multilibs to the set of targets
    that don't support weak undefined symbols without special flags, in
    which tzdb's zoneinfo_dir_override is given a weak definition.
    
    
    for  libstdc++-v3/ChangeLog
    
            * src/c++20/tzdb.cc (__gnu_cxx::zoneinfo_dir_override): Define
            on VxWorks non-RTP.

Diff:
---
 libstdc++-v3/src/c++20/tzdb.cc | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/libstdc++-v3/src/c++20/tzdb.cc b/libstdc++-v3/src/c++20/tzdb.cc
index 890a4c53e2d..639d1c440ba 100644
--- a/libstdc++-v3/src/c++20/tzdb.cc
+++ b/libstdc++-v3/src/c++20/tzdb.cc
@@ -70,8 +70,9 @@ namespace __gnu_cxx
 #else
   [[gnu::weak]] const char* zoneinfo_dir_override();
 
-#if defined(__APPLE__) || defined(__hpux__)
-  // Need a weak definition for Mach-O.
+#if defined(__APPLE__) || defined(__hpux__) \
+  || (defined(__VXWORKS__) && !defined(__RTP__))
+  // Need a weak definition for Mach-O et al.
   [[gnu::weak]] const char* zoneinfo_dir_override()
   {
 #ifdef _GLIBCXX_ZONEINFO_DIR

                 reply	other threads:[~2024-04-18 11:14 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20240418111440.D1CC63858D37@sourceware.org \
    --to=aoliva@gcc.gnu.org \
    --cc=gcc-cvs@gcc.gnu.org \
    --cc=libstdc++-cvs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).