[prev in list] [next in list] [prev in thread] [next in thread] 

List:       llvm-dev
Subject:    [LLVMdev] Revised patch to make gccld link native .so's
From:       Adam Treat <manyoso () yahoo ! com>
Date:       2005-02-21 6:46:57
Message-ID: 200502210146.57194.manyoso () yahoo ! com
[Download RAW message or body]


Here is a revised patch after some suggestions:

1.   Removed extraneous changes (the white space changes that are -/+ 
whitespace), and the commented out code.
2.   Keep the warning for linking dynamic libraries in LinkLibraries.cpp

I still don't have a good solution to the problem of -L paths that include 
bytecode versions of the native libraries we're trying to link.  Consider the 
following situation...  

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?
 

["linker.diff.gz" (application/x-gzip)]

[prev in list] [next in list] [prev in thread] [next in thread]