Displaying 20 results from an estimated 8000 matches similar to: "[LLVMdev] Potential breakage in llvm-gcc's ./configure"
2008 Mar 24
0
[LLVMdev] Potential breakage in llvm-gcc's ./configure
>
> ./configure in the llvm package will work on my amd64 machine
> with this command line:
>
> ./configure --prefix=$HOME --enable-optimized \
> --build=i686-pc-linux-gnu CC=gcc-4.2 CXX=g++-4.2
>
> Note that the CC and CXX flags are set on the command line, not as
> environment variables - trying to submit them via the environment got me
> all kinds of
2008 Mar 23
0
[LLVMdev] Potential breakage in llvm-gcc's ./configure
Just a quick heads-up:
The ./configure in the llvm 2.2 package will work on my amd64 machine
with this command line:
./configure --prefix=$HOME --enable-optimized \
--build=i686-pc-linux-gnu CC=gcc-4.2 CXX=g++-4.2
Note that the CC and CXX flags are set on the command line, not as
environment variables - trying to submit them via the environment got me
all kinds of breakage.
Also not that this
2008 Mar 30
2
[LLVMdev] Compiling llvm-gcc on amd64 with 32 bits: assembler still carps
Hi all,
I managed to navigate around all those issues with environment variables
and such. llvm itself now builds and checks just fine, but I can't get
llvm-gcc to compile.
Trying to 'make' from .../gcc gives me:
./xgcc -B./ -B/home/jo/i686-pc-linux-gnu/bin/
-isystem /home/jo/i686-pc-linux-gnu/include
-isystem /home/jo/i686-pc-linux-gnu/sys-include
-L/home/jo/llvm-gcc-wrk/gcc/../ld
2008 Mar 30
0
[LLVMdev] Compiling llvm-gcc on amd64 with 32 bits: assembler still carps
It shoudl work fine if you set CC right and use --build --target
--host == i686-pc-linux-gnu
On Sun, Mar 30, 2008 at 10:40 AM, Joachim Durchholz <jo at durchholz.org> wrote:
> Hi all,
>
> I managed to navigate around all those issues with environment variables
> and such. llvm itself now builds and checks just fine, but I can't get
> llvm-gcc to compile.
>
>
2008 Mar 30
1
[LLVMdev] Compiling llvm-gcc on amd64 with 32 bits: assembler still carps
Hello, Joachim
> This assembler was configured for a target of `x86_64-linux-gnu'.
Hrm, try to check, how 'as' is invoked by llvm-gcc, you need jut to run
the mentioned cmdline 'by hands':
./xgcc -B./ -B/home/jo/i686-pc-linux-gnu/bin/
-isystem /home/jo/i686-pc-linux-gnu/include
-isystem /home/jo/i686-pc-linux-gnu/sys-include
-L/home/jo/llvm-gcc-wrk/gcc/../ld -O2 -DIN_GCC
2008 Mar 30
2
[LLVMdev] Compiling llvm-gcc on amd64 with 32 bits: assembler still carps
To clarify,
configure --host=i686-pc-linux-gnu --target=i686-pc-linux-gnu
--target=i686-pc-linux-gnu
I do this all the time on my 4 core amd64 box and it works fine.
On Sun, Mar 30, 2008 at 12:22 PM, Daniel Berlin <dberlin at dberlin.org> wrote:
> It shoudl work fine if you set CC right and use --build --target
>
> --host == i686-pc-linux-gnu
>
>
>
> On Sun, Mar 30,
2008 Mar 24
0
[LLVMdev] Potential breakage in llvm-gcc's ./configure
> This is close to a showstopper for integrating an llvm-gcc bootstrap
> into the nightly tester. The llvm-gcc ./configure needs to be called
> very differently from the llvm ./configure, and keeping two sets of
> options is Not Worth The Trouble, at least IMHO.
So you didn't like the suggestion of having the configure for llvm-gcc set
via an environment variable? That avoids
2008 Mar 20
3
[LLVMdev] Just got bitten by accidentally using the wrong gcc
Hi all,
I just forgot to ./configure with CC=gcc-4.2 CXX=g++-4.2, getting the
(broken-for-LLVM) gcc-4.1 as a compiler.
The error message that I got was this:
make[1]: Entering directory `/home/jo/llvm-wrk/lib/VMCore'
make[1]: *** No rule to make target
`/home/jo/llvm-wrk/Release/bin/tblgen', needed by
`/home/jo/llvm-wrk/lib/VMCore/Release/Intrinsics.gen.tmp'. Stop.
2006 Mar 02
4
[LLVMdev] Re: Re: New GCC4-based C/C++/ObjC front-end for LLVM
On Thu, 2 Mar 2006, Vladimir Prus wrote:
>>> The instructions seem to have one path wrong. It says to get:
>>
>> I'll put together a tarball today. That will be easier than dealing with
>> a patch, and it will include a bunch of bugfixes since the previous email.
> Further into process, I get this error:
> In file included from
2008 Mar 20
0
[LLVMdev] Just got bitten by accidentally using the wrong gcc
On Mar 20, 2008, at 3:00 PM, Joachim Durchholz wrote:
> Hi all,
>
> I just forgot to ./configure with CC=gcc-4.2 CXX=g++-4.2, getting the
> (broken-for-LLVM) gcc-4.1 as a compiler.
> The error message that I got was this:
> make[1]: Entering directory `/home/jo/llvm-wrk/lib/VMCore'
> make[1]: *** No rule to make target
> `/home/jo/llvm-wrk/Release/bin/tblgen',
2008 Mar 24
2
[LLVMdev] Potential breakage in llvm-gcc's ./configure
Am Montag, den 24.03.2008, 12:06 -0700 schrieb Tanya M. Lattner:
> > This is close to a showstopper for integrating an llvm-gcc bootstrap
> > into the nightly tester. The llvm-gcc ./configure needs to be called
> > very differently from the llvm ./configure, and keeping two sets of
> > options is Not Worth The Trouble, at least IMHO.
>
> So you didn't like the
2008 Mar 24
0
[LLVMdev] Potential breakage in llvm-gcc's ./configure
Hello, Joachim
> Hm. For some reason, ld kept searching the wrong (64-bit) library paths
> when trying to link the 32-bit results.
Hrm. This looks like to be old story about 'lib vs lib32 vs lib64'
directories in different distributions. Almost every of them patch gcc
inside their packages to provide valid library paths.
Look for example, here:
2008 Nov 18
5
[LLVMdev] llvm-gcc compilation error: BUILT_IN_ADJUST_TRAMPOLINE undeclared
llvm-gcc 2.4 doesn't seem to compile; what is wrong?
This is my first attempt to compile llvm-gcc.
The llvm core compiled without problems.
$ uname -a
Linux ygramoel 2.6.26.5-45.fc9.x86_64 #1 SMP Sat Sep 20 03:23:12 EDT 2008
x86_64 x86_64 x86_64 GNU/Linux
$ gcc -v
...
gcc version 4.3.0 20080428 (Red Hat 4.3.0-8) (GCC)
$ svn co
2006 Mar 07
0
[LLVMdev] Re: Re: Re: New GCC4-based C/C++/ObjC front-end for LLVM
Chris Lattner wrote:
> On Thu, 2 Mar 2006, Vladimir Prus wrote:
>>>> The instructions seem to have one path wrong. It says to get:
>>>
>>> I'll put together a tarball today. That will be easier than dealing
>>> with a patch, and it will include a bunch of bugfixes since the previous
>>> email.
>> Further into process, I get this error:
2008 Mar 25
0
[LLVMdev] Potential breakage in llvm-gcc's ./configure
Hi Jo,
> No, that was written under the assumption that passing in CC and CXX
> via env variables wouldn't work. Things work now, so that assumption
> is obviously wrong.
>
> I still don't like environment variables. They tend to remain in
> effect long after I forgot that I set them, creating all sorts of
> hassle. In fact I suspect I already fell prey to this,
2008 Oct 02
1
[LLVMdev] build broken (a different way)
I get the output below on Ubuntu Hardy on ia32 from svn 56984.
John
make[2]: Entering directory `/home/regehr/llvm-gcc/build/gcc'
/home/regehr/llvm-gcc/build/./gcc/xgcc
-B/home/regehr/llvm-gcc/build/./gcc/ -B/home/regehr/i686-pc-linux-gnu/bin/
-B/home/regehr/i686-pc-linux-gnu/lib/ -isystem
/home/regehr/i686-pc-linux-gnu/include -isystem
/home/regehr/i686-pc-linux-gnu/sys-include -O2 -O2
2008 Jul 30
3
[LLVMdev] llvm-gcc builds on 32 bit linux broken
Hi all,
I'm having some trouble building llvm-gcc as of today, with and without
bootstrap.
The error I get is:
/home/kooijman/src/llvm-gcc/obj/./gcc/xgcc
-B/home/kooijman/src/llvm-gcc/obj/./gcc/
-B/home/kooijman/src/llvm-gcc/obj/../install/i686-pc-linux-gnu/bin/
-B/home/kooijman/src/llvm-gcc/obj/../install/i686-pc-linux-gnu/lib/ -isystem
2008 May 29
2
[LLVMdev] problems compiling gcc frontend: Error: bad register name `%rbp'
I have problem compiling the gcc frontend.
Almost everything seems to compile but at the very end
when crt startup files are compiled, the assembler complains
about bad registers.
Any idea what I am doing wrong?
Thanks,
Robert
HOST:
os: ubuntu 2.6.18 kernel x86_64 GNU/Linux
compiler: gcc (GCC) 4.0.3 (Ubuntu 4.0.3-1ubuntu5)
SOURCE:
svn trunk gcc4.2
CONFIGURE:
2008 Mar 30
3
[LLVMdev] Compiling llvm-gcc on amd64 with 32 bits: assembler still carps
On Mar 30, 2008, at 10:07 AM, Joachim Durchholz wrote:
>
> Am Sonntag, den 30.03.2008, 12:23 -0400 schrieb Daniel Berlin:
>> To clarify,
>>
>> configure --host=i686-pc-linux-gnu --target=i686-pc-linux-gnu
>> --target=i686-pc-linux-gnu
>>
>> I do this all the time on my 4 core amd64 box and it works fine.
>
> There must be some other difference, as
2010 Jul 07
2
[LLVMdev] llvm-gcc : Did not get a target machine! Triplet is mips64el-unknown-linux-gnu
Hi all,
I met this error(title) when i was trying to compile llvm-gcc-4.2-2.7 on
loongson2f,a mips compatible platform.I also failed to build a
cross-compiler and the error message was the same . Is that means llvm-gcc
cannot support mips back-end now?
Thanks.
Here is my configure options:
$export TARGET=mips64el-unknown-linux-gnu
$../../src/llvm-gcc-4.2-2.7.source/configure