Problems building libstdc++-v3

[Kai Ruottu]

"Kai Ruottu" <kai.ruottu@luukku.com> wrote:

> > /usr/local/powerpc/powerpc-eabi/lib/und/libyk.a(sbrk.o): In function `sbrk':
> > /home/lobell/build/newlib/powerpc-eabi/und/libgloss/rs6000/../../../../../../src/newlib-1.10.0/libgloss/sbrk.c:33: 
> > undefined reference to `__end'
> > 
> > In yellowknife.ld (my target), only _end is defined. Is there a reason for 
> > compiling with -fleading-underscore in powerpc-eabi/und/libiberty?
> 
>  So your workaround could be to not build any 'und' libraries,
> because it is unclear for what purpose they will be needed --
> for compatability with some commercial tools, for some old
> prebuilt libs, of why...

 Does someone know why the libs with the leading underscore in the
symbol name would still be needed in the 'powerpc-eabi' tools ?  I
remember that some years ago there were 3rd party libraries which
had the underscore in symbols, but is there anymore ?

 As told, the provided '*.ld'-files don't define the '__end' to be
the same as '_end', so the undercsored variations are not remembered
in them.  BTW, I didn't notice the default linker script having
'__end__', not '__end' :

> -------------------- clip -------------------------
>   .endjunk BLOCK(__section_alignment__) :
>   {
>     /* end is deprecated, don't use it */
>      end = .;			<------
>      _end = .;			<------
>      __end__ = .;		<------
>   }
> -------------------- clip -------------------------

 But if the 'und'-variations of the libs are really needed,
fixing the provided '*.ld' files to have the :

      _end = .;
      __end = .;

instead of only the '_end = .;', would then be the necessary
bugfix...

Cheers, Kai


------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com