Build error and Makefile.settings

[Mathieu Deschamps]

ok i've found were it bugs :

when it does this :
export LINUXBIOS_ASSEMBLER:=$(shell  touch dummy.s ; $(CC) -c -Wa,-v
dummy.s 2>&1; rm -f dummy.s dummy.o )

the answer should be when typing make echo :
LINUXBIOS_ASSEMBLER="Version de l'assembleur GNU 2.13.90.0.18
(i386-redhat-linux) utilisant la version BFD 2.13.90.0.18 20030206"
But the ' character makes a parse error even if the string is quoted ' '

I propose to patch this quckly:
export LINUXBIOS_ASSEMBLER:=$(shell  touch dummy.s ; $(CC) -c -Wa,-v
dummy.s 2>&1 | tr -s '''; rm -f dummy.s dummy.o )

mathieu

[ron minnich]

On 14 Apr 2004, Mathieu Deschamps wrote:
> the answer should be when typing make echo :
> LINUXBIOS_ASSEMBLER="Version de l'assembleur GNU 2.13.90.0.18
> (i386-redhat-linux) utilisant la version BFD 2.13.90.0.18 20030206"
> But the ' character makes a parse error even if the string is quoted ' '

ack! Now I bet we never thought of that one!
> I propose to patch this quckly:
> export LINUXBIOS_ASSEMBLER:=$(shell  touch dummy.s ; $(CC) -c -Wa,-v
> dummy.s 2>&1 | tr -s '''; rm -f dummy.s dummy.o )

sounds good.

ron

[ron minnich]

BTW Mathieu you've just discovered our first internationalization bug ... 
in a Makefile. Ow!

ron

[Mathieu Deschamps]

So kind of you to cheer me up Ron !!
because I found a new one, as it say "the least not the last" :'(
I've brought some V1 files dealing with CONFIG_VGA_CONSOLE=1 option into
V2 source tree (in bulldoze mode)

(oh, on the fly there's still no support of this kind on V2 for epia-m
?)

Rather than modified these file includes, I'd have liked to "change
makefile" concerning the -I option pass to gcc. And what a surprise dooh
: it's sed'ing for "install:" but in french it's "installés:"

##################################
SYNOPSIS :

#grep -n -e "GCC_INC" < Makefile

15: GCC_INC_DIR := $(shell $(CC) -print-search-dirs | sed -ne
"s/install: (.*)/\1include/gp")
16: CPPFLAGS := -I$(TOP)/src/include -I$(TOP)/src/arch/$(ARCH)/include
-I$(GCC_INC_DIR) $(CPUFLAGS)

#gcc -print-search-dirs | grep"/usr/lib/gcc-lib/i386-redhat-linux/3.2.2"
installés: /usr/lib/gcc-lib/i386-redhat-linux/3.2.2/
programmes:
=/usr/lib/gcc-lib/i386-redhat-linux/3.2.2/:/usr/lib/gcc-lib/i386-redhat-linux/3.2.2/:/usr/lib/gcc-lib/i386-redhat-linux/:/usr/lib/gcc/i386-redhat-linux/3.2.2/:/usr/lib/gcc/i386-redhat-linux/:/usr/lib/gcc-lib/i386-redhat-linux/3.2.2/../../../../i386-redhat-linux/bin/i386-redhat-linux/3.2.2/:/usr/lib/gcc-lib/i386-redhat-linux/3.2.2/../../../../i386-redhat-linux/bin/
libraries:
=/usr/lib/gcc-lib/i386-redhat-linux/3.2.2/:/usr/lib/gcc/i386-redhat-linux/3.2.2/:/usr/lib/gcc-lib/i386-redhat-linux/3.2.2/../../../../i386-redhat-linux/lib/i386-redhat-linux/3.2.2/:/usr/lib/gcc-lib/i386-redhat-linux/3.2.2/../../../../i386-redhat-linux/lib/:/usr/lib/gcc-lib/i386-redhat-linux/3.2.2/../../../i386-redhat-linux/3.2.2/:/usr/lib/gcc-lib/i386-redhat-linux/3.2.2/../../../:/lib/i386-redhat-linux/3.2.2/:/lib/:/usr/lib/i386-redhat-linux/3.2.2/:/usr/lib/
#################################

So it can find nothing for sure... Who is enough french language lover
to translate even thoses words every body understand in english ? 
Gosh !:[

Well, it looks like 'am gone for a super bug hunt :) Or if anybody could
spare me that sweating ?

Every trick is welcome !

mathieu

Le mer 14/04/2004 à 15:35, ron minnich a écrit :
> BTW Mathieu you've just discovered our first internationalization bug ... 
> in a Makefile. Ow!
>
> ron
>
> Linuxbios mailing list
> [e-mail]
> http://www.clustermatic.org/mailman/listinfo/linuxbios

[ron minnich]

On 14 Apr 2004, Mathieu Deschamps wrote:
> Rather than modified these file includes, I'd have liked to "change
> makefile" concerning the -I option pass to gcc. And what a surprise dooh
> : it's sed'ing for "install:" but in french it's "installés:"

In V2, I have tried to remove makefile rules that call shell scripts. 
These types of rules seem very simple at first but as you can see turn 
into a real nightmare over time.

Please take another look at how V2 works with an eye to removing these 
types of rules. I would rather not reintroduce them into v2. I notice a 
few have come back but I would very much like to limit their use.

thanks

ron