Linux Intel Requirements to Build egcs

Linux Intel Requirements to Build egcs

[Sean O'Keeffe]

I'm new to the list and I haven't been able to build any of the ecgs
binaries from 971031.  I always end up with cpp usage errors in various
places.

I am running RedHat 4.2 and I have made all of the upgrades necessary to
build 2.1.x kernels.  (I run kernel 2.1.57 if that makes any
differnece.)  My machine is a SMP dual PPro.

I have:

binutils 2.8.1.0.1
libc-5.4.28
gcc-2.7.2.3
libg++-2.7.2.8
ld.so 1.9.5
dejagnu 1.3

Do I need libgcc2?

Also what ./configure options should I be using for this settup?

(I noticed that autoconf always generates gcc/Makefile with
USE_COLLECT=ld even if I don't specify --with-gnu-ld.  Is this an error?
I remove this by hand my compile goes much further but still fails.)

Thanks, Sean

------------------------
- Sean Kevin O'Keeffe  -
- (619) 272-1673       -
- sokeeffe@ucsd.edu    -  
------------------------

Re: Linux Intel Requirements to Build egcs

[Joe Buck]

> I'm new to the list and I haven't been able to build any of the ecgs
> binaries from 971031.  I always end up with cpp usage errors in various
> places.

Odd.

> I am running RedHat 4.2 and I have made all of the upgrades necessary to
> build 2.1.x kernels.  (I run kernel 2.1.57 if that makes any
> differnece.)  My machine is a SMP dual PPro.

egcs builds fine on a straight Intel RedHat 4.2 system.  Maybe there is
something funny about your setup -- we'd need to see exactly what messages
you are getting.

> (I noticed that autoconf always generates gcc/Makefile with
> USE_COLLECT=ld even if I don't specify --with-gnu-ld.  Is this an error?

No.

> I remove this by hand my compile goes much further but still fails.)

The intent is that you don't need to change anything, just

configure [--prefix=/some/path]
make bootstrap
make install

Re: Linux Intel Requirements to Build egcs

[Jim Wilson]

	I'm new to the list and I haven't been able to build any of the ecgs
	binaries from 971031.  I always end up with cpp usage errors in various
	places.

This usually indicates that some environment variable is set incorrectly.
If one of the environment variables that gcc uses has an explicit or implicit
`.' among the list of filenames, then the old gcc that you are using to
compile EGCS will accidentally try to load and use some of the new files in
EGCS, and the old gcc gets confused because of incompatibilities because
the old and new versions of these files.

If you fix your environment variable, then the problem will go away.  The
most likely culprits are COMPILER_PATH, LIBRARY_PATH, and LPATH.  If any
of these have an explicit `.' in them, or if they start or end with a
colon (which adds an implicit `.' to the directory list) then this is what
is causing EGCS to fail.

	Do I need libgcc2?

All targets need libgcc2.  libgcc2 is part of gcc, and will automatically
be built.  There is no need to worry about.

	Also what ./configure options should I be using for this settup?

I don't know.

	(I noticed that autoconf always generates gcc/Makefile with
	USE_COLLECT=ld even if I don't specify --with-gnu-ld.  Is this an error?
	I remove this by hand my compile goes much further but still fails.)

No, this isn't an error.  This tells gcc to build collect2.  Collect2 is
always needed now, regardless of whether GNU ld is being used, because collect2
includes C++ template instantiation support which is not in GNU ld.

Jim

Re: Linux Intel Requirements to Build egcs

[Jeffrey A Law]

  In message < Pine.SOL.3.95.971104175328.26534A-100000@galaxy.ucsd.edu >you writ:
  > Do I need libgcc2?
No, it's built as part of the normal build/install process for
egcs/gcc.


  > Also what ./configure options should I be using for this settup?
You shouldn't need any, unless you want to install into a nonstandard
directory -- in which case you'd use --prefix=somedir

  > (I noticed that autoconf always generates gcc/Makefile with
  > USE_COLLECT=ld even if I don't specify --with-gnu-ld.  Is this an error?
  > I remove this by hand my compile goes much further but still fails.)
Nope, this is intentional.

Maybe if you provided the details about what went wrong we could
help you.  cut-and-paste the errors from the build....

jeff

Re: Linux Intel Requirements to Build egcs

[H.J. Lu]

> 
> 
> I'm new to the list and I haven't been able to build any of the ecgs
> binaries from 971031.  I always end up with cpp usage errors in various

971031 is broken on linux. You need Jeff's dwarf2out.c patch for
x86. For alpha, you need my toplev.c and Jeff's alias.c patches.

> places.
> 
> I am running RedHat 4.2 and I have made all of the upgrades necessary to
> build 2.1.x kernels.  (I run kernel 2.1.57 if that makes any
> differnece.)  My machine is a SMP dual PPro.
> 
> I have:
> 
> binutils 2.8.1.0.1

You need binutils 2.8.1.0.15.

> libc-5.4.28
> gcc-2.7.2.3
> ld.so 1.9.5

You need my libg++ 2.8.0b6.3 and my patch to egcs. Check out
the egcs archive for them.

> libg++-2.7.2.8
> dejagnu 1.3

You need dejagnu 971028.


H.J.

Re: Linux Intel Requirements to Build egcs

[Andrey Slepuhin]

Joe Buck wrote:
> > I am running RedHat 4.2 and I have made all of the upgrades necessary to
> > build 2.1.x kernels.  (I run kernel 2.1.57 if that makes any
> > differnece.)  My machine is a SMP dual PPro.
> 
> egcs builds fine on a straight Intel RedHat 4.2 system.  Maybe there is
> something funny about your setup -- we'd need to see exactly what messages
> you are getting.

I also had the same problems trying to build egcs on PPro ander RedHat 4.2.
The problem is following: gcc from RedHat distribution (2.7.2.1) has ./ in
the path where it searches for specs file - so it takes this file from
gcc subdirectory in egcs when make enter this subdirectory . It seems to me
that gcc 2.7.2.1 couldn't understand correctly some information from this
file (may be due to some information about i686 CPU) and passes incorrect
options to cpp.

Andrey Slepuhin,
Moscow State University

Re: Linux Intel Requirements to Build egcs

[Patrick Michael Kane]

I just ran a test build on a dual PPro200 system running stock RedHat 4.2. 
All systems go.

Quoting Andrey Slepuhin (pooh@msu.ru):
[-- Warning: koi8-r is not compatible with your display.]

> Joe Buck wrote:
> > > I am running RedHat 4.2 and I have made all of the upgrades necessary to
> > > build 2.1.x kernels.  (I run kernel 2.1.57 if that makes any
> > > differnece.)  My machine is a SMP dual PPro.
> > 
> > egcs builds fine on a straight Intel RedHat 4.2 system.  Maybe there is
> > something funny about your setup -- we'd need to see exactly what messages
> > you are getting.
> 
> I also had the same problems trying to build egcs on PPro ander RedHat 4.2.
> The problem is following: gcc from RedHat distribution (2.7.2.1) has ./ in
> the path where it searches for specs file - so it takes this file from
> gcc subdirectory in egcs when make enter this subdirectory . It seems to me
> that gcc 2.7.2.1 couldn't understand correctly some information from this
> file (may be due to some information about i686 CPU) and passes incorrect
> options to cpp.
> 
> Andrey Slepuhin,
> Moscow State University

-- 
-----BEGIN PGP SIGNATURE-----
Version: 2.6.3i

iQB1AwUBNGCDuajKvguh7HhBAQGBEAL/f0+yqJZOhQZi/GX4+k4giGxgysyGXLYQ
MIEqaeixqq1Mzraehf/Uc427WnJKai+hyJkunpllwcSxlGY0Ooxit2ZYFfSmeV+a
Z1vp2Fssi5NgXajaFR2ON0rU9chflhzG
=zGtd
-----END PGP SIGNATURE-----

Re: Linux Intel Requirements to Build egcs

[Joe Buck]

> 	Do I need libgcc2?
> 
> All targets need libgcc2.  libgcc2 is part of gcc, and will automatically
> be built.  There is no need to worry about.

He's probably confusing libgcc2 with glibc2, which is a completely
different thing.

Re: Linux Intel Requirements to Build egcs

[Joe Buck]

> I also had the same problems trying to build egcs on PPro ander RedHat 4.2.
> The problem is following: gcc from RedHat distribution (2.7.2.1) has ./ in
> the path where it searches for specs file - so it takes this file from
> gcc subdirectory in egcs when make enter this subdirectory . It seems to me
> that gcc 2.7.2.1 couldn't understand correctly some information from this
> file (may be due to some information about i686 CPU) and passes incorrect
> options to cpp.

I did not see this symptom (on Red Hat 4.2).  My builds work OK.
Could you post the output that you got?  (The exact error messsages,
not just an interpretation of what went wrong).

Re: Linux Intel Requirements to Build egcs

[Joe Buck]

> > I'm new to the list and I haven't been able to build any of the ecgs
> > binaries from 971031.  I always end up with cpp usage errors in various
> 
> 971031 is broken on linux. You need Jeff's dwarf2out.c patch for
> x86. For alpha, you need my toplev.c and Jeff's alias.c patches.

Right, my apologies.  My successful build (on Red Hat 4.2) uses Jeff's patch.
The patch can be found at

http://www.cygnus.com/ml/egcs/1997-Nov/0009.html