| Newsgroups |
gmane.linux.lsb.discuss |
| Message-ID |
<[email protected]> |
On Sun, 6 Apr 2003, Mike Hearn wrote:
> Hi,
>
> I'm trying to figure out how to use the LSB CC developer kit to force a
> little hello world GTK app to use the LSB symvers. A few things confuse
> me:
>
> 1) If I run nm on my actual libc, I can see various symbols that have
> versions. If I run it on the stub libc provideded by lsbdev-base, I
> don't see any symvers at all. How does this work?
I _think_ those are the alternate version symbols you are seeing. If a symbol
only has 1 version, you don't normally see it. Readelf might give more
info.
> 2) In theory, the lsbcc program should statically link anything that
> isn't needed. Attempting to build an LSB gtk1.2 program that prints
> Hello World and inits GTK fails with lots of unknown internal Xlib
> symbols.
These are usually caused by using X extensions which have not been included
in the LSB. Any idea which extension you are using? (beside render?)
> Basically, I'm wondering what the flags to GCC would be to make it use
> the LSB stub libraries so I can avoid using lsbcc and just dynamically
> link gtk.
man lsbcc will show several env variable which can be set to cause a lot
of debug output. One of the bits will show the gcc line that gets used.
Stuart
[email protected] Free Standards Group
Lead Developer, Written Specification Linux Standard Base
1024D/37A79149: 0791 D3B8 9A4C 2CDC A31F
BD03 0A62 E534 37A7 9149