mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Szabolcs Nagy <nsz@port70.net>
To: musl@lists.openwall.com
Subject: Re: Support for multiarch/multilib
Date: Tue, 17 Nov 2015 16:06:53 +0100	[thread overview]
Message-ID: <20151117150650.GE18372@port70.net> (raw)
In-Reply-To: <CABBv4TZW_-tWXfDi1nqvPWZfxhoYWdrzEDr37-5eNg33hEZjeQ@mail.gmail.com>

* Petr Hosek <phosek@chromium.org> [2015-11-17 06:15:20 +0000]:
> We're using musl in multiarch/multilib setup (i386/x86-64) and it works
> fine, except for header duplication. Given two architectures,
> i386-linux-gnu and x86_64-linux-gnu, I'd like to install the shared headers
> into /usr/include, and install bits (what is normally in include/bits) for
> each architecture into the respective subfolders
> /usr/include/i386-linux-gnu/bits and /usr/x86_64-linux-gnu.
> 

multiarch should make it possible to support multiple abis
on the same host.. but currently that's not the case, there
are headers shared across abis.

$ARCH-linux-gnu is certainly not the right name for musl as
it conflicts with glibc.

> I can obviously achieve by copying/moving files after install, but I'd
> prefer to have the support for that scenario directly in the Makefile.
> Would you accept such patch?
> 
> There are two possible ways to implements this I can think of: (1) add a
> separate targets such as install-arch-headers and install-generic-headers,
> or (2) define additional Makefile variable such as includebits which would
> be set to $(includedir)/bits by default but could be overridden when
> invoking make. Do you have strong preference for either of these solutions?

i personally prefer something with make variables so
make install does the right thing if i set my vars
properly. (i assume you need the same for /usr/lib.)

but i'm not sure if trying to support a particular
flavour of multi* is a good idea at this point.


  reply	other threads:[~2015-11-17 15:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-17  6:15 Petr Hosek
2015-11-17 15:06 ` Szabolcs Nagy [this message]
2015-11-17 15:36   ` 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=20151117150650.GE18372@port70.net \
    --to=nsz@port70.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).