search for: llvm_lib_search_path

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/byteco...

On Sun, 12 Dec 2004, 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&...

gccld: Cannot find linker input file 'crtend.o I have set the LLVM_LIB_SEARCH_PATH ls -l $LLVM_LIB_SEARCH_PATH total 104 -rw-r--r-- 1 muj20 muj20 12788 Dec 7 17:05 crtend.o -rw-r--r-- 1 muj20 muj20 1984 Dec 7 17:05 libc.bc -rw-r--r-- 1 muj20 muj20 120 Dec 7 17:05 libcurses.bc

Chris Lattner wrote: > On Sun, 12 Dec 2004, 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 se...

...d /home/wanderer/pkg/build/llvm/night/build ]) then rm -r /home/wanderer/pkg/build/llvm/night/build ; fi LC_MESSAGES=C export LC_MESSAGES LANG=C export LANG PATH=/sbin:/bin:/usr/sbin:/home/wanderer/pkg/gcc_34/bin:/home/wanderer/pkg/qmtest/bin:/usr/bin:/usr/local/sbin:/usr/local/bin export PATH LLVM_LIB_SEARCH_PATH=/home/wanderer/pkg/llvm_cfe/bytecode-libs export LLVM_LIB_SEARCH_PATH LLVMGCCDIR=/home/wanderer/pkg/llvm_cfe export LLVMGCCDIR LLVM_LIB_SEARCH_PATH=/home/wanderer/pkg/llvm_cfe/bytecode-libs export LLVM_LIB_SEARCH_PATH LD_LIBRARY_PATH=/home/wanderer/pkg/gcc_34/lib export LD_LIBRARY_PATH cd /home...

On Sun, 12 Dec 2004, Jeff Cohen wrote: >> I definitely prefer #1. The only concern I have with it is that this makes >> it impossible to move the llvmgcc install directory once it is built (tools >> would not look in the correct directories). >> > This is a very big concern. Users of LLVM generally do not build llvmgcc -- > are actively discouraged from building

...> bytecode-libs directory. It already passes in -L options for > "lib/gcc/<target>/3.4-llvm/" and others, so this should be pretty easy. I agree that this is the right way to go; it's been on my mind for some time, but I've never explored the possibility. I think LLVM_LIB_SEARCH_PATH should still exist, sort of as a parallell to LD_LIBRARY_PATH, but the compiler driver should be able to pass the -L option to gccld/llvm-ld/whatever to include the compiler runtime libraries. Speaking of which, is there a reason not to install the libraries inside of LLVMGCCDIR/lib? That'...

That's weird. What is your default shell that Perl invokes with the "system" command. This works fine with bash-2.05b. Reid. On Sun, 2004-09-05 at 10:01, Vladimir Merzliakov wrote: > > x86 FreeBSD: > > * hasn't run with changes yet > > I manually start script. I use this options (+ -verbose now for testing) > >

On Sun, 12 Dec 2004, John T. Criswell wrote: > Speaking of which, is there a reason not to install the libraries inside of > LLVMGCCDIR/lib? That's where libstdc++ lives, and it's already in the > llvm-gcc's search path? That is an excellent point, I don't think there is any reason not to just install them into gcc/lib. -Chris -- http://nondot.org/sabre/

...r 2 gmake[1]: Leaving directory `/llvm/build/unittests' gmake: *** [all] Error 1 # Again, we can see that it is looking for "/llvm/build/unittests/lib/libLLVMSupport.a" library which is actually present in "/llvm/build/Release+Asserts/lib/libLLVMSupport.a" does setting up LLVM_LIB_SEARCH_PATH help ? # echo $LLVM_LIB_SEARCH_PATH /llvm/build/Release+Asserts/lib/ ===> Is it correct ? # Thanks -- View this message in context: http://llvm.1065342.n5.nabble.com/llvm-config-is-broken-tp50418p50435.html Sent from the LLVM - Dev mailing list archive at Nabble.com.

....cpp_17E02520_F7D322F615PrintStackTraceEv+0x1f)[0x835c40f] /lib/tls/libc.so.6(abort+0x1d2)[0x201302] lli[0x8116dbb] make[1]: *** [evenodd.exe] Aborted The 'pthread_once' is located in the native library binary file: /usr/lib/libpthread.a. I've also included the path to the library in LLVM_LIB_SEARCH_PATH environment variable. When LLVM tool gccld is linking above program, it doesn't complain that it cannot find the function or library. Any ideas? ============================================================= Henrik Bach LLVM Open Source Developer e-mail: henrik_bach_llvm at hotmail.com ===...

...lvm is /home/my/llvm/llvm-bin/ and llvmgcc dir is /home/my/llvm/llvm/llvm-gcc and the configure option is --prefix=/home/my/llvm/llvm-bin/ --enable-jit --llvmgccdir=/home/my/llvm/llvm/llvm-gcc </pre> </blockquote> <pre wrap=""><!----> Make sure you set your LLVM_LIB_SEARCH_PATH envvar, as specified in the getting started guide: <a class="moz-txt-link-freetext" href="http://llvm.cs.uiuc.edu/docs/GettingStarted.html#environment">http://llvm.cs.uiuc.edu/docs/GettingStarted.html#environment</a> </pre> <blockquote type="cite&q...

...gt; /home/wanderer/pkg/build/llvm/night/build ; fi > > LC_MESSAGES=C > export LC_MESSAGES > > LANG=C > export LANG > > PATH=/sbin:/bin:/usr/sbin:/home/wanderer/pkg/gcc_34/bin:/home/wanderer/pkg/qmtest/bin:/usr/bin:/usr/local/sbin:/usr/local/bin > export PATH > > LLVM_LIB_SEARCH_PATH=/home/wanderer/pkg/llvm_cfe/bytecode-libs > export LLVM_LIB_SEARCH_PATH > > LLVMGCCDIR=/home/wanderer/pkg/llvm_cfe > export LLVMGCCDIR > > LLVM_LIB_SEARCH_PATH=/home/wanderer/pkg/llvm_cfe/bytecode-libs > export LLVM_LIB_SEARCH_PATH > > LD_LIBRARY_PATH=/home/wanderer/pk...

...can't find the >>libraries, like "c" or "crtend". [1] > > > Did you install the bytecode libraries into the C/C++ frontend lib > directory? > thanks for the pointer. Yes I've done that, but in the new shell session I apparently forgot to set the LLVM_LIB_SEARCH_PATH. now gccld isn't complaining anymore but the interpreter doesn't seem to like it still: ERROR: Program used external function 'clock_gettime' which could not be resolved! lli((anonymous namespace)::PrintStackTrace()+0x1a)[0x862a53e] lli((anonymous namespace)::SignalHandler(int)+...

hi, I'm really new to llvm. I've successfully bootstrapped llvm-14 on my system and am able to successfully compile c code to llvm. the problem is now that gccld is complaining that it can't find the libraries, like "c" or "crtend". [1] all is fine, if I just use intrinsified functions like printf and friends, but I want to use the clock_gettime function and

...ly a bug that this does not automatically happen. > I known about new NightlyTest.pl option: -noexternals > But what I must do for enable it Are you using the NightlyTest.pl file? To run the tester I don't use gmake directly at all. Instead, I have this in my crontab: 5 3 * * * LLVM_LIB_SEARCH_PATH=/home/vadve/lattner/local/x86/llvm-gcc/bytecode-libs $HOME/llvm/utils/NightlyTest.pl -parallel -enable-linscan /home/vadve/shared/PublicCVS $HOME/buildtest-X86 $HOME/cvs/testresults-X86 When run like this, you can use -noexternals as you wish. -Chris -- http://llvm.cs.uiuc.edu/ http://www.nondo...

At this moment I use "gmake TEST=nightly" command line to run night tester What I must specific and where to disable SPEC run (i don't have it) I known about new NightlyTest.pl option: -noexternals But what I must do for enable it Vladimir

> Are you using the NightlyTest.pl file? To run the tester I don't use > gmake directly at all. Instead, I have this in my crontab: > > 5 3 * * * LLVM_LIB_SEARCH_PATH=/home/vadve/lattner/local/x86/llvm-gcc/bytecode-libs $HOME/llvm/utils/NightlyTest.pl -parallel -enable-linscan /home/vadve/shared/PublicCVS $HOME/buildtest-X86 $HOME/cvs/testresults-X86 > > When run like this, you can use -noexternals as you wish. Thank you fo information. I will used this c...

...some optimization. I am running the following script - #!/bin/bash while read line; do clang -S -emit-llvm -DNDEBUG -DSPEC_CPU -o $line'.o' $line'.c' done < files.txt while read line; do opt -block-placement $line'.o' -o $line'.o' done < files.txt #export LLVM_LIB_SEARCH_PATH=/usr/lib llvm-link *.o -o out.o.linked llc out.o.linked gcc out.o.linked.s -o hmmer **files.txt contains the name of the source files of the hmmer benchmark. But "llc" gives me the following error - /tmp/ccVq4r6d.o: In function `PostprocessSignificantHit': out.o.linked:(.text+0xc1f...

Please read this if you're working out of LLVM CVS: I just checked in a change to the makefiles to stop using -fshort-enum when building LLVM. This flag enables a trivial optimization, but causes the code generated by the G++ compiler to not match the standard C++ ABI. Because of this, the presence of the flag makes it more difficult to link LLVM libraries to external source bases, and it