[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Wed, 27 May 2015 00:23:26 +0000
From: Lucas Simões <simoes.lucas.silva@...il.com>
To: Justin Cormack <justin@...cialbusservice.com>, musl@...ts.openwall.com
Cc: Paulo Castro <p.oliveira.castro@...il.com>
Subject: Re: Using Musl with LLVM/Clang
Thank you for the quick response guys!
That's really sad, I was truly hoping to find a way to use musl out of the
box with Clang (on my Arch)
Guess I'll just have to check the toolchains on this ELLCC project
Em ter, 26 de mai de 2015 às 04:48, Justin Cormack <
justin@...cialbusservice.com> escreveu:
> On 26 May 2015 at 02:53, Shiz <hi@...z.me> wrote:
> >> On 26 May 2015, at 03:37, Rich Felker <dalias@...c.org> wrote:
> >>
> >> The main reason we need a specfile for gcc rather than just -nostdinc
> >> and -nostdlib is that the latter does not suppress search of the
> >> default library paths, just the libraries, i.e. it removes the -l's
> >> but not the -L's. If you can find a way to remove the default -L's for
> >> clang then it should be easy.
> >>
> >> Rich
> >
> > Sadly, after looking at the clang driver source[1], there seems to be no
> > such option: it unconditionally adds the library paths. Unless there’s
> > some way to influence ToolChain.getFilePaths(), it doesn’t seem like it
> > can be done without modifying the clang source code.
>
> You can use clang with --sysroot, if everything is under the same root
> path.
>
> In theory if clang had support you could just use -target or just
> rename the compiler and it would just compile for Musl, according to
> the docs http://clang.llvm.org/docs/CrossCompilation.html but I am
> guessing that needs some upstream support, would be nice to add.
>
> Justin
>
Content of type "text/html" skipped
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
