Fix for PPC uClibc build

Brent Cook bcook at bpointsys.com
Mon Mar 6 15:00:20 UTC 2006


On Monday 06 March 2006 08:17, Mike Frysinger wrote:
> On Sunday 05 March 2006 22:56, Brent Cook wrote:
> > I'm actually curious about how the automatic test daemon is building
> > PowerPC, because I sure can't get SVN to build properly (tried GCC 3.4.5
> > to 4.1 and various binutils)
>
> i use gcc-3.4.5 and binutils-2.16.1 for just about all my targets
> -mike

The GNU binutils version probably explains why it compiles; I had been using 
various iterations of the Linux binutils branch:

Changes from binutils 2.16.90.0.1:
...
5. Don't allow local symbol to be equated common/undefined symbols (PR
857).
...
I just got SVN+PowerPC to build using this combination, but inet_ntop appears 
to cause a segfault now. BTW, is this a reasonable way of debugging uClibc? I 
just try to chroot with gdb:

[root at pe chroot]# gdb chroot
(gdb) set args ./
(gdb) run
Starting program: /usr/sbin/chroot ./
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)

Program received signal SIGSEGV, Segmentation fault.
0x300bc094 in inet_ntop () from /lib/libc.so.0
(gdb) bt
#0  0x300bc094 in inet_ntop () from /lib/libc.so.0
#1  0x300bc00c in inet_ntop () from /lib/libc.so.0
#2  0x300bc00c in inet_ntop () from /lib/libc.so.0
#3  0x300bc00c in inet_ntop () from /lib/libc.so.0
#4  0x300bc00c in inet_ntop () from /lib/libc.so.0
#5  0x300bc00c in inet_ntop () from /lib/libc.so.0
#6  0x300bc00c in inet_ntop () from /lib/libc.so.0
#7  0x300bc00c in inet_ntop () from /lib/libc.so.0
#8  0x300bc00c in inet_ntop () from /lib/libc.so.0

heh, does this mean that inet_ntop is calling itself recursively, or is GDB 
messing up in its symbol resolver?



More information about the uClibc mailing list