public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/103866] AM_PROG_LIBTOOL not compatible with GCC_NO_EXECUTABLES
Date: Thu, 30 Dec 2021 11:20:59 +0000	[thread overview]
Message-ID: <bug-103866-4-bo0djKzrxo@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103866-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103866

--- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> ---
libstdc++-v3/configure.ac has:

# Libtool setup.
if test "x${with_newlib}" != "xyes" && test "x${with_avrlibc}" != "xyes"; then
  AC_LIBTOOL_DLOPEN
fi
AM_PROG_LIBTOOL
ACX_LT_HOST_FLAGS
AC_SUBST(enable_shared)
AC_SUBST(enable_static)


Since I actively avoid understanding what libtool actually does I have no idea
if/when we can make that AM_PROG_LIBTOOL conditional. Libstdc++ doesn't use
dlopen, so maybe we can just add --disable-dlopen. Or maybe --disable-shared
should imply --disable-dlopen.

  reply	other threads:[~2021-12-30 11:20 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-30 11:04 [Bug libstdc++/103866] New: " redi at gcc dot gnu.org
2021-12-30 11:20 ` redi at gcc dot gnu.org [this message]
2021-12-30 11:34 ` [Bug libstdc++/103866] " pinskia at gcc dot gnu.org
2021-12-30 12:01 ` redi at gcc dot gnu.org
2021-12-30 12:06 ` redi at gcc dot gnu.org
2021-12-30 12:11 ` redi at gcc dot gnu.org
2021-12-30 18:08 ` pixel@nobis-crew.org
2021-12-30 19:05 ` redi at gcc dot gnu.org
2021-12-30 21:01 ` pixel@nobis-crew.org
2021-12-31 18:58 ` redi at gcc dot gnu.org
2021-12-31 19:01 ` redi at gcc dot gnu.org
2022-01-06 21:16 ` redi at gcc dot gnu.org
2022-01-10 12:18 ` cvs-commit at gcc dot gnu.org
2022-01-10 12:24 ` redi at gcc dot gnu.org
2022-01-10 18:33 ` pixel@nobis-crew.org

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=bug-103866-4-bo0djKzrxo@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).