argp support in uClibc as separate shared object
Carmelo AMOROSO
carmelo.amoroso at st.com
Mon Oct 4 09:08:53 UTC 2010
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Folks,
time ago we added argp support into ST branch of uClibc because it is
used by some elfutils tests and prelink tool that we build (we did not
want to modify them to use getopt instead of argp). So we ported the
argp support from glibc into uClibc and modified it accordingly to fit
into the uClibc build system. We did not upstream this work because it
is a feature that is almost never used, so it does not worth to add this
extra code into uClibc (I discussed this with Bernhard)
If some of you are going to use prelink, this support will be actually
required and should have our patches. I was thinking to create a
"libuargp" to keep the argp code in a separate shared object avoiding to
populate the libc.so with seldom used functions.
So "libuargp" would be transparently linkedby using the AS_NEEDED
directive in the linker script libc.so for those applications that
actually requires argp symbols (as for libubacktrace).
What do you think ?
Regards,
Carmelo
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAkypmaUACgkQoRq/3BrK1s8IXQCgg6OU6OeYBqyuxH9XOzkzg7dT
b+0An3iRnrISvoCcc/4P4IRAyJT/gLTM
=PDpH
-----END PGP SIGNATURE-----
More information about the uClibc
mailing list