-
Notifications
You must be signed in to change notification settings - Fork 15.3k
Closed
Labels
bugzillaIssues migrated from bugzillaIssues migrated from bugzillaenhancementImproving things as opposed to bug fixing, e.g. new or missing featureImproving things as opposed to bug fixing, e.g. new or missing featurellvm-toolsAll llvm tools that do not have corresponding tagAll llvm tools that do not have corresponding tag
Description
| Bugzilla Link | 525 |
| Resolution | FIXED |
| Resolved on | Feb 22, 2010 12:54 |
| Version | trunk |
| OS | All |
| Blocks | llvm/llvm-bugzilla-archive#526 |
| Reporter | LLVM Bugzilla Contributor |
Extended Description
A directory in our -L path has a libFoo.so native library that we need to
link. It also contains a libBar.so bytecode library.
Another directory in our -L path has a bytecode version of libFoo.so and a
native version of libBar.so.
What do we do?
llvm-g++ -Wl,-native -shared -o libtest.so test.o -L/foobar -lfoo -L/barfoo
-lbar
/foobar
libFoo.so --native
libBar.so --bytecode
/barfoo
libFoo.so --bytecode
libBar.so --native
Now, it is possible to test for this situation, but even if we know that it is
going to happen, how do we tell gcc or the system linker how to do the
correct thing?
Metadata
Metadata
Assignees
Labels
bugzillaIssues migrated from bugzillaIssues migrated from bugzillaenhancementImproving things as opposed to bug fixing, e.g. new or missing featureImproving things as opposed to bug fixing, e.g. new or missing featurellvm-toolsAll llvm tools that do not have corresponding tagAll llvm tools that do not have corresponding tag