From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: Re: Co-existing i386 and x86_64 libraries?
Date: Tue, 29 Apr 2014 23:00:53 -0400 [thread overview]
Message-ID: <20140430030053.GF26358@brightrain.aerifal.cx> (raw)
In-Reply-To: <53602595.5080605@f-prot.com>
On Tue, Apr 29, 2014 at 10:20:05PM +0000, Oliver Schneider wrote:
> Hi,
>
> short of setting different prefixes for each respective build, what
> could I do to have two coexisting musl-libc libraries, one for -m64 and
> one for -m32 builds on IA-32?
>
> The compiler (gcc in my case) supports the targets and the following
> does the job on a 64-bit host:
>
> ../configure --enable-debug --target=i386 CFLAGS=-m32 CC="ccache gcc"
As a general practice it's probably better to put the -m32 as part of
$CC, but this should work too for musl.
> However, I have yet to find a solution to having both builds live
> peacefully together under the same "prefix" and the specs file used by
> the GCC wrapper choosing the proper architecture.
You need separate libdirs for each arch. This is fundamental; it's not
specific to musl.
> Any ideas how to accomplish this?
>
> Looking at the Makefile the way it stands, I reckon this is virtually
> impossible. There are hardcoded library names used after including
> config.mak, so overriding something like that inside config.mak is hopeless.
Renaming the libraries is definitely not a viable solution. The names
are all fixed because they have to be.
> Thanks,
>
> // Oliver
>
> PS: on another note, the Makefile appears to use GNU-make-isms, wouldn't
> it make sense to name it GNUmakefile in order to avoid it being picked
> up by other make flavors? Or am I missing something here?
We have some ppl involved with the project who are allergic to seeing
the letters G, N, and U together anyhere...
Rich
next prev parent reply other threads:[~2014-04-30 3:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-29 22:20 Oliver Schneider
2014-04-30 3:00 ` Rich Felker [this message]
2014-05-02 10:47 ` Oliver Schneider
2014-05-02 16:13 ` Rich Felker
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=20140430030053.GF26358@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).