From: Alan H. <al...@fa...> - 2006-01-30 14:57:29
|
That was the whole point of the PATH statement, so it picks up the newer sed. You'll need to put that back Franck and work out another fix for your updated compiler tools. Alan. On Mon, 2006-01-30 at 14:44 +0000, Eric Oberlander wrote: > Franck > > I now get an error in v1.4.11 building Stage 1 gcc, complaining of > "sed: invalid option -i" > > Something has broken make this morning, as it worked OK last night. > > Eric > > on 30/1/06 11:30 am, Franck Bourdonnec at fra...@us... > wrote: > > > Update of /cvsroot/ipcop/ipcop > > In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv8757 > > > > Modified Files: > > Tag: IPCOP_v1_4_0 > > make.sh > > Log Message: > > Fix a problem with toolchain compilation logic. Declaring new path to early, > > that is before compiling sed,m4,binutils,gcc (lpspass=1) do this: > > The very first time, everything is compiled with native system compiler. > > After this, a ggc3 will be present in the TOOLS directory. > > Asking rebuild of flex,sed,... will be done with gcc3 AND NOT the native > > compiler again. This may explain all the 'cross compilation, use --HOST=' > > errors I have when updating a tool frmo toolchain. > > > > Add variable so that lfs/makefile will be able to choose correct version > > for toolchain tools (so we can start with gcc2 or gcc4). This will prevent > > having customized lfs/makefile. > > > > > > Index: make.sh > > =================================================================== > > RCS file: /cvsroot/ipcop/ipcop/make.sh,v > > retrieving revision 1.129.2.140 > > retrieving revision 1.129.2.141 > > diff -C2 -d -r1.129.2.140 -r1.129.2.141 > > *** make.sh 30 Jan 2006 10:22:01 -0000 1.129.2.140 > > --- make.sh 30 Jan 2006 11:30:09 -0000 1.129.2.141 > > *************** > > *** 380,384 **** > > # Build sed now, as we use some extensions > > ORG_PATH=$PATH > > ! export PATH=$BASEDIR/build/usr/local/bin:$BASEDIR/build/tools/bin:$PATH > > lfsmake1 ccache > > lfsmake1 sed LFS_PASS=1 > > --- 380,385 ---- > > # Build sed now, as we use some extensions > > ORG_PATH=$PATH > > ! NATIVEGCC=`gcc --version | grep GCC | awk {'print $3'}` > > ! export NATIVEGCC GCCmajor=${NATIVEGCC:0:1} GCCminor=${NATIVEGCC:2:1} > > GCCrelease=${NATIVEGCC:4:1} > > lfsmake1 ccache > > lfsmake1 sed LFS_PASS=1 > > *************** > > *** 388,391 **** > > --- 389,394 ---- > > lfsmake1 binutils LFS_PASS=1 > > lfsmake1 gcc LFS_PASS=1 > > + export PATH=$BASEDIR/build/usr/local/bin:$BASEDIR/build/tools/bin:$PATH > > + > > lfsmake1 linux > > lfsmake1 tcl > > > > > ------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. Do you grep through log files > for problems? Stop! Download the new AJAX search engine that makes > searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 > _______________________________________________ > IPCop-devel mailing list > IPC...@li... > https://lists.sourceforge.net/lists/listinfo/ipcop-devel |