diff for ppc changes

I've attached a diff file against current 1.4 cvs to build
on ppc. I've also 
enabled building with binutils 2.15.90.0.3 ang gcc-4, and
building should now 
work on Ubuntu.

My changes are nothing major -- just cleaned up the
toolchain sequence a bit.

I've tested these changes on ppc with gcc4; x86 with gcc3.4
and x86 with gcc4.  
All work fine.

Let me know if you think this is ready to be committed.

IvanK.


------------------------------------------------------------
-------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the
chance to share your
opinions on IT & business topics through brief
surveys-and earn cash
http://www.techsay.com/default.
php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
IPCop-devel mailing list
IPCop-devellists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ipcop-devel

Le Tuesday 20 March 2007 09:00:25 Ivan Kabaivanov, vous avez
écrit :
> I've attached a diff file against current 1.4 cvs to
build on ppc. I've
> also enabled building with binutils 2.15.90.0.3 ang
gcc-4, and building
> should now work on Ubuntu.
>
> My changes are nothing major -- just cleaned up the
toolchain sequence a
> bit.
>
> I've tested these changes on ppc with gcc4; x86 with
gcc3.4 and x86 with
> gcc4. All work fine.
>
> Let me know if you think this is ready to be
committed.
>
> IvanK.


Hello Yvan

I prefer the model used in 1.5

the lfs/script knows itsel if it should build or not
with (your?) variable ARCH all,i486,...

------------------------------------------------------------
-------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the
chance to share your
opinions on IT & business topics through brief
surveys-and earn cash
http://www.techsay.com/default.
php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
IPCop-devel mailing list
IPCop-devellists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ipcop-devel

Selon Ivan Kabaivanov <chepatiyahoo.com>:

> I've attached a diff file against current 1.4 cvs to
build on ppc. I've also
> enabled building with binutils 2.15.90.0.3 ang gcc-4,
and building should now
> work on Ubuntu.
>
> My changes are nothing major -- just cleaned up the
toolchain sequence a bit.
>
> I've tested these changes on ppc with gcc4; x86 with
gcc3.4 and x86 with
> gcc4.
> All work fine.
>
> Let me know if you think this is ready to be
committed.
>
> IvanK.
>
>
Not tested, just read the patch.
It should introduce some error on alpha build on
src/install+setup/setup/Attic/keymap.c
Curiously, on alpha KEYMAPROOT is
"/usr/share/kbd/keymaps/i386/"

So each #if defined (__i386__) should be replaced there by
#if defined (__i386__) || defined (__alpha__)

I will test that (it mostly take me one day to build on that
machine).

Gilles

------------------------------------------------------------
-------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the
chance to share your
opinions on IT & business topics through brief
surveys-and earn cash
http://www.techsay.com/default.
php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
IPCop-devel mailing list
IPCop-devellists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ipcop-devel

----- Original Message ----- 
From: "Ivan Kabaivanov" <chepatiyahoo.com>
To: <ipcop-devellists.sourceforge.net>
Sent: Tuesday, March 20, 2007 9:00 AM
Subject: [IPCop-devel] diff for ppc changes


> I've attached a diff file against current 1.4 cvs to
build on ppc. I've
also
> enabled building with binutils 2.15.90.0.3 ang gcc-4,
and building should
now
> work on Ubuntu.
>
> My changes are nothing major -- just cleaned up the
toolchain sequence a
bit.
>
> I've tested these changes on ppc with gcc4; x86 with
gcc3.4 and x86 with
gcc4.
> All work fine.
>
> Let me know if you think this is ready to be
committed.
>
> IvanK.
>
Could you send the two patch files not added to cvs as they
did not appear
on the cvs diff and are necessary to build.

Concerning the way to split the src/ROOTFILES, the simpliest
way is to do
that in lfs/Config and redirect the files output to
config/rootfiles/arch_$MACHINE
Then compiling on a different architecture and comparing
with a diff -q will
show files that are the same or different.

Gilles


------------------------------------------------------------
-------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the
chance to share your
opinions on IT & business topics through brief
surveys-and earn cash
http://www.techsay.com/default.
php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
IPCop-devel mailing list
IPCop-devellists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ipcop-devel

On Tuesday 20 March 2007, Gilles Espinasse wrote:
> ----- Original Message -----
> From: "Ivan Kabaivanov" <chepatiyahoo.com>
> To: <ipcop-devellists.sourceforge.net>
> Sent: Tuesday, March 20, 2007 9:00 AM
> Subject: [IPCop-devel] diff for ppc changes
>
> > I've attached a diff file against current 1.4 cvs
to build on ppc. I've
>
> also
>
> > enabled building with binutils 2.15.90.0.3 ang
gcc-4, and building should
>
> now
>
> > work on Ubuntu.
> >
> > My changes are nothing major -- just cleaned up
the toolchain sequence a
>
> bit.
>
> > I've tested these changes on ppc with gcc4; x86
with gcc3.4 and x86 with
>
> gcc4.
>
> > All work fine.
> >
> > Let me know if you think this is ready to be
committed.
> >
> > IvanK.
>
> Could you send the two patch files not added to cvs as
they did not appear
> on the cvs diff and are necessary to build.
>
> Concerning the way to split the src/ROOTFILES, the
simpliest way is to do
> that in lfs/Config and redirect the files output to
> config/rootfiles/arch_$MACHINE
> Then compiling on a different architecture and
comparing with a diff -q
> will show files that are the same or different.
>
> Gilles

Gilles,

here are the two files.

IvanK.



------------------------------------------------------------
-------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the
chance to share your
opinions on IT & business topics through brief
surveys-and earn cash
http://www.techsay.com/default.
php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
IPCop-devel mailing list
IPCop-devellists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ipcop-devel

----- Original Message ----- 
From: "Ivan Kabaivanov" <chepatiyahoo.com>
To: "IPCOP devel" <ipcop-devellists.sourceforge.net>
Sent: Tuesday, March 20, 2007 10:59 PM
Subject: Re: [IPCop-devel] diff for ppc changes


> On Tuesday 20 March 2007, Gilles Espinasse wrote:
> > ----- Original Message -----
> > From: "Ivan Kabaivanov" <chepatiyahoo.com>
> > To: <ipcop-devellists.sourceforge.net>
> > Sent: Tuesday, March 20, 2007 9:00 AM
> > Subject: [IPCop-devel] diff for ppc changes
> >
Thank for the patches.
I try to build on i386 and had one failure and one still
under build that
successfully build
gcc LFS_PASS=1

Success in on debian sarge (gcc-3.3.5)

Failure is on gentoo with gcc-4.1.1
it fail at 'Building gcc LFS_PASS=1 with this error
I was able to build the toolchain before applying the
patch.

./xgcc -B./ -B/tools/i686-pc-linux-gnu/bin/ -isystem
/tools/i686-pc-linux-gnu/include -isystem
/tools/i686-pc-linux-gnu/sys-include -O2  -DIN_GCC    -W
-Wall -Wwrite-strin
gs -Wstrict-prototypes -Wmissing-prototypes -isystem
./include  -fPIC -g -DHAVE_GTHR_DEFAULT -DIN_LIBGCC2
-D__GCC_FLOAT_NOT_NEEDE
D  -fno-stack-protector-all -D_LIBC_PROVIDES_SSP_ -shared
-nodefaultlibs -Wl
,--soname=libgcc_s.so.1
-Wl,--version-script=libgcc/./libgcc.map -o
libgcc_s.so.1   libgcc/./_muldi3.o libgcc/./_negdi2.o
libgcc/./_lshrdi3.o
libgcc/./_ashldi3.o libgcc/./_ashrdi3.o libgcc/./_ffsdi2.o
libgcc/./_clz.o
libgcc/./_cmpdi2.o libgcc/./_ucmpdi2.o
libgcc/./_floatdidf.o
libgcc/./_floatdisf.o libgcc/./_fixunsdfsi.o
libgcc/./_fixunssfsi.o
libgcc/./_fixunsdfdi.o libgcc/./_fixdfdi.o
libgcc/./_fixunssfdi.o
libgcc/./_fixsfdi.o libgcc/./_fixxfdi.o
libgcc/./_fixunsxfdi.o
libgcc/./_floatdixf.o libgcc/./_fixunsxfsi.o
libgcc/./_fixtfdi.o
libgcc/./_fixunstfdi.o libgcc/./_floatditf.o
libgcc/./_clear_cache.o
libgcc/./_trampoline.o libgcc/./__main.o libgcc/./_exit.o
libgcc/./_absvsi2.o libgcc/./_absvdi2.o libgcc/./_addvsi3.o
libgcc/./_addvdi3.o libgcc/./_subvsi3.o libgcc/./_subvdi3.o
libgcc/./_mulvsi3.o libgcc/./_mulvdi3.o libgcc/./_negvsi2.o
libgcc/./_negvdi2.o libgcc/./_ctors.o
libgcc/./_stack_smash_handler.o
libgcc/./_divdi3.o libgcc/./_moddi3.o libgcc/./_udivdi3.o
libgcc/./_umoddi3.o libgcc/./_udiv_w_sdiv.o
libgcc/./_udivmoddi4.o
libgcc/./unwind-dw2.o libgcc/./unwind-dw2-fde-glibc.o
libgcc/./unwind-sjlj.o
libgcc/./unwind-c.o -lc && rm -f libgcc_s.so
&& ln -s libgcc_s.so.1
libgcc_s.so
/tools/i686-pc-linux-gnu/bin/ld:/usr/lib/libc.so: file
format not
recognized; treating as linker script
/tools/i686-pc-linux-gnu/bin/ld:/usr/lib/libc.so:5: syntax
error
collect2: ld returned 1 exit status
make[4]: *** [libgcc_s.so] Error 1
make[4]: Leaving directory
`/usr/src/ipcop/1.4b/build/usr/src/gcc-build/gcc'
make[3]: *** [libgcc.a] Error 2
make[3]: Leaving directory
`/usr/src/ipcop/1.4b/build/usr/src/gcc-build/gcc'
make[2]: *** [stage1_build] Error 2
make[2]: Leaving directory
`/usr/src/ipcop/1.4b/build/usr/src/gcc-build/gcc'
make[1]: *** [bootstrap] Error 2
make[1]: Leaving directory
`/usr/src/ipcop/1.4b/build/usr/src/gcc-build'
make: *** [/usr/src/ipcop/1.4b/log/gcc-3.3.3-tools1] Error
2

Gilles


------------------------------------------------------------
-------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the
chance to share your
opinions on IT & business topics through brief
surveys-and earn cash
http://www.techsay.com/default.
php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
IPCop-devel mailing list
IPCop-devellists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ipcop-devel

On Wednesday 21 March 2007 03:40, Gilles Espinasse wrote:
> ----- Original Message -----
> From: "Ivan Kabaivanov" <chepatiyahoo.com>
> To: "IPCOP devel" <ipcop-devellists.sourceforge.net>
> Sent: Tuesday, March 20, 2007 10:59 PM
> Subject: Re: [IPCop-devel] diff for ppc changes
>
> > On Tuesday 20 March 2007, Gilles Espinasse wrote:
> > > ----- Original Message -----
> > > From: "Ivan Kabaivanov"
<chepatiyahoo.com>
> > > To: <ipcop-devellists.sourceforge.net>
> > > Sent: Tuesday, March 20, 2007 9:00 AM
> > > Subject: [IPCop-devel] diff for ppc changes
>
> Thank for the patches.
> I try to build on i386 and had one failure and one
still under build that
> successfully build
> gcc LFS_PASS=1
>
> Success in on debian sarge (gcc-3.3.5)
>
> Failure is on gentoo with gcc-4.1.1
> it fail at 'Building gcc LFS_PASS=1 with this error
> I was able to build the toolchain before applying the
patch.
>
> ./xgcc -B./ -B/tools/i686-pc-linux-gnu/bin/ -isystem
> /tools/i686-pc-linux-gnu/include -isystem
> /tools/i686-pc-linux-gnu/sys-include -O2  -DIN_GCC   
-W -Wall
> -Wwrite-strin gs -Wstrict-prototypes
-Wmissing-prototypes -isystem
> ./include  -fPIC -g -DHAVE_GTHR_DEFAULT -DIN_LIBGCC2
> -D__GCC_FLOAT_NOT_NEEDE D  -fno-stack-protector-all
-D_LIBC_PROVIDES_SSP_
> -shared -nodefaultlibs -Wl ,--soname=libgcc_s.so.1
> -Wl,--version-script=libgcc/./libgcc.map -o
libgcc_s.so.1  
> libgcc/./_muldi3.o libgcc/./_negdi2.o
libgcc/./_lshrdi3.o
> libgcc/./_ashldi3.o libgcc/./_ashrdi3.o
libgcc/./_ffsdi2.o libgcc/./_clz.o
> libgcc/./_cmpdi2.o libgcc/./_ucmpdi2.o
libgcc/./_floatdidf.o
> libgcc/./_floatdisf.o libgcc/./_fixunsdfsi.o
libgcc/./_fixunssfsi.o
> libgcc/./_fixunsdfdi.o libgcc/./_fixdfdi.o
libgcc/./_fixunssfdi.o
> libgcc/./_fixsfdi.o libgcc/./_fixxfdi.o
libgcc/./_fixunsxfdi.o
> libgcc/./_floatdixf.o libgcc/./_fixunsxfsi.o
libgcc/./_fixtfdi.o
> libgcc/./_fixunstfdi.o libgcc/./_floatditf.o
libgcc/./_clear_cache.o
> libgcc/./_trampoline.o libgcc/./__main.o
libgcc/./_exit.o
> libgcc/./_absvsi2.o libgcc/./_absvdi2.o
libgcc/./_addvsi3.o
> libgcc/./_addvdi3.o libgcc/./_subvsi3.o
libgcc/./_subvdi3.o
> libgcc/./_mulvsi3.o libgcc/./_mulvdi3.o
libgcc/./_negvsi2.o
> libgcc/./_negvdi2.o libgcc/./_ctors.o
libgcc/./_stack_smash_handler.o
> libgcc/./_divdi3.o libgcc/./_moddi3.o
libgcc/./_udivdi3.o
> libgcc/./_umoddi3.o libgcc/./_udiv_w_sdiv.o
libgcc/./_udivmoddi4.o
> libgcc/./unwind-dw2.o libgcc/./unwind-dw2-fde-glibc.o
> libgcc/./unwind-sjlj.o libgcc/./unwind-c.o -lc
&& rm -f libgcc_s.so && ln
> -s libgcc_s.so.1 libgcc_s.so
> /tools/i686-pc-linux-gnu/bin/ld:/usr/lib/libc.so: file
format not
> recognized; treating as linker script
> /tools/i686-pc-linux-gnu/bin/ld:/usr/lib/libc.so:5:
syntax error
> collect2: ld returned 1 exit status
> make[4]: *** [libgcc_s.so] Error 1
> make[4]: Leaving directory
> `/usr/src/ipcop/1.4b/build/usr/src/gcc-build/gcc'
make[3]: *** [libgcc.a]
> Error 2
> make[3]: Leaving directory
> `/usr/src/ipcop/1.4b/build/usr/src/gcc-build/gcc'
make[2]: ***
> [stage1_build] Error 2
> make[2]: Leaving directory
> `/usr/src/ipcop/1.4b/build/usr/src/gcc-build/gcc'
make[1]: *** [bootstrap]
> Error 2
> make[1]: Leaving directory
`/usr/src/ipcop/1.4b/build/usr/src/gcc-build'
> make: *** [/usr/src/ipcop/1.4b/log/gcc-3.3.3-tools1]
Error 2
>
> Gilles


Gilles,

what's the glibc version you have on gentoo?  Can you email
the contents 
of /usr/lib/libc.so -- there should be 5 lines.  Is line 5
like this:

GROUP ( /lib/libc.so.6 /usr/lib/libc_nonshared.a AS_NEEDED 
( /lib/ld-linux.so.2 ) )

this is on one line.

Try changing it to:

GROUP ( /lib/libc.so.6 /usr/lib/libc_nonshared.a )

but then after you compile ipcop-toolchain stage, change it
back.

Looks like the problem is that old binutils' ld doesn't
understand AS_NEEDED.  
That means we have to upgrade binutils, but I wanted to stay
with the 
original 1.4.x binutils to avoid trouble (even though I
don't think there'll 
be any even if we do upgrade).  I just don't like messing
with the toolchain 
(binutils,gcc,glibc).

IvanK.

------------------------------------------------------------
-------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the
chance to share your
opinions on IT & business topics through brief
surveys-and earn cash
http://www.techsay.com/default.
php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
IPCop-devel mailing list
IPCop-devellists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ipcop-devel

----- Original Message ----- 
From: "Ivan Kabaivanov" <chepatiyahoo.com>
To: "IPCOP devel" <ipcop-devellists.sourceforge.net>
Sent: Wednesday, March 21, 2007 8:46 PM
Subject: Re: [IPCop-devel] diff for ppc changes


> On Wednesday 21 March 2007 03:40, Gilles Espinasse
wrote:
> > ----- Original Message -----
> > From: "Ivan Kabaivanov" <chepatiyahoo.com>
> > To: "IPCOP devel" <ipcop-devellists.sourceforge.net>
> > Sent: Tuesday, March 20, 2007 10:59 PM
> > Subject: Re: [IPCop-devel] diff for ppc changes
> >
> > > On Tuesday 20 March 2007, Gilles Espinasse
wrote:
> > > > ----- Original Message -----
> > > > From: "Ivan Kabaivanov"
<chepatiyahoo.com>
> > > > To: <ipcop-devellists.sourceforge.net>
> > > > Sent: Tuesday, March 20, 2007 9:00 AM
> > > > Subject: [IPCop-devel] diff for ppc
changes
> >
> > Thank for the patches.
> > I try to build on i386 and had one failure and one
still under build
that
> > successfully build
> > gcc LFS_PASS=1
> >
> > Success in on debian sarge (gcc-3.3.5)
> >
> > Failure is on gentoo with gcc-4.1.1
> > it fail at 'Building gcc LFS_PASS=1 with this
error
> > I was able to build the toolchain before applying
the patch.
> >
...
> > /tools/i686-pc-linux-gnu/bin/ld:/usr/lib/libc.so:
file format not
> > recognized; treating as linker script
> >
/tools/i686-pc-linux-gnu/bin/ld:/usr/lib/libc.so:5: syntax
error
> > collect2: ld returned 1 exit status
> > make[4]: *** [libgcc_s.so] Error 1
> > make[4]: Leaving directory
> > `/usr/src/ipcop/1.4b/build/usr/src/gcc-build/gcc'
make[3]: ***
[libgcc.a]
> > Error 2
> > make[3]: Leaving directory
> > `/usr/src/ipcop/1.4b/build/usr/src/gcc-build/gcc'
make[2]: ***
> > [stage1_build] Error 2
> > make[2]: Leaving directory
> > `/usr/src/ipcop/1.4b/build/usr/src/gcc-build/gcc'
make[1]: ***
[bootstrap]
> > Error 2
> > make[1]: Leaving directory
`/usr/src/ipcop/1.4b/build/usr/src/gcc-build'
> > make: ***
[/usr/src/ipcop/1.4b/log/gcc-3.3.3-tools1] Error 2
> >
> > Gilles
>
>
> Gilles,
>
> what's the glibc version you have on gentoo?  Can you
email the contents
> of /usr/lib/libc.so -- there should be 5 lines.  Is
line 5 like this:
>
> GROUP ( /lib/libc.so.6 /usr/lib/libc_nonshared.a
AS_NEEDED
> ( /lib/ld-linux.so.2 ) )
>
> this is on one line.
>
> Try changing it to:
>
> GROUP ( /lib/libc.so.6 /usr/lib/libc_nonshared.a )
>
> but then after you compile ipcop-toolchain stage,
change it back.
>
> Looks like the problem is that old binutils' ld doesn't
understand
AS_NEEDED.
> That means we have to upgrade binutils, but I wanted to
stay with the
> original 1.4.x binutils to avoid trouble (even though I
don't think
there'll
> be any even if we do upgrade).  I just don't like
messing with the
toolchain
> (binutils,gcc,glibc).
>
> IvanK.
>
the workaround allow to pass Building gcc LFS_PASS=1
glibc version is 2.4

Gilles


------------------------------------------------------------
-------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the
chance to share your
opinions on IT & business topics through brief
surveys-and earn cash
http://www.techsay.com/default.
php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
IPCop-devel mailing list
IPCop-devellists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ipcop-devel