Displaying 20 results from an estimated 10000 matches similar to: "[LLVMdev] LLVM_LIB_SEARCH_PATH"
2004 Dec 12
0
[LLVMdev] LLVM_LIB_SEARCH_PATH
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
2004 Dec 12
2
[LLVMdev] LLVM_LIB_SEARCH_PATH
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
2004 Oct 27
2
[LLVMdev] Some Questions about LLVM
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=GB2312" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Yes, I checked that envvar, and it is set.<br>
The error msg when compiling a .c
2004 Dec 13
0
[LLVMdev] LLVM_LIB_SEARCH_PATH
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
2004 Dec 13
2
[LLVMdev] LLVM_LIB_SEARCH_PATH
Chris Lattner wrote:
> 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
2003 Dec 07
0
[LLVMdev] Important change to LLVM makefiles
I have recently built the LLVM suite .. The problem is when I run
llvmgcc( after setting alias to $LLVM )
gcc: installation problem, cannot exec `gccld': No such file or directory
the LLVM_LIB_SEARCH_PATH=..
is set to LLVMGCCDIR/bytecode-libs
Any idea
2004 Oct 25
0
[LLVMdev] Some Questions about LLVM
On Mon, 25 Oct 2004, zhou feng wrote:
> I have some questions about LLVM
> 1. I recently compiled LLVM on my X86 machine correctly. But when I use
> the built LLVm compiling programs(in the getting started guide), I got
> an warning saying can not find library "lc" (something like that). Yet
> LLVM did yeild a execution native code and it runs correctly except with
> a
2003 Dec 06
2
[LLVMdev] Important change to LLVM makefiles
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
2004 Oct 25
5
[LLVMdev] Some Questions about LLVM
hi, all
I have some questions about LLVM
1. I recently compiled LLVM on my X86 machine correctly. But when I use
the built LLVm compiling programs(in the getting started guide), I got
an warning saying can not find library "lc" (something like that). Yet
LLVM did yeild a execution native code and it runs correctly except with
a waring saying something like "__main**"(I
2004 Sep 05
0
[LLVMdev] POST MORTEM: llvm-test changes
> That's weird. What is your default shell that Perl invokes with the
> "system" command. This works fine with bash-2.05b.
In reality :) i use this script in crontab (and run it manually with added
verbose flag):
---8X--------------
#!/bin/sh -
#
if !([ -d /home/wanderer/pkg/build/llvm/night/testresults-X86-FreeBSD ])
then mkdir
2003 Dec 07
2
[LLVMdev] Can you hint on solution to following problem
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
2004 Sep 05
2
[LLVMdev] POST MORTEM: llvm-test changes
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)
>
>
2005 Mar 01
3
[LLVMdev] question about gccld and external libraries
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
2004 Dec 13
0
[LLVMdev] LLVM_LIB_SEARCH_PATH
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/
2004 Dec 14
0
[LLVMdev] User visible changes to llvmgcc and runtime libraries
Hi all LLVM CVS users,
Recently, the LLVM makefiles have changed how runtime libraries are
handled for the C/C++ frontend. Please take the following steps
(assuming 'llvmgccdir' is whatever you normally pass to configure as the
--with-llvmgcdir option):
1. Go into your llvm/runtime directory, and run 'make install-bytecode'.
This will install runtime libraries into
2004 May 03
0
[LLVMdev] Plea for help
Finn S Andersen wrote:
> Sorry to disturb you all, but I simply cannot get
> the linearscan allocator to work. I have upgraded
> llvm to mainline cvs. Everything works until I get
> to llc -regalloc=linearscan or lli -regalloc=linearscan.
>
> I have installed it on redhat 9 and on Fedora Core
> distributions (I even took it as far as to format a new
> partition and
2004 Dec 20
0
[LLVMdev] Compiling FreeType 2.1.9 with LLVM 1.4
On Sun, 2004-12-19 at 20:20, Adam Warner wrote:
> Hi all,
Hi Adam,
>
> I learned of LLVM a couple of days ago:
> <http://groups.google.co.nz/groups?selm=pan.2004.12.18.11.29.33.33249%40consulting.net.nz>
> <http://groups.google.co.nz/groups?th=608e6e38e496f09d>
> (I posted a tail call followup which is missing from the archive)
> Jestingly, LLVM developers
2004 May 03
3
[LLVMdev] Plea for help
Sorry to disturb you all, but I simply cannot get
the linearscan allocator to work. I have upgraded
llvm to mainline cvs. Everything works until I get
to llc -regalloc=linearscan or lli -regalloc=linearscan.
I have installed it on redhat 9 and on Fedora Core
distributions (I even took it as far as to format a new
partition and install Fedora core all over). I have submitted
the bytecode that
2004 Dec 22
3
[LLVMdev] README: Build Environment Changes
LLVMers,
If you're not working from the CVS "head", you can ignore this.
Otherwise, please read it!
I have committed changes to CVS head that require changes to your build
environment. This is part of PR432. The changes involve getting the CFE
to build an executable named llvm-gcc instead of gcc. The hyphenated
name was chosen to be consistent with other LLVM tools, it is also
2004 Jun 24
0
[LLVMdev] Using -noexternals option of NightlyTest.pl
On Thu, 24 Jun 2004, Vladimir Merzliakov wrote:
> 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 think that it's currently a bug that this does not automatically happen.
> I known about new NightlyTest.pl option: -noexternals
> But what I must do for