mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: Re: [PATCH 1/2] add musl-clang, a wrapper for system clang installs
Date: Fri, 29 May 2015 13:13:35 -0400	[thread overview]
Message-ID: <20150529171335.GL17573@brightrain.aerifal.cx> (raw)
In-Reply-To: <AA1BBCEF-E785-48BD-AAE5-0CF19E580719@shiz.me>

On Fri, May 29, 2015 at 07:11:18PM +0200, Shiz wrote:
> > On 29 May 2015, at 19:03, Rich Felker <dalias@libc.org> wrote:
> > 
> > This logic looks wrong. For example, "-L foo" would result in input=1,
> > no? And same for any other options with arguments.
> > 
> > Rich
> 
> Hmm, I’m afraid you’re right. I’ll need to rethink this approach...
> I was slightly annoyed by it being needed in the first place, but there’s no
> other way from what I could see than these markers to figure out what comes
> from a user and what doesn’t, since clang re-orders -l and -L arguments.
> If they weren’t needed I could just move -lc to the linker wrapper...

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


  reply	other threads:[~2015-05-29 17:13 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 [this message]
2015-05-29 17:35       ` Shiz
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=20150529171335.GL17573@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).