Re: building gcc 4.0.0 on Solaris

2005-05-11 Thread Eric Botcazou
> I meant when using GCC with the Sun assembler/linker, it shows up on > sparc. But it doesn't show up on sparc when using Sun cc with Sun > assembler/linker, and thus Sun doesn't document it as a sparc problem. OK, I misinterpreted "tools", thanks for the clarification. Yes, that is a very pla

Re: building gcc 4.0.0 on Solaris

2005-05-11 Thread James E Wilson
On Sat, 2005-05-07 at 10:22, Eric Botcazou wrote: > > Apparently this problem only shows up for x86 when using Sun tools, but > > when using GNU tools, it also shows up for sparc. > Do you have a testcase? AFAIK the problem only shows up with the Sun tools. I meant when using GCC with the Sun ass

Re: building gcc 4.0.0 on Solaris

2005-05-11 Thread Dimitri Papadopoulos-Orfanos
Hi, OK, I guess the latest compilers from Sun ship with a better "as". Unfortunately I'm stuck with Sun Studio One 7 for now. Maybe it should be documented that a recent version of "as" is needed by gcc. A version not affected by the bug. 4.0.0 bootstraps on Solaris 2.5.1 with as: WorkShop Compil

Re: building gcc 4.0.0 on Solaris

2005-05-10 Thread Eric Botcazou
> I'm also using --with-gnu-as and --with-gnu-ld now. At some point these > were required or made a difference on HP-UX only as far as I can recall; > I hadn't noticed they were now required or making a difference on > Solaris too. They should not be required if --with-as and --with-ld are respect

Re: building gcc 4.0.0 on Solaris

2005-05-10 Thread Dimitri Papadopoulos-Orfanos
Hi, BTW: Have you tried to also look at what ulimits are set on your system? I've rebooted the system and things are really getting better (even Sun's "ar" seems to be working now). This was a kernel problem, the kernel is not up-to-date with patches and the workstation hadn't been rebooted for

Re: building gcc 4.0.0 on Solaris

2005-05-10 Thread Karel Gardas
On Tue, 10 May 2005, Dimitri Papadopoulos-Orfanos wrote: > > Yeah, in 1991 my 386 featured 4 Mb and I really see no reason why it could > > not > > be used to build libgcj nowadays. ;-) > > Ooops :-) > > These were indeed Gb instead of Mb for those wondering... [have not followed this thread, so

Re: building gcc 4.0.0 on Solaris

2005-05-10 Thread Dimitri Papadopoulos-Orfanos
Yeah, in 1991 my 386 featured 4 Mb and I really see no reason why it could not be used to build libgcj nowadays. ;-) Ooops :-) These were indeed Gb instead of Mb for those wondering... -- Dimitri

Re: building gcc 4.0.0 on Solaris

2005-05-10 Thread Eric Botcazou
> /usr/local/binutils/bin/ld [...] -soname libgcj.so.6 > [...] > GNU ld version 2.16 >Supported emulations: > elf32_sparc > elf64_sparc > /usr/local/binutils/bin/ld: failed to set dynamic section sizes: Memory > exhausted > > Ouch! 1 Mb RAM + 2Mb swap ought to be enough. Yeah, in 1991

Re: building gcc 4.0.0 on Solaris

2005-05-10 Thread Dimitri Papadopoulos-Orfanos
Hi, Pass -debug to collect2. I'm not sure this will give you a *small* testcase though. /usr/local/binutils/bin/ld [...] -soname libgcj.so.6 [...] GNU ld version 2.16 Supported emulations: elf32_sparc elf64_sparc /usr/local/binutils/bin/ld: failed to set dynamic section sizes: Memory exh

Re: building gcc 4.0.0 on Solaris

2005-05-10 Thread Eric Botcazou
> Actually I'd like to help fix bugs in the Solaris toolchain, apart from > compiling my C++ programs. > > Using "xgcc -v" instead of plain "xgcc" I've found that the problem > happens here: > /tmp/GCC/gcc/collect2 [...] /tmp/GCC/gcc/crtn.o -soname libgcj.so.6 > collect2: ld returned 1 exit status

Re: building gcc 4.0.0 on Solaris

2005-05-10 Thread Eric Botcazou
> Actually I'd like to help fix bugs in the Solaris toolchain, apart from > compiling my C++ programs. > > Using "xgcc -v" instead of plain "xgcc" I've found that the problem > happens here: > /tmp/GCC/gcc/collect2 [...] /tmp/GCC/gcc/crtn.o -soname libgcj.so.6 > collect2: ld returned 1 exit status

Re: building gcc 4.0.0 on Solaris

2005-05-10 Thread Dimitri Papadopoulos-Orfanos
Hi, libgcj.so.6.0.0 is a monster so that could be a memory problem too. If you're not interested in Java, I'd suggest to configure with --disable-libgcj. Actually I'd like to help fix bugs in the Solaris toolchain, apart from compiling my C++ programs. Using "xgcc -v" instead of plain "xgcc" I

Re: building gcc 4.0.0 on Solaris

2005-05-10 Thread Dimitri Papadopoulos-Orfanos
Hi, I have configured with: ./configure \ --with-as=/usr/local/binutils/bin/as \ --with-ld=/usr/local/binutils/bin/ld \ ... so I should be using GNU's as and ld. --with-gnu-as and --with-gnu-ld I presume? No, but configure does detect that, d

Re: building gcc 4.0.0 on Solaris

2005-05-10 Thread Eric Botcazou
> > How did you configure? The mix of GNU tools and Sun tools looks > > suspicious. > > I think there's no mix involved. > > I have configured with: > ./configure \ > --with-as=/usr/local/binutils/bin/as \ > --with-ld=/usr/local/binutils/bin/ld \ > .

Re: building gcc 4.0.0 on Solaris

2005-05-10 Thread Dimitri Papadopoulos-Orfanos
Hi, How did you configure? The mix of GNU tools and Sun tools looks suspicious. I think there's no mix involved. I have configured with: ./configure \ --with-as=/usr/local/binutils/bin/as \ --with-ld=/usr/local/binutils/bin/ld \ ... so I shou

Re: building gcc 4.0.0 on Solaris

2005-05-10 Thread Eric Botcazou
> I've worked around this by changing all occurrences of AR="ar" in > sparc-sun-solaris2.8/libjava/libtool to AR="/usr/local/binutils/bin/ar". > Using GNU's ar fixes the problem indeed. > > I have another problem later on, again in sparc-sun-solaris2.8/libjava: > > /tmp/GCC/gcc/xgcc -shared-libgcc

Re: building gcc 4.0.0 on Solaris

2005-05-10 Thread Dimitri Papadopoulos-Orfanos
Hi, I have installed binutils-2.16. Things work better in the sense that I get much farther into building the Java libraries. I still hit a problem: [...] ar rc .libs/libgcj0_convenience.a [... around 100.000 characters ...] internal error: error_message(58) [...] Is this a known issue? I've work

Re: building gcc 4.0.0 on Solaris

2005-05-09 Thread Dimitri Papadopoulos-Orfanos
Hi, As far as I can understand, it's not possible to build gcc 4.0.0 and gcc 3.4.* using GNU binutils with current release 2.15 of GNU binutils. One has to use the CVS sources or at least one file. FYI binutils-2.16 has just been released. You might want to try that. I have installed binutils-2

Re: building gcc 4.0.0 on Solaris

2005-05-07 Thread Eric Botcazou
> > Bug ID: 4910101 > > Synopsis: fbe needs a way to reference section labels > > Category: compiler > > Subcategory: assembler-x86 > > Apparently this problem only shows up for x86 when using Sun tools, but > when using GNU tools, it also shows up for sparc. Do you have a testcase

Re: building gcc 4.0.0 on Solaris

2005-05-03 Thread James E Wilson
Dimitri Papadopoulos-Orfanos wrote: As far as I can understand, it's not possible to build gcc 4.0.0 and gcc 3.4.* using GNU binutils with current release 2.15 of GNU binutils. One has to use the CVS sources or at least one file. FYI binutils-2.16 has just been released. You might want to try th

Re: building gcc 4.0.0 on Solaris

2005-05-02 Thread Eric Botcazou
> OK, I guess the latest compilers from Sun ship with a better "as". > Unfortunately I'm stuck with Sun Studio One 7 for now. Maybe it should > be documented that a recent version of "as" is needed by gcc. A version not affected by the bug. 4.0.0 bootstraps on Solaris 2.5.1 with as: WorkShop Comp

Re: building gcc 4.0.0 on Solaris

2005-05-02 Thread Dimitri Papadopoulos-Orfanos
Hi, The build fails with the following message: ld: fatal: relocation error: R_SPARC_DISP32: file .libs/libstdc++.lax/libsupc++convenience.a/vterminate.o: symbol : offset 0xfccd33ad is non-aligned Probably a Sun 'as' bug, a similar problem was reported on Solaris 7: http://gcc.gnu.org/install/spec

Re: building gcc 4.0.0 on Solaris

2005-04-30 Thread Eric Botcazou
> 1) Using Sun's as/ld. I build gcc this way: > cd /tmp > gtar xjf ~/gcc-4.0.0.tar.bz2 > mkdir gcc > cd gcc > setenv CONFIG_SHELL /bin/ksh > /tmp/gcc-4.0.0/configure \ > --prefix=/usr/local/gcc-4.0.0 > gmake bootstrap > > The build fails with