public inbox for newlib-cvs@sourceware.org help / color / mirror / Atom feed
From: Corinna Vinschen <corinna@sourceware.org> To: newlib-cvs@sourceware.org Subject: [newlib-cygwin] Fix libgloss being built for disabled multilibs Date: Sat, 02 Nov 2019 15:31:00 -0000 [thread overview] Message-ID: <20191102153154.122530.qmail@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=newlib-cygwin.git;h=fa14f445ba1fb360fb5c4957798bf788345b0ef2 commit fa14f445ba1fb360fb5c4957798bf788345b0ef2 Author: Jozef Lawrynowicz <jozef.l@mittosystems.com> Date: Wed Oct 30 14:35:21 2019 +0000 Fix libgloss being built for disabled multilibs Target libraries are considered to be built for GCC's "host", not GCC's "target". The "host" variable must be set by configure scripts using "config-ml.in" to determine multilib support, otherwise disabled multilibs (specified as a configure argument with --disable-<multilib>) will still be built for the subdirectories those configure scripts reside in. Diff: --- libgloss/configure | 1 + libgloss/configure.in | 1 + 2 files changed, 2 insertions(+) diff --git a/libgloss/configure b/libgloss/configure index eb116b5..6c592b1 100755 --- a/libgloss/configure +++ b/libgloss/configure @@ -3883,6 +3883,7 @@ cat >>$CONFIG_STATUS <<_ACEOF || ac_write_fail=1 AMDEP_TRUE="$AMDEP_TRUE" ac_aux_dir="$ac_aux_dir" srcdir=${srcdir} target=${target} +host=${host} with_multisubdir=${with_multisubdir} ac_configure_args="--enable-multilib ${ac_configure_args}" CONFIG_SHELL=${CONFIG_SHELL-/bin/sh} diff --git a/libgloss/configure.in b/libgloss/configure.in index a681f23..16f413f 100644 --- a/libgloss/configure.in +++ b/libgloss/configure.in @@ -229,6 +229,7 @@ AC_CONFIG_FILES([Makefile], fi], srcdir=${srcdir} target=${target} +host=${host} with_multisubdir=${with_multisubdir} ac_configure_args="--enable-multilib ${ac_configure_args}" CONFIG_SHELL=${CONFIG_SHELL-/bin/sh}
reply other threads:[~2019-11-02 15:31 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=20191102153154.122530.qmail@sourceware.org \ --to=corinna@sourceware.org \ --cc=newlib-cvs@sourceware.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).