Re: egcs-1.0.2 installation -- bug (?)

Re: egcs-1.0.2 installation -- bug (?)

[Markus Sicheneder]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1402 bytes --]

hello,

first of all i want to thank you all for your help, especially Horst von
Brand. finally i solved the problems i had with building egcs and the
shared libraries.
i send this message also to egcs-bugs@cygnus.com. maybe it´s not a
"real" bug (in the code), but it gave me a hard time during compilation
-- so decide yourself; i think a note in the installation files would
help.

trying to build the shared libraries compilation always ended with an
error like:
	xgcc: pic/cmathi.o: No such file or directory.
about a dozen of object files were quotet not to be in the "pic"
directory.

Horst von Brand mentioned:
> AFAIK, there has to be a pic directory in each of the directories into
> which libraries are built, in this case I think it would be
Well, the pic directories exist for the "libiberty" and the "libio", but
not for the "libstc++" :-(

the files needed are list in
	objdir/libraries/libstdc++/piclist.
a closer look at this file shows that a directory "pic" in the path
"objdir/libraries/libstdc++/" is needed. i created this and also copied
all the object files from "objdir/libraries/libstdc++/" to the "pic"
directory (just in case ...)

after doing this it compiled just fine :-)

regards,
	markus

-- 
Markus Sicheneder, Allmandring 20 C, D-70569 Stuttgart
e-mail: sichen@studbox.uni-stuttgart.de                        
www:    http://wwwcip.rus.uni-stuttgart.de/~lrt12741/

Re: egcs-1.0.2 installation -- bug (?)

[Horst von Brand]

Markus Sicheneder <sichen@studbox.uni-stuttgart.de> said:
> Horst von Brand mentioned:
> > AFAIK, there has to be a pic directory in each of the directories into
> > which libraries are built, in this case I think it would be

> Well, the pic directories exist for the "libiberty" and the "libio", but
> not for the "libstc++" :-(

I'd call this a bug in the build process: If libwhatever/pic/ doesn't exist,
it should be created during the build.

> the files needed are list in
> 	objdir/libraries/libstdc++/piclist.
> a closer look at this file shows that a directory "pic" in the path
> "objdir/libraries/libstdc++/" is needed. i created this and also copied
> all the object files from "objdir/libraries/libstdc++/" to the "pic"
> directory (just in case ...)

Careful there! The files in the pic directory should have been compiled
with -fPIC, i.e., be position independent. If you move/copy other *.o files
that weren't compiled with -fPIC, you can build a shared library just fine
(at least under some systems), only it will _not_ be really shared, it has
to be relocated for each program that uses it: Longer startup times and
much more memory consumption. But no warnings ;-/
-- 
Dr. Horst H. von Brand                       mailto:vonbrand@inf.utfsm.cl
Departamento de Informatica                     Fono: +56 32 654431
Universidad Tecnica Federico Santa Maria              +56 32 654239
Casilla 110-V, Valparaiso, Chile                Fax:  +56 32 797513

Re: egcs-1.0.2 installation -- bug (?)

[Jeffrey A Law]

  In message < 199804171422.KAA15812@pincoya.inf.utfsm.cl >you write:
  > Markus Sicheneder <sichen@studbox.uni-stuttgart.de> said:
  > > Horst von Brand mentioned:
  > > > AFAIK, there has to be a pic directory in each of the directories into
  > > > which libraries are built, in this case I think it would be
  > 
  > > Well, the pic directories exist for the "libiberty" and the "libio", but
  > > not for the "libstc++" :-(
  > 
  > I'd call this a bug in the build process: If libwhatever/pic/ doesn't
  > exist, it should be created during the build.
Absolutely.

Did anyone actually bug the problem to find out why the pic directories
weren't created in the first place?  (No, I haven't managed to read the
whole thread -- I'm looking for an exec summary :-)

jeff