From: Andy Lutomirski <luto@amacapital.net>
To: musl@lists.openwall.com
Subject: Re: musl-gcc -m32 is broken
Date: Thu, 27 Aug 2015 12:58:21 -0700 [thread overview]
Message-ID: <55DF6BDD.6000104@amacapital.net> (raw)
In-Reply-To: <20150827014407.GT32742@brightrain.aerifal.cx>
On 08/26/2015 06:44 PM, Rich Felker wrote:
> On Wed, Aug 26, 2015 at 03:16:22PM -0700, Andy Lutomirski wrote:
>> Adding %{m16|m32:-m elf_i386} to the *link spec in musl-gcc.specs
>> fixes at least the obvious failure for me.
>
> Can you clarify? musl-gcc's target is coupled to the target arch that
> the corresponding musl libc was built for. Switching targets with -m32
> and similar options is not going to get you correspondingly switched
> libraries. Or am I misunderstanding what you're trying to do?
I build for an i386 target on an x86_64 Fedora system using CFLAGS=-m32.
It built successfully and even seems to work, but musl-gcc ends up
omitting -m32 in the link stage, so it tries to pick up the wrong
libraries and fails to link.
ISTM either musl-gcc should accept and honor -m32 (and work!) or
musl-gcc should hardcode the target architecture (i.e. musl-gcc should
target i386 even without -m32).
--Andy
next prev parent reply other threads:[~2015-08-27 19:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-26 22:16 Andy Lutomirski
2015-08-27 1:44 ` Rich Felker
2015-08-27 19:58 ` Andy Lutomirski [this message]
2015-08-27 20:09 ` Rich Felker
2015-08-28 0:49 ` Andy Lutomirski
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=55DF6BDD.6000104@amacapital.net \
--to=luto@amacapital.net \
--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).