mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: Re: Compile error with --target=i386
Date: Tue, 16 Feb 2016 14:49:22 -0500	[thread overview]
Message-ID: <20160216194922.GW9349@brightrain.aerifal.cx> (raw)
In-Reply-To: <alpine.LNX.2.20.1602162204050.32308@monopod.intra.ispras.ru>

On Tue, Feb 16, 2016 at 10:12:39PM +0300, Alexander Monakov wrote:
> On Tue, 16 Feb 2016, Rich Felker wrote:
> > In the case of musl, CFLAGS is always passed even at the linking
> > stage; I think the problem is just at configure time, where the
> > user-provided CFLAGS are not used in all the configure-time tests.
> > Maybe this is contrary to the normal UI for configure scripts and
> > should be changed?
> 
> I don't have a strong opinion whether it's contrary or not; my weak opinion is
> that it is contrary, indeed; but nevertheless I stand by my original point
> that -m32 is better when specified in $CC, generally speaking.
> 
> If you look at the opening post, you'll see that -m32 does not appear on the
> quoted command line.  If Petr did it as he has shown, he forgot to 'export'
> the variable; this would explain the failure (otherwise as you say it should
> have worked).
> 
> Also please note that $CC should have -m32 (and any other ABI tweaks) for
> musl-gcc to work as intended.

Yes, I agree with all this. I was just wondering if we should be
including that invoking user's CFLAGS when running tests in configure.
Right now I think it's inconsistent whether we do or not.

Rich


      reply	other threads:[~2016-02-16 19:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-16  9:18 Petr Petrov
2016-02-16 10:10 ` Alexander Monakov
2016-02-16 10:31   ` Petr Petrov
2016-02-16 10:39     ` Alexander Monakov
2016-02-16 16:54       ` Rich Felker
2016-02-16 19:12         ` Alexander Monakov
2016-02-16 19:49           ` Rich Felker [this message]

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=20160216194922.GW9349@brightrain.aerifal.cx \
    --to=dalias@libc.org \
    --cc=musl@lists.openwall.com \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

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 NNTP newsgroup(s).