public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Olivier Hainque <hainque@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r13-2979] Arrange to --disable-shared by default for VxWorks Date: Fri, 30 Sep 2022 10:43:21 +0000 (GMT) [thread overview] Message-ID: <20220930104321.884B93858CDB@sourceware.org> (raw) https://gcc.gnu.org/g:9b8ffbb8a0cadd68bf7887c5655a29ec04060111 commit r13-2979-g9b8ffbb8a0cadd68bf7887c5655a29ec04060111 Author: Olivier Hainque <hainque@adacore.com> Date: Fri Dec 3 17:48:18 2021 +0000 Arrange to --disable-shared by default for VxWorks This change makes sure that shared libraries for VxWorks are only built on explicit request, when configured with --enable-shared. As the support to build shared libs gets in very incrementally, this provides us with a robust way to guard the relevant pieces and reduce the risks of accidentally breaking a platform not yet ready for it. 2022-09-30 Olivier Hainque <hainque@adacore.com> * configure.ac (*vxworks*): If enable_shared is not set, set to "no" and add --disable-shared to target and host_configargs. * configure: Regenerate. Diff: --- configure | 11 +++++++++++ configure.ac | 11 +++++++++++ 2 files changed, 22 insertions(+) diff --git a/configure b/configure index e7604dc6ff0..d9aa84c6138 100755 --- a/configure +++ b/configure @@ -10263,6 +10263,17 @@ case "${target}" in mep*) FLAGS_FOR_TARGET="$FLAGS_FOR_TARGET -mlibrary" ;; + # The VxWorks support for shared libraries is getting in + # incrementally. Make sure it doesn't get activated implicitly: + *vxworks*) + if test "${enable_shared-unset}" = unset ; then + enable_shared=no + # So the build of libraries knows ... + target_configargs="${target_configargs} --disable-shared" + # So gcc knows ... + host_configargs="${host_configargs} --disable-shared" + fi + ;; esac # Makefile fragments. diff --git a/configure.ac b/configure.ac index 3cfd9b41fca..2cff32e300e 100644 --- a/configure.ac +++ b/configure.ac @@ -3440,6 +3440,17 @@ case "${target}" in mep*) FLAGS_FOR_TARGET="$FLAGS_FOR_TARGET -mlibrary" ;; + # The VxWorks support for shared libraries is getting in + # incrementally. Make sure it doesn't get activated implicitly: + *vxworks*) + if test "${enable_shared-unset}" = unset ; then + enable_shared=no + # So the build of libraries knows ... + target_configargs="${target_configargs} --disable-shared" + # So gcc knows ... + host_configargs="${host_configargs} --disable-shared" + fi + ;; esac # Makefile fragments.
reply other threads:[~2022-09-30 10:43 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=20220930104321.884B93858CDB@sourceware.org \ --to=hainque@gcc.gnu.org \ --cc=gcc-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: linkBe 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).