calling from one libfoo.a to another
travis@subspacefield.org
travis@subspacefield.org
Wed Mar 10 22:02:00 GMT 2010
Hello all,
Not sure where to ask this, apologies in advance if this isn't
appropriate. I'll only ask once, so ignoring me or a direct response
will be sufficient.
I'd like to call from one library (libfoo.a) to another (libbar.a) without
directly linking the two. In other words, I'd like to have the symbol
resolved when I link the final executable. I've tried "weak"
attribute, and they work in some cases, like when the caller is not in
a library, but on our platform, when you compile it into libraries, it
gets left undefined... a call to the weak reference will segfault at
run-time (I assume because it's not getting defined before the
I'm just curious if there's an easy way to call from one .a to another
to avoid drastically restructuring our code base.
If this is unclear, please let me know.
--
A Weapon of Mass Construction
My emails do not have attachments; it's a digital signature that your mail
program doesn't understand. | http://www.subspacefield.org/~travis/
If you are a spammer, please email john@subspacefield.org to get blacklisted.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <https://gcc.gnu.org/pipermail/gcc-help/attachments/20100310/9992cd86/attachment.sig>
More information about the Gcc-help
mailing list