Re: 4.3.0 and 4.3.1 don't build startfiles (crtXXX.o files)

2008-06-08 Thread Joseph S. Myers
On Sun, 8 Jun 2008, Denys Vlasenko wrote: > What is Paul's suggested process? I just reread his post again > and it contains no suggestions what to do, it was useful in > other way: he explained where my understanding of build process > is incorrect: The procedure for EGLIBC is documented in deta

Re: 4.3.0 and 4.3.1 don't build startfiles (crtXXX.o files)

2008-06-08 Thread Paolo Bonzini
1) Binutils 2) Whatever bits of compiler are required to produce... 3) libc headers 4) A basic C compiler+libgcc that is sufficient to build... 5) libc 6) A full compiler+runtime, c++, fortran, etc. If someone is willing to expand on the above and explain what exactly do I need to do in step 2,

Re: 4.3.0 and 4.3.1 don't build startfiles (crtXXX.o files)

2008-06-08 Thread Denys Vlasenko
On Sunday 08 June 2008 22:41, Paolo Bonzini wrote: > > > Then, running "make all-target-libgcc" built them, but I finally settled > > for just "make" - it didn't error out. > > Yes, the advantage of Paul's suggested process are not only that the > installations are reproducible and always use th

Re: 4.3.0 and 4.3.1 don't build startfiles (crtXXX.o files)

2008-06-08 Thread Paolo Bonzini
Then, running "make all-target-libgcc" built them, but I finally settled for just "make" - it didn't error out. Yes, the advantage of Paul's suggested process are not only that the installations are reproducible and always use the complete feature set of the underlying libc (that's the big p

Re: 4.3.0 and 4.3.1 don't build startfiles (crtXXX.o files)

2008-06-08 Thread Denys Vlasenko
On Sunday 08 June 2008 16:27, Paul Brook wrote: > > As far as I know, toolchain is built in this order: > > > > 1. binutils > > 2. C compiler > > 3. libc > > No. > > That usually only works if you already have the toolchain installed. In which > case ordering is irelevant, you can just build whi

Re: 4.3.0 and 4.3.1 don't build startfiles (crtXXX.o files)

2008-06-08 Thread Paul Brook
> As far as I know, toolchain is built in this order: > > 1. binutils > 2. C compiler > 3. libc No. That usually only works if you already have the toolchain installed. In which case ordering is irelevant, you can just build whichever component you want to update. A full bootstrap process look

Re: 4.3.0 and 4.3.1 don't build startfiles (crtXXX.o files)

2008-06-08 Thread Denys Vlasenko
On Sunday 08 June 2008 13:50, Joseph S. Myers wrote: > On Sun, 8 Jun 2008, Denys Vlasenko wrote: > > > ../../../gcc-4.3.1/libgcc/config/libbid/bid_decimal_globals.c:52:18: error: > > fenv.h: No such file or directory > > Decimal floating point requires . The DPD code only requires the > header

Re: 4.3.0 and 4.3.1 don't build startfiles (crtXXX.o files)

2008-06-08 Thread Joseph S. Myers
On Sun, 8 Jun 2008, Denys Vlasenko wrote: > ../../../gcc-4.3.1/libgcc/config/libbid/bid_decimal_globals.c:52:18: error: > fenv.h: No such file or directory Decimal floating point requires . The DPD code only requires the header, not any of the actual functions it declares; it looks like the BI

Re: 4.3.0 and 4.3.1 don't build startfiles (crtXXX.o files)

2008-06-08 Thread Denys Vlasenko
On Sunday 08 June 2008 04:52, Daniel Jacobowitz wrote: > On Sat, Jun 07, 2008 at 11:26:05AM +0200, Denys Vlasenko wrote: > > Seen that 4.3.1 has been released, I tried to build > > i486-linux-uclibc cross-compiler. > > You probably forgot to build libgcc. Are you using 'make all' / 'make > instal

Re: 4.3.0 and 4.3.1 don't build startfiles (crtXXX.o files)

2008-06-07 Thread Daniel Jacobowitz
On Sat, Jun 07, 2008 at 11:26:05AM +0200, Denys Vlasenko wrote: > Seen that 4.3.1 has been released, I tried to build > i486-linux-uclibc cross-compiler. You probably forgot to build libgcc. Are you using 'make all' / 'make install' or something more specific? Also check the libgcc configure.hos

4.3.0 and 4.3.1 don't build startfiles (crtXXX.o files)

2008-06-07 Thread Denys Vlasenko
Seen that 4.3.1 has been released, I tried to build i486-linux-uclibc cross-compiler. It went fine except for the detail that none of crt.o files are found in installation directory after "make install" For comparison, gcc 4.2.1's directory has them: # find -name 'crt*.o' ./lib/gcc/i486-linu