Sebastian Huber sebastian.huber@embedded-brains.de
Fri Aug 11 09:49:00 GMT 2017

• Previous message (by thread): [PATCH] Also disallow global alias of common symbol
• Next message (by thread): Static linking on 64-bit PowerPC ELFv2
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

Hello,

I recently added 64-bit PowerPC for RTEMS using the ELFv2 ABI. On RTEMS, 
the applications are statically linked with the operating system. I am 
now a bit surprised be a linker behaviour. I have a big library 
containing a network stack with many features. On other targets the 
linker just picks individual objects from the library to resolve the 
dependencies. However, on the 64-bit PowerPC the linker seems to pull in 
the complete library somehow. I see in the linker map file lines like this:

./libbsd.a(utils.c.18.o)      (print_string)

The applications has no direct or indirect references to print_string, 
however, the utils.c.18.o is still included in the link process. This in 
turn leads to unresolved references. Is this the expected behaviour on 
64-bit PowerPC?

-- 
Sebastian Huber, embedded brains GmbH

Address : Dornierstr. 4, D-82178 Puchheim, Germany
Phone   : +49 89 189 47 41-16
Fax     : +49 89 189 47 41-09
E-Mail  : sebastian.huber@embedded-brains.de
PGP     : Public key available on request.

Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.

---

• Previous message (by thread): [PATCH] Also disallow global alias of common symbol
• Next message (by thread): Static linking on 64-bit PowerPC ELFv2
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

More information about the Binutils mailing list