Hi people!
With "GNU Make 3.81rc2" and "GNU sed version 4.1.4" from Debian testing, I get an error with the following entries in l4/tool/gcc-wrap/Makefile:
$(SYSTOOLS): %.$(SYSTEM): %.in .general.d @$(GEN_MESSAGE) $(VERBOSE)sed '\ s,@system@,$(SYSTEM),g;\ s,@ar@,$(AR),g;\ s,@nm@,$(NM),g;\ s,@ranlib@,$(RANLIB),g;\ s,@cc@,$(CC_$(DEFAULT_ARCH)),g;\ s,@cxx@,$(CXX_$(DEFAULT_ARCH)),g;\ s,@l4dir@,$(absfilename $(L4DIR)),g;\ s,@dropsdir@,$(DROPS_STDDIR),g;\ s,@compilerincdir@,$(GCCDIR_$(DEFAULT_ARCH))/include,g;\ s,@libgcc@,$(GCCLIB_$(DEFAULT_ARCH)),g;\ s,@libgcc_eh@,$(GCCLIB_EH_$(DEFAULT_ARCH)),g;\ s,@default_system@,$(DEFAULT_SYSTEM),g;\ s,@default_arch@,$(DEFAULT_ARCH),g;\ s,@default_cpu@,$(call PROCESS_SYSTEM, 's/[^-_]*_([^-]*).*/\1/p'),g;\ s,@default_l4api@,$(call PROCESS_SYSTEM, 's/.*-(.*)/\1/p'),g;\ ' $< > $@.new $(VERBOSE)chmod 755 $@.new $(VERBOSE)mv $@.new $@
For some reason (probably "make" or "sed" is broken?), the multi-line sed command is not recognized properly. I get the following error:
... Generating drops-ar.Linux sed '\ s,@system@,Linux,g;\ s,@ar@,ar,g;\ s,@nm@,nm,g;\ s,@ranlib@,ranlib,g;\ s,@cc@,,g;\ s,@cxx@,,g;\ s,@l4dir@,,g;\
s,@dropsdir@,/home/osk/tmp/dropsupdate-060619-163030/drops-060619/build,g;\ s,@compilerincdir@,/include,g;\ s,@libgcc@,,g;\ s,@libgcc_eh@,,g;\ s,@default_system@,x86_586,g;\ s,@default_arch@,x86,g;\ s,@default_cpu@,586,g;\ s,@default_l4api@,,g;\ ' drops-ar.in > drops-ar.Linux.new sed: -e expression #1, char 359: unterminated address regex make: *** [drops-ar.Linux] Error 1
When I try it "by hand", I get the same error. Nevertheless it works, when I put all the sed command into a single line.
Probably you already have a better solution to that?
Best regards Oskar.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi Oskar,
Oskar Senft wrote on 19.06.2006 23:22 this:
For some reason (probably "make" or "sed" is broken?), the multi-line sed command is not recognized properly. I get the following error:
Correct, this is a sed incompatibility bug. The fix is to split the multiline command into single -e statements:
... Generating drops-ar.Linux sed '\ s,@system@,Linux,g;\ s,@ar@,ar,g;\ s,@nm@,nm,g;\ s,@ranlib@,ranlib,g;\ s,@cc@,,g;\ s,@cxx@,,g;\ s,@l4dir@,,g;\
s,@dropsdir@,/home/osk/tmp/dropsupdate-060619-163030/drops-060619/build,g;\ s,@compilerincdir@,/include,g;\ s,@libgcc@,,g;\ s,@libgcc_eh@,,g;\ s,@default_system@,x86_586,g;\ s,@default_arch@,x86,g;\ s,@default_cpu@,586,g;\ s,@default_l4api@,,g;\ ' drops-ar.in > drops-ar.Linux.new
to:
sed -e 's,@system@,Linux,g' \ -e 's,@ar@,ar,g' \ -e ',@nm@,nm,g' \ ... (and so on)
Probably you already have a better solution to that?
Fix in CVS will follow shortly!
Thanks, Ron. - -- Mit freundlichen Gruessen / with regards ra3 @ inf.tu-dresden.de http://os.inf.tu-dresden.de/~ra3/
Hi Ronald!
Probably you already have a better solution to that?
Fix in CVS will follow shortly!
Great, thank you!
Regards Oskar.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi,
Oskar Senft wrote on 21.06.2006 13:51 this:
Great, thank you!
I took a closer look at gcc-wrap asking myself why that sed issue had not been fixed yet. The answer is pretty simple: gcc-wrap is only used by the stdlibc++ package, which requires oskit. The support for the latter had been dropped a while ago making stdlibc++ obsolete as well and therefore also eliminating the need to maintain gcc-wrap.
Simplest solution is to remove the gcc-wrap subdir from the l4/tool directory.
HTH, Ron.
PS: If you require C++ support, please use uclibc and uclibc++ packages. - -- Mit freundlichen Gruessen / with regards ra3 @ inf.tu-dresden.de http://os.inf.tu-dresden.de/~ra3/
l4-hackers@os.inf.tu-dresden.de
-
Oskar Senft -
Ronald Aigner