Re: problems in building gcc-3.3.5 with SUSE10.1 (having gcc-4.1.0)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Am 07.08.2006, 15:43 Uhr, schrieb Andrew Haley <aph@xxxxxxxxxx>:

Martin Krischik writes:
 > Am 07.08.2006, 12:51 Uhr, schrieb Andrew Haley <aph@xxxxxxxxxx>:
 >
 > > Tian, Pu \(NIH/NIDDK\) [C] writes:
 > >  > Hi,
> > > I am a newbie and am trying to build gcc-3.3.5 on my SUSe10.1 system
 > > (which have gcc-4.1.0 from the package, also have g77 based on
 > > gcc-3.3.5, the machine is a Thinkpad T60). I downloaded the tarball,
> > unpack it, and tried to build it in a OBJDIR gcc_BLDG with the following
 > > command:
 > >  >
 > >  > ../gcc-3.3.5/configure --prefix=/usr/local/gcc-3.3.5
 > >  > seems went OK. then
 > >  >
 > >  > make bootstrap
 > >  >
 > >  > failed with lots of warnings, the final few lines are:
 > >  >
 > >  > a-charac.ads:16:01: (style) multiple blank lines
 > >  > make[2]: *** [ada/a-charac.o] Error 1
> > > make[2]: Leaving directory `/home/pu/Documents/COMPILERS/gcc_BLDG/gcc'
 > >  > make[1]: *** [stage1_build] Error 2
> > > make[1]: Leaving directory `/home/pu/Documents/COMPILERS/gcc_BLDG/gcc'
 > >  > make: *** [bootstrap] Error 2
 > >  >
 > >  > I also tried to build in the source directory, the same thing
 > > happened. This is true for gcc-3.4.6 too. I attached the output file
 > > from configure (config.log) and make (make.log). Any advices will be
 > > highly appreciated.
 >
> Ada uses Warnings=Errors, which improves code quality a lot but also means
 > that a newer compiler - with more warnings - won't allways compiler an
 > older compiler.
 >
 > > Please don't attach such huge files to your mail.
 > >
> > Do you really need an Ada compiler? If you don't, just configure with
 > > --enable-languages=c,c++,java etc...
 >
> Well, OP certainly don't want an Ada compiler from the 3.3 branch which is
 > quite buggy. Better to use the 4.1.0 which comes with SuSE 10.1 or
> download a ready made rpm-package for SuSE 10.1 from the GNU Ada project
 > [1].

The OP has already got gcc-4.1.0.

Indeed he has.

For some reason they don't state,
3.3.5 is wanted.  I'm guessing they've got broken C++ code, by the
way...

Or Fortran - as the OP mentioned F77. So finetuning --enable-languages is best advice we can give.

Martin

--
Martin Krischik


[Index of Archives]     [Linux C Programming]     [Linux Kernel]     [eCos]     [Fedora Development]     [Fedora Announce]     [Autoconf]     [The DWARVES Debugging Tools]     [Yosemite Campsites]     [Yosemite News]     [Linux GCC]

  Powered by Linux