public inbox for libstdc++-cvs@sourceware.org
help / color / mirror / Atom feed
From: Jonathan Wakely <redi@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org, libstdc++-cvs@gcc.gnu.org
Subject: [gcc r11-6073] libstdc++: Disabling AC_LIBTOOL_DLOPEN check if building with avr-libc
Date: Tue, 15 Dec 2020 11:45:55 +0000 (GMT)	[thread overview]
Message-ID: <20201215114555.2996E384A07D@sourceware.org> (raw)

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

commit r11-6073-ga929b39aa32a6bc65158bd8e32ce96bc1c906065
Author: Vladimir Vishnevsky <vv.os.swe@gmail.com>
Date:   Tue Dec 15 11:40:07 2020 +0000

    libstdc++: Disabling AC_LIBTOOL_DLOPEN check if building with avr-libc
    
    The AC_LIBTOOL_DLOPEN checks were previously disabled for newlib targets.
    The patch applies similar logic to avr-libc based builds.
    
    libstdc++-v3/ChangeLog:
    
            * configure.ac: Skip AC_LIBTOOL_DLOPEN check if avr-libc is used.
            * configure: Regenerate.

Diff:
---
 libstdc++-v3/configure    | 2 +-
 libstdc++-v3/configure.ac | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/libstdc++-v3/configure b/libstdc++-v3/configure
index d7a4826b8e2..e6f30a1a706 100755
--- a/libstdc++-v3/configure
+++ b/libstdc++-v3/configure
@@ -5899,7 +5899,7 @@ $as_echo "$as_me: OS config directory is $os_include_dir" >&6;}
 
 
 # Libtool setup.
-if test "x${with_newlib}" != "xyes"; then
+if test "x${with_newlib}" != "xyes" && test "x${with_avrlibc}" != "xyes"; then
   enable_dlopen=yes
 
 
diff --git a/libstdc++-v3/configure.ac b/libstdc++-v3/configure.ac
index cbfdf4c6bad..771814110a1 100644
--- a/libstdc++-v3/configure.ac
+++ b/libstdc++-v3/configure.ac
@@ -90,7 +90,7 @@ AC_SYS_LARGEFILE
 GLIBCXX_CONFIGURE
 
 # Libtool setup.
-if test "x${with_newlib}" != "xyes"; then
+if test "x${with_newlib}" != "xyes" && test "x${with_avrlibc}" != "xyes"; then
   AC_LIBTOOL_DLOPEN
 fi
 AM_PROG_LIBTOOL


                 reply	other threads:[~2020-12-15 11:45 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=20201215114555.2996E384A07D@sourceware.org \
    --to=redi@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).