This is the mail archive of the
cygwin-apps@cygwin.com
mailing list for the Cygwin project.
Re: mknetrel issues
On Sun, Jun 15, 2003 at 02:05:42AM +0100, Max Bowsher wrote:
>Christopher Faylor wrote:
>> On Sat, Jun 14, 2003 at 10:43:44PM +0100, Max Bowsher wrote:
>>> I've been trying to use mknetrel (natively on Cygwin) to build myself a
>>> gcc-3.3.
>>>
>>> I ran into a variety of small issues:
>...
>>> 2) Use of $(BASE_FLAGS_TO_PASS) and $(EXTRA_HOST_FLAGS)
>>> I'm guessing these are intended to be make variables, but the quotes are
>>> getting lost prematurely, and they are being interpreted by bash as $()
>>> command interpolation.
>>
>> The parentheses should be dropped. I never use these variables, so that's
>> why I never noticed the makefile-like usage.
>
>There is still something wrong with the quoting here:
>
>Making net release for gcc-3.3-max, pid 2748
>echo makeflags: GCJ=i686-pc-cygwin-gcjGCJH=i686-pc-cygwin-gcjh
>"$EXTRABUILDARGS" "CFLAGS=$opt" "CXXFLAGS=$opt"
>"TARGET_FLAGS_TO_PASS=$EXTRABUILDARGS"' $BASE_FLAGS_TO_PASS
>$EXTRA_TARGET_FLAGS' "FLAGS_TO_PASS=$EXTRABUILDARGS"' $BASE_FLAGS_TO_PASS
>$EXTRA_HOST_FLAGS'
>make[1]: Entering directory `/netrel/build/gcc-3.3-max/libiberty'
>make[1]: *** No rule to make target `ASE_FLAGS_TO_PASS'. Stop.
>make[1]: Leaving directory `/netrel/build/gcc-3.3-max/libiberty'
>make: *** [all-libiberty] Error 2
>
>Since I don't understand what's supposed to happen, I'm going to avoid the
>issue by removing all the needdevoflags stuff.
Yeah, that's the ticket. Avoid that pesky "understanding" and implement
a local hack.
cgf