From: Petr Hosek <phosek@chromium.org>
To: musl@lists.openwall.com
Subject: Re: Support for out-of-tree build
Date: Mon, 30 Nov 2015 01:29:06 +0000 [thread overview]
Message-ID: <CABBv4TabDxXBoN1TJTC--k4p9NXoXkAV9s+CrY7NYygXCh=QXg@mail.gmail.com> (raw)
In-Reply-To: <20151120222000.GA3818@brightrain.aerifal.cx>
[-- Attachment #1: Type: text/plain, Size: 1118 bytes --]
On Fri, Nov 20, 2015 at 2:21 PM Rich Felker <dalias@libc.org> wrote:
> I think this is failing to replicate the current behavior where a .sub
> file in src/*/$(ARCH)$(ASMSUBARCH) replaces the .s file in
> src/*/$(ARCH). In cases where both exist we'll end up with duplicate
> symbol errors linking libc.so and both present (with the wrong one
> likely getting used) in libc.a.
>
I tried various combinations of ARCH and SUBARCH and the behavior seems to
be the same as in current implementation. Do you have any examples?
> This problem will of course disappear when we get rid of .sub files,
> but that doesn't help unless we remove .sub files first.
>
> I suppose all that's needed for now is to add more EXCLUDE_OBJS using
> the same input but with:
>
> $(subst /$(ARCH)$(ASMSUBARCH)/,/$(ARCH)/,...
>
> instead of:
>
> $(subst /$(ARCH)$(ASMSUBARCH)/,/,...
>
> Does this sound right?
>
When I tried this change, I started getting duplicate symbol errors when
linking libc.so, but with the original it seems to be working fine (this
particular case was when ARCH=arm SUBARCH=hf ASMSUBARCH=ebhf).
[-- Attachment #2: Type: text/html, Size: 1600 bytes --]
next prev parent reply other threads:[~2015-11-30 1:29 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-06 23:40 Petr Hosek
2015-11-07 13:05 ` Szabolcs Nagy
2015-11-08 0:43 ` Rich Felker
2015-11-08 2:16 ` Szabolcs Nagy
2015-11-08 2:29 ` Rich Felker
2015-11-11 22:02 ` Petr Hosek
2015-11-11 23:08 ` Rich Felker
2015-11-12 0:01 ` Rich Felker
2015-11-12 0:28 ` Petr Hosek
2015-11-12 14:50 ` Szabolcs Nagy
2015-11-12 20:17 ` Petr Hosek
2015-11-12 20:30 ` Rich Felker
2015-11-12 21:10 ` Szabolcs Nagy
2015-11-12 21:52 ` Rich Felker
2015-11-12 22:35 ` Petr Hosek
2015-11-12 23:41 ` Rich Felker
2015-11-17 2:45 ` Petr Hosek
2015-11-17 6:05 ` Petr Hosek
2015-11-17 19:51 ` Szabolcs Nagy
2015-11-17 21:00 ` Rich Felker
2015-11-17 21:37 ` Petr Hosek
2015-11-17 22:01 ` Rich Felker
2015-11-17 22:15 ` Petr Hosek
2015-11-17 22:58 ` Rich Felker
2015-11-17 23:06 ` Szabolcs Nagy
2015-11-17 23:27 ` Rich Felker
2015-11-17 23:43 ` Rich Felker
2015-11-17 23:54 ` Petr Hosek
2015-11-18 0:19 ` Szabolcs Nagy
2015-11-18 0:19 ` Rich Felker
2015-11-18 20:19 ` Petr Hosek
2015-11-18 21:44 ` Rich Felker
2015-11-19 0:22 ` Petr Hosek
2015-11-20 4:09 ` Rich Felker
2015-11-20 5:02 ` Rich Felker
2015-11-20 10:51 ` Szabolcs Nagy
2015-11-30 1:25 ` Petr Hosek
2015-11-20 22:20 ` Rich Felker
2015-11-30 1:29 ` Petr Hosek [this message]
2015-11-30 1:35 ` Rich Felker
2015-11-30 2:49 ` Petr Hosek
2015-11-30 21:14 ` Rich Felker
2015-11-30 22:14 ` Rich Felker
2015-12-01 2:14 ` Petr Hosek
2015-12-09 0:39 ` Rich Felker
2015-12-10 1:39 ` Petr Hosek
2015-12-10 12:47 ` Szabolcs Nagy
2016-01-17 22:32 ` Rich Felker
2016-01-17 23:41 ` Szabolcs Nagy
2016-01-20 3:49 ` Rich Felker
2015-11-21 1:05 ` Szabolcs Nagy
2015-11-21 1:16 ` Szabolcs Nagy
2015-11-22 14:56 ` Szabolcs Nagy
2015-11-30 1:30 ` Petr Hosek
2015-11-30 12:01 ` Szabolcs Nagy
2015-11-30 22:22 ` 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='CABBv4TabDxXBoN1TJTC--k4p9NXoXkAV9s+CrY7NYygXCh=QXg@mail.gmail.com' \
--to=phosek@chromium.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).