From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: Re: Co-existing i386 and x86_64 libraries?
Date: Fri, 2 May 2014 12:13:55 -0400 [thread overview]
Message-ID: <20140502161355.GV26358@brightrain.aerifal.cx> (raw)
In-Reply-To: <536377AE.1050602@f-prot.com>
On Fri, May 02, 2014 at 10:47:10AM +0000, Oliver Schneider wrote:
> Hi Rich, all,
>
> On 2014-04-30 03:00, Rich Felker wrote:
> > You need separate libdirs for each arch. This is fundamental; it's not
> > specific to musl.
> But the include dirs can be shared, or are the headers being "primed"
> somehow, during the build?
I was talking about things needed for runtime. For development you
even need separate bin dirs (think pkg-conf, getconf, etc.) for the
configure scripts to work right. At present musl's headers can be
shared between archs except for the bits subdir (so you can make a
custom install where bits isn't in the shared include dir, and instead
add it to gcc's default include path) but this isn't a permanent
guarantee that it will work that way. You're best off having all
development-related files be separate per-arch.
Rich
prev parent reply other threads:[~2014-05-02 16:13 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
2014-05-02 10:47 ` Oliver Schneider
2014-05-02 16:13 ` 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=20140502161355.GV26358@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).