From: Shiz <hi@shiz.me>
To: musl@lists.openwall.com
Subject: Re: [PATCH 1/2] add musl-clang, a wrapper for system clang installs
Date: Fri, 29 May 2015 19:35:18 +0200 [thread overview]
Message-ID: <0453E380-A35F-4B0E-9D9B-AC03BEDEDB55@shiz.me> (raw)
In-Reply-To: <20150529171335.GL17573@brightrain.aerifal.cx>
[-- Attachment #1: Type: text/plain, Size: 795 bytes --]
> On 29 May 2015, at 19:13, Rich Felker <dalias@libc.org> wrote:
>
> On Fri, May 29, 2015 at 07:11:18PM +0200, Shiz wrote:
>
> What if you add a bogus prefix to all -l and -L options provided by
> the user? Then the wrapper can remove any -l or -L options without the
> prefix, then remove the prefix from the ones that remain.
>
> Rich
This isn’t a bad idea, but it modifies the behaviour in the same way
musl-clang does, except the other way around: it will not have clang
invoke ld if only -l is supplied by the user and no object paths are,
which is what normally should happen.
I’m pretty sure I’ve devised a fix that doesn’t modify behaviour and
makes ld.musl-clang a bit cleaner as a side-effect - I’ll post an updated
patch after a bit of testing.
-S
[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next prev parent reply other threads:[~2015-05-29 17:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-29 16:48 Shiz
2015-05-29 16:55 ` [PATCH 2/2] build: overhaul wrapper script system for multiple wrapper support Shiz
2015-06-01 3:18 ` Rich Felker
2015-06-01 14:15 ` Shiz
2015-06-01 14:47 ` Rich Felker
2015-06-01 15:39 ` Shiz
2015-06-01 16:03 ` Rich Felker
2015-05-29 17:03 ` [PATCH 1/2] add musl-clang, a wrapper for system clang installs Rich Felker
2015-05-29 17:11 ` Shiz
2015-05-29 17:13 ` Rich Felker
2015-05-29 17:35 ` Shiz [this message]
2015-05-29 18:43 ` [PATCH v2] " Shiz
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=0453E380-A35F-4B0E-9D9B-AC03BEDEDB55@shiz.me \
--to=hi@shiz.me \
--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).