[LLVMbugs] [PATCH] Remove useless workaround from llvm-config

Reid Spencer reid at x10sys.com
Fri Mar 24 11:24:20 PST 2006


On Fri, 2006-03-24 at 13:51 -0500, Eric Kidd wrote:
> Hmm. I'm really concerned about those cyclic dependencies, especially  
> among the *.a files--we're just asking for nasty link-time trouble.  
> My workarounds seem to be sufficient for some cases (MacOS X linker,  
> out-of-tree builds), but not for others.

Yes, I agree. I would like to see if LLVM's code can be rearranged so
there are zero cycles. That of course, will take some redesign and a lot
of conversation with Chris.
> 
> Is your build clean?

yes.

> I don't have LinkInInterpreter() yet. This was added yesterday  
> afternoon, right? 

Yes.

> Because in my day-old tree, I can still produce a  
> working HowToUseJIT.cpp without any LLVMInterpreter.o at all, which  
> seems desirable.

Okay.

> The new "LinkInInterpreter/LinkInJIT" stuff should probably be  
> conditionalized on TARGET_HAS_JIT so we can pull in one or the other  
> intelligently.

Yes, it should.

> 
> > It looks like llvm-config is not providing the system libraries.
> 
> Yeah, there's no clean place for me to get that information right  
> now--LLVM mixes together system libraries and libtool-specific stuff,  
> the later of which arguably shouldn't be in llvm-config's output. I  
> can probably fix this.

Okay. If you need any help from Makefiles, just let me know.

> But for now, it looks like you need '-lpthread -ldl'. Try:
> 
>    g++ `llvm-config --ldflags` -o HowToUseJIT HowToUseJIT.o \
>      `llvm-config --libs engine bcreader scalaropts interpreter` - 
> lpthread -ldl
> 
> That should get you very close.

Yes, that gets it down to just: 

/proj/llvm/llvm2/include/llvm/ExecutionEngine/Interpreter.h:35:
undefined reference to `llvm::LinkInInterpreter()'

> Personally, if the 1.7 release is close, I'd prefer to use the  
> existing Makefile.rules logic for in-tree builds.

Yes, we wouldn't replace it unless llvm-config was working perfectly in
all cases, and maybe not even then (impacts users too).

> I'm sorry you're having so much trouble, and I wish I could do more  
> to help. :-( We'll figure all this out next week.

No worries. Talk to you next week.

Reid
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
URL: <http://lists.llvm.org/pipermail/llvm-bugs/attachments/20060324/ccec788b/attachment.sig>


More information about the llvm-bugs mailing list