[LLVMdev] LLVM_LIB_SEARCH_PATH

[Vikram S. Adve]

I'm very much in favor of option 1.  In general, I think we should 
avoid the need for users to set special environment variables for 
running llvm tools -- it creates a non-obvious, hidden dependence 
that's often a pain to track down.

Specifically in this case, it seems to me that the env. variable is 
unnecessary anyway since llvm-link already takes path choices on the 
command line.  These could be used if a user wants to specify locations 
other than any default ones inferred at configuration time.

Incidentally, I don't think we should assume that users configure with 
--with-llvmgccdir.  Some users may not want to use or install llvm-gcc.


On Dec 12, 2004, at 4:54 PM, Reid Spencer wrote:

> Hello,
>
> I need to solicit your opinion about something.
>
> I'm toying with the idea of getting rid of LLVM_LIB_SEARCH_PATH. Right
> now the linkers will use this environment variable if it specifies a
> single directory. It will look in that directory to find libraries when
> things like -lc or -lcrtend are specified on the command line. Right
> now, the only known place this is useful to set to is the CFE's
> install/bytecode-libs directory. However, the configure script can make
> that path available to us already because LLVM requires configuring 
> with
> --with-llvmgccdir=... So, it is my understanding that current usage of
> LLVM_LIB_SEARCH_PATH is redundant with already available information
> from the configure script.
>
> Does anyone put anything *other* than CFE/install/bytecode-libs in 
> their
> LLVM_LIB_SEARCH_PATH? Does anyone expect it to actually be a colon
> separated list of path names to be searched (its not interpreted that
> way currently)?
>
> I see two options:
>
> 1. Get rid of LLVM_LIB_SEARCH_PATH and just have the linker "know"
>    about the bytecode-libs directory if --with-llvmgccdir was
>    specified to configure.
>
> 2. Fully support LLVM_LIB_SEARCH_PATH as a colon separated path list
>    to search for bytecode archives and files. In this case their would
>    be no need to specify the bytecode-libs directory, it would be
>    included already.
>
> Which do you like?
> _______________________________________________
> LLVM Developers mailing list
> LLVMdev at cs.uiuc.edu         http://llvm.cs.uiuc.edu
> http://mail.cs.uiuc.edu/mailman/listinfo/llvmdev