Re: egcs1.1.2 lnx cross ppc newuser followup

[Jeffrey A Law <law at upchuck dot cygnus dot com>]

  In message <9904021924.AA25430@dogbert>you write:
  > I tried some advice I got earlier. I recompiled binutils without --with-new
  > lib I added --with-headers instead.
  > 
  > I then rebuilt from scratch egcs.
  > I am still getting the following undefined
  > symbols in the following directory during configure:
  > 
  > /home/jperry/cross-compile-linux-egcs112-objdir/ppc-rtems-eabi/libiberty
  > 
  > Here is config.log from that directory.
  > 
  > This file contains any messages produced by compilers while
  > running configure, to aid debugging if configure makes a mistake.

  > /home/jperry/cross-compile-linux-egcs112-objdir/gcc/libgcc.a(eabi.o)(.got2+
  > 0x8)
  > : undefined reference to `__SDATA_START__'
  > /home/jperry/cross-compile-linux-egcs112-objdir/gcc/libgcc.a(eabi.o)(.got2+
  > 0xc)
  > : undefined reference to `__SBSS_END__'
  > /home/jperry/cross-compile-linux-egcs112-objdir/gcc/libgcc.a(eabi.o)(.got2+
  > 0x14
  > ): undefined reference to `__SDATA2_START__'
  > /home/jperry/cross-compile-linux-egcs112-objdir/gcc/libgcc.a(eabi.o)(.got2+
  > 0x18
  > ): undefined reference to `__SBSS2_END__'
Two issues I can think of.

  1. Is is possible these symbols are supposed to be defiend by the linker
     via a linker script?   I believe this is the case.

  2. Or are they supposed to be provided by the libc on your target system?
     Less likely than #1, but possible.


Jeff