[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20130415044913.GU20323@brightrain.aerifal.cx>
Date: Mon, 15 Apr 2013 00:49:13 -0400
From: Rich Felker <dalias@...ifal.cx>
To: musl@...ts.openwall.com
Subject: Re: Request for ideas on arch-specific musl-gcc specfile
additions
On Mon, Apr 15, 2013 at 12:31:34AM -0400, Zvi Gilboa wrote:
> 2) add arch-specific variables in the relevant places and set them
> from outside, possibly by executing musl-gcc.specs.sh from within an
> arch-specific shell script. For instance:
>
> *cpp_options:
> $ARCH_SPECIFIC_CFLAGS -nostdinc -isystem $incdir %(old_cpp_options)
Hmm, I had forgotten it was a shell script and not just a sed script
or something doing the replacements. So we could just put something
like:
$(case "$ARCH" in
mips*) echo "mips stuff here" ;;
powerpc*) echo "ppc stuff here" ;;
easc)
Does that work? Might have to add $ARCH to the args to the script, but
otherwise it seems ok.
Rich
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.
