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] New: AM_PROG_LIBTOOL not compatible with GCC_NO_EXECUTABLES
Date: Thu, 30 Dec 2021 11:04:00 +0000 [thread overview]
Message-ID: <bug-103866-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103866
Bug ID: 103866
Summary: AM_PROG_LIBTOOL not compatible with GCC_NO_EXECUTABLES
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Keywords: build
Severity: normal
Priority: P3
Component: libstdc++
Assignee: unassigned at gcc dot gnu.org
Reporter: redi at gcc dot gnu.org
Target Milestone: ---
The libtool setup in the top-level libtool.m4 has this snippet in
LT_SYS_DLOPEN_SELF:
*)
AC_CHECK_FUNC([shl_load],
[lt_cv_dlopen="shl_load"],
[AC_CHECK_LIB([dld], [shl_load],
[lt_cv_dlopen="shl_load" lt_cv_dlopen_libs="-ldld"],
[AC_CHECK_FUNC([dlopen],
[lt_cv_dlopen="dlopen"],
[AC_CHECK_LIB([dl], [dlopen],
[lt_cv_dlopen="dlopen" lt_cv_dlopen_libs="-ldl"],
[AC_CHECK_LIB([svld], [dlopen],
[lt_cv_dlopen="dlopen" lt_cv_dlopen_libs="-lsvld"],
[AC_CHECK_LIB([dld], [dld_link],
[lt_cv_dlopen="dld_link" lt_cv_dlopen_libs="-ldld"])
])
])
])
])
])
;;
This can fail if GCC_NO_EXECUTABLES has been used, e.g. for a mips-none-elf
cross-compiler (see Bug 100057 comment 33, but ignore all the other comments
there).
It looks like --disable-dlopen will avoid that snippet, but should that be
necessary if --disable-shared has been used? If it can't depend on
--disable-shared, is there some other flag we can use to infer that the user
doesn't want/need those checks for a bare metal build?
next reply other threads:[~2021-12-30 11:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-30 11:04 redi at gcc dot gnu.org [this message]
2021-12-30 11:20 ` [Bug libstdc++/103866] " redi at gcc dot gnu.org
2021-12-30 11:34 ` 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@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).