egcs1.1.2 lnx cross ppc newuser followup

egcs1.1.2 lnx cross ppc newuser followup

[Jeffrey Perry]

I tried some advice I got earlier. I recompiled binutils without --with-newlib 
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.

configure:581: checking host system type
configure:604: checking build system type
configure:630: checking for ppc-rtems-eabi-ar
configure:661: checking for ppc-rtems-eabi-ranlib
configure:736: checking for gcc
configure:813: checking whether we are using GNU C
configure:822: /home/jperry/cross-compile-linux-egcs112-objdir/gcc/xgcc 
-B/home/jperry/cross-compile-linux-egcs112-objdir/gcc/ -E conftest.c
configure:837: checking whether /home/jperry/cross-compile-linux-egcs112-objdir
/gcc/xgcc -B/home/jperry/cross-compile-linux-egcs112-objdir/gcc/ accepts -g
configure:866: checking for POSIXized ISC
configure:904: checking for a BSD compatible install
configure:963: checking how to run the C preprocessor
configure:984: /home/jperry/cross-compile-linux-egcs112-objdir/gcc/xgcc 
-B/home/jperry/cross-compile-linux-egcs112-objdir/gcc/ -E  conftest.c >
/dev/null 2>conftest.out
configure:1027: checking for sys/file.h
configure:1037: /home/jperry/cross-compile-linux-egcs112-objdir/gcc/xgcc 
-B/home/jperry/cross-compile-linux-egcs112-objdir/gcc/ -E  conftest.c >
/dev/null 2>conftest.out
configure:1027: checking for sys/param.h
configure:1037: /home/jperry/cross-compile-linux-egcs112-objdir/gcc/xgcc 
-B/home/jperry/cross-compile-linux-egcs112-objdir/gcc/ -E  conftest.c >
/dev/null 2>conftest.out
configure:1027: checking for stdlib.h
configure:1037: /home/jperry/cross-compile-linux-egcs112-objdir/gcc/xgcc 
-B/home/jperry/cross-compile-linux-egcs112-objdir/gcc/ -E  conftest.c >
/dev/null 2>conftest.out
configure:1027: checking for string.h
configure:1037: /home/jperry/cross-compile-linux-egcs112-objdir/gcc/xgcc 
-B/home/jperry/cross-compile-linux-egcs112-objdir/gcc/ -E  conftest.c >
/dev/null 2>conftest.out
configure:1027: checking for unistd.h
configure:1037: /home/jperry/cross-compile-linux-egcs112-objdir/gcc/xgcc 
-B/home/jperry/cross-compile-linux-egcs112-objdir/gcc/ -E  conftest.c >
/dev/null 2>conftest.out
configure:1584: checking whether the C compiler (/home/jperry/cross-compile-lin
ux-egcs112-objdir/gcc/xgcc -B/home/jperry/cross-compile-linux-egcs112-objdir/gc
c/ -g -O2 ) works
configure:1598: /home/jperry/cross-compile-linux-egcs112-objdir/gcc/xgcc 
-B/home/jperry/cross-compile-linux-egcs112-objdir/gcc/ -o conftest -g -O2   
conftest.c  1>&5
/usr/local/ppc-rtems-eabi/bin/ld: warning: cannot find entry symbol _start; 
defaulting to 01800074
/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__'
collect2: ld returned 1 exit status
configure: failed program was:
#line 1594 "configure"
#include "confdefs.h"
main(){return(0);}

Re: egcs1.1.2 lnx cross ppc newuser followup

[Jeffrey A Law]

  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

Re: egcs1.1.2 lnx cross ppc newuser followup

[David Edelsohn]

>>>>> Jeffrey A Law writes:

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

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

      I know that GCC/EGCS explicitly provides those symbols in assembly
file "crt" bookends for eABI.  I thought that Linux provided its own
crti/crtn bookends for the link step.  The LinuxPPC configuration seems to
specifically look for crt1.o, crti.o, crtbegin.o, crtend.o, crtn.o.  It
even looks for ecrti.o and ecrtn.o if -mnewlib is used.

David

Re: egcs1.1.2 lnx cross ppc newuser followup

[Jeffrey Perry]

Hmm...

I know there are linker scripts now installed in /usr/local/ppc-rtems-eabi/libs
/ldscripts
(binutils 2.9.1 installed them)

I really don't know anything about them.
I did poke around and find the symbols in target formatted object files.

 ppc-rtems-eabi-nm ecrtn.o | grep -i sdata
00000000 G __SDATA2_END__
00000000 G __SDATA_END__

ppc-rtems-eabi-nm ecrti.o | grep -i sdata
00000000 G __SDATA2_START__
00000000 G __SDATA_START__

Now what? Why couldn't it find these, they were in gcc/

> >>>>> Jeffrey A Law writes:
> 
> Jeff> 1. Is is possible these symbols are supposed to be defiend by the linker
> Jeff> via a linker script?   I believe this is the case.
> 
> Jeff> 2. Or are they supposed to be provided by the libc on your target system?
> Jeff> Less likely than #1, but possible.
> 
>       I know that GCC/EGCS explicitly provides those symbols in assembly
> file "crt" bookends for eABI.  I thought that Linux provided its own
> crti/crtn bookends for the link step.  The LinuxPPC configuration seems to
> specifically look for crt1.o, crti.o, crtbegin.o, crtend.o, crtn.o.  It
> even looks for ecrti.o and ecrtn.o if -mnewlib is used.
> 
> David
> 

Re: egcs1.1.2 lnx cross ppc newuser followup

[Jeffrey A Law]

  In message < 9904022256.AA25737@dogbert >you write:
  > Hmm...
  > 
  > I know there are linker scripts now installed in /usr/local/ppc-rtems-eabi/
  > libs
  > /ldscripts
  > (binutils 2.9.1 installed them)
  > 
  > I really don't know anything about them.
  > I did poke around and find the symbols in target formatted object files.
  > 
  >  ppc-rtems-eabi-nm ecrtn.o | grep -i sdata
  > 00000000 G __SDATA2_END__
  > 00000000 G __SDATA_END__
  > 
  > ppc-rtems-eabi-nm ecrti.o | grep -i sdata
  > 00000000 G __SDATA2_START__
  > 00000000 G __SDATA_START__
  > 
  > Now what? Why couldn't it find these, they were in gcc/
You're going to have to debug it.  ie, why are those files not linked in? 
Again, it could well be the linker script or some other issue.


jeff

Re: egcs1.1.2 lnx cross ppc newuser followup

[David Edelsohn]

>>>>> Jeffrey A Law writes:

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

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

      I know that GCC/EGCS explicitly provides those symbols in assembly
file "crt" bookends for eABI.  I thought that Linux provided its own
crti/crtn bookends for the link step.  The LinuxPPC configuration seems to
specifically look for crt1.o, crti.o, crtbegin.o, crtend.o, crtn.o.  It
even looks for ecrti.o and ecrtn.o if -mnewlib is used.

David

egcs1.1.2 lnx cross ppc newuser followup

[Jeffrey Perry]

I tried some advice I got earlier. I recompiled binutils without --with-newlib 
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.

configure:581: checking host system type
configure:604: checking build system type
configure:630: checking for ppc-rtems-eabi-ar
configure:661: checking for ppc-rtems-eabi-ranlib
configure:736: checking for gcc
configure:813: checking whether we are using GNU C
configure:822: /home/jperry/cross-compile-linux-egcs112-objdir/gcc/xgcc 
-B/home/jperry/cross-compile-linux-egcs112-objdir/gcc/ -E conftest.c
configure:837: checking whether /home/jperry/cross-compile-linux-egcs112-objdir
/gcc/xgcc -B/home/jperry/cross-compile-linux-egcs112-objdir/gcc/ accepts -g
configure:866: checking for POSIXized ISC
configure:904: checking for a BSD compatible install
configure:963: checking how to run the C preprocessor
configure:984: /home/jperry/cross-compile-linux-egcs112-objdir/gcc/xgcc 
-B/home/jperry/cross-compile-linux-egcs112-objdir/gcc/ -E  conftest.c >
/dev/null 2>conftest.out
configure:1027: checking for sys/file.h
configure:1037: /home/jperry/cross-compile-linux-egcs112-objdir/gcc/xgcc 
-B/home/jperry/cross-compile-linux-egcs112-objdir/gcc/ -E  conftest.c >
/dev/null 2>conftest.out
configure:1027: checking for sys/param.h
configure:1037: /home/jperry/cross-compile-linux-egcs112-objdir/gcc/xgcc 
-B/home/jperry/cross-compile-linux-egcs112-objdir/gcc/ -E  conftest.c >
/dev/null 2>conftest.out
configure:1027: checking for stdlib.h
configure:1037: /home/jperry/cross-compile-linux-egcs112-objdir/gcc/xgcc 
-B/home/jperry/cross-compile-linux-egcs112-objdir/gcc/ -E  conftest.c >
/dev/null 2>conftest.out
configure:1027: checking for string.h
configure:1037: /home/jperry/cross-compile-linux-egcs112-objdir/gcc/xgcc 
-B/home/jperry/cross-compile-linux-egcs112-objdir/gcc/ -E  conftest.c >
/dev/null 2>conftest.out
configure:1027: checking for unistd.h
configure:1037: /home/jperry/cross-compile-linux-egcs112-objdir/gcc/xgcc 
-B/home/jperry/cross-compile-linux-egcs112-objdir/gcc/ -E  conftest.c >
/dev/null 2>conftest.out
configure:1584: checking whether the C compiler (/home/jperry/cross-compile-lin
ux-egcs112-objdir/gcc/xgcc -B/home/jperry/cross-compile-linux-egcs112-objdir/gc
c/ -g -O2 ) works
configure:1598: /home/jperry/cross-compile-linux-egcs112-objdir/gcc/xgcc 
-B/home/jperry/cross-compile-linux-egcs112-objdir/gcc/ -o conftest -g -O2   
conftest.c  1>&5
/usr/local/ppc-rtems-eabi/bin/ld: warning: cannot find entry symbol _start; 
defaulting to 01800074
/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__'
collect2: ld returned 1 exit status
configure: failed program was:
#line 1594 "configure"
#include "confdefs.h"
main(){return(0);}

Re: egcs1.1.2 lnx cross ppc newuser followup

[Jeffrey A Law]

  In message < 9904022256.AA25737@dogbert >you write:
  > Hmm...
  > 
  > I know there are linker scripts now installed in /usr/local/ppc-rtems-eabi/
  > libs
  > /ldscripts
  > (binutils 2.9.1 installed them)
  > 
  > I really don't know anything about them.
  > I did poke around and find the symbols in target formatted object files.
  > 
  >  ppc-rtems-eabi-nm ecrtn.o | grep -i sdata
  > 00000000 G __SDATA2_END__
  > 00000000 G __SDATA_END__
  > 
  > ppc-rtems-eabi-nm ecrti.o | grep -i sdata
  > 00000000 G __SDATA2_START__
  > 00000000 G __SDATA_START__
  > 
  > Now what? Why couldn't it find these, they were in gcc/
You're going to have to debug it.  ie, why are those files not linked in? 
Again, it could well be the linker script or some other issue.


jeff

Re: egcs1.1.2 lnx cross ppc newuser followup

[Jeffrey Perry]

Hmm...

I know there are linker scripts now installed in /usr/local/ppc-rtems-eabi/libs
/ldscripts
(binutils 2.9.1 installed them)

I really don't know anything about them.
I did poke around and find the symbols in target formatted object files.

 ppc-rtems-eabi-nm ecrtn.o | grep -i sdata
00000000 G __SDATA2_END__
00000000 G __SDATA_END__

ppc-rtems-eabi-nm ecrti.o | grep -i sdata
00000000 G __SDATA2_START__
00000000 G __SDATA_START__

Now what? Why couldn't it find these, they were in gcc/

> >>>>> Jeffrey A Law writes:
> 
> Jeff> 1. Is is possible these symbols are supposed to be defiend by the linker
> Jeff> via a linker script?   I believe this is the case.
> 
> Jeff> 2. Or are they supposed to be provided by the libc on your target system?
> Jeff> Less likely than #1, but possible.
> 
>       I know that GCC/EGCS explicitly provides those symbols in assembly
> file "crt" bookends for eABI.  I thought that Linux provided its own
> crti/crtn bookends for the link step.  The LinuxPPC configuration seems to
> specifically look for crt1.o, crti.o, crtbegin.o, crtend.o, crtn.o.  It
> even looks for ecrti.o and ecrtn.o if -mnewlib is used.
> 
> David
> 

Re: egcs1.1.2 lnx cross ppc newuser followup

[Jeffrey A Law]

  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