egcs-199805171100UTC snapshot on m68k-next-nextstep3: strangebehaviour in compiling libiberty ...

Toon Moene toon@moene.indiv.nluug.nl
Mon May 18 10:18:00 GMT 1998


Jeff,

  > >  Did you configure with --enable-shared?  It looks like
  > >  it's trying to build a PIC libiberty.

  > Well, I most certainly did not (if you think a Fortran user has any  
  > use for shared libraries - like in reducing the memory footprint of  
  > the entire system by sharing code - think again:  I'm just
  > interested in running one big executable at a time :-)

>  By chance did you wipe your entire build tree after doing
>  the update?
>
>  I was able to get the same failure mode (enable_shared
>  stuff in the generated Makefile, even though I hadn't
>  turned on --enable-shared).
>
>  I ended up wiping out that tree because I wanted to watch
>  a full configure, and wouldn't you know it the problem
>  is gone.

Hmmm, I thought I started from a clean slate (I really have no  
choice  - due to disk resource limitations I can only build one of  
{gcc2, egcs} at a time, and I had to build the former to alpha-test  
g77-0.5.23 ...)

I retried `../egcs/configure --prefix=/usr/snp' with a clean object  
directory; this is the relevant part of obj/libiberty/Makefile:

# Warning: this fragment is automatically generated
# Following fragment copied from  
../../egcs/libiberty/config/../../config/mh-m68kpic
PICFLAG=-fpic
enable_shared = yes

which doesn't really surprise me, because IIRC it always built the  
`-fpic' part - the only reason to worry about it this time was the  
invalid assembler produced ;-)

BTW, it seems to take an inordinate amount of time to configure  
libiberty - the first time (before keeping an eye on it with tail -f  
config.log) I thought it hung ...

HTH,
Toon.



More information about the Gcc-bugs mailing list