[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <61640.132.241.44.49.1348184386.squirrel@lavabit.com>
Date: Thu, 20 Sep 2012 19:39:46 -0400 (EDT)
From: idunham@...abit.com
To: musl@...ts.openwall.com
Subject: Re: musl-gcc question
> On Thu, Sep 20, 2012 at 05:53:45PM -0400, idunham@...abit.com wrote:
>> Rich, what would you think of changing from a hardcoded "gcc" to using
>> something along these lines:
>>
>> [ -z "$REALGCC" ] && REALGCC=gcc
>> $REALGCC <the current parameters>
>>
>> By setting REALGCC to rawgcc, Landley's toolchain could easily be used.
>> This would also help for using other cross-toolchains.
>> (note: I'm not particular about the variable, but $GCC might be a bad
>> choice: ISTR seeing one or two Makefiles that set that.)
>
> Have you tested if this works okay? If it's known to work, send a
> clean patch and I think it should be okay to apply.
That was off the top of my head, but it works.
Patch has been tested by building musl, then building my patched netbsd m4.
(I modified musl-gcc after installation to echo REALGCC).
Usage:
REALGCC=rawgcc make CC=musl-gcc
Isaac Dunham
View attachment "realgcc.diff" of type "text/x-patch" (703 bytes)
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.
