Displaying 20 results from an estimated 10000 matches similar to: "[LLVMdev] Just got bitten by accidentally using the wrong gcc"
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 20
3
[LLVMdev] Just got bitten by accidentally using the wrong gcc
llvm's ./configure already does that for gcc < 3.
What are valid versions? Exactly 4.0 and 4.2? 4.0 and >=4.2?
dnl Verify that GCC is version 3.0 or higher
if test "$GCC" = "yes"
then
AC_COMPILE_IFELSE([[#if !defined(__GNUC__) || __GNUC__ < 3
#error Unsupported GCC version
#endif
]], [], [AC_MSG_ERROR([gcc 3.x required, but you have a lower
version])])
fi
2008 Mar 20
4
[LLVMdev] Just got bitten by accidentally using the wrong gcc
>> 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
>>
2008 Mar 20
0
[LLVMdev] Just got bitten by accidentally using the wrong gcc
Am Donnerstag, den 20.03.2008, 15:27 -0700 schrieb Shantonu Sen:
> llvm's ./configure already does that for gcc < 3.
>
> What are valid versions? Exactly 4.0 and 4.2? 4.0 and >=4.2?
There's a list at http://llvm.org/docs/GettingStarted.html#brokengcc so
there is a reasonable basis.
The list isn't comprehensive, of course, and will likely grow in the
future. OTOH
2008 Mar 21
0
[LLVMdev] Just got bitten by accidentally using the wrong gcc
Am Freitag, den 21.03.2008, 06:56 -0700 schrieb Shantonu Sen:
> I recommend you don't parse version strings. In fact I switch the
> check to use AC_COMPILE precisely for the reason that gcc --version is
> totally unreliable and vendor specific. For example, what's the
> regular expression that tells you what the GCC version is:
> i686-apple-darwin9-gcc-4.0.1 (GCC)
2008 Mar 21
3
[LLVMdev] Just got bitten by accidentally using the wrong gcc
I recommend you don't parse version strings. In fact I switch the
check to use AC_COMPILE precisely for the reason that gcc --version is
totally unreliable and vendor specific. For example, what's the
regular expression that tells you what the GCC version is:
i686-apple-darwin9-gcc-4.0.1 (GCC) 4.0.1 (Apple Inc. build 5470)
(Aspen 5470.3)
Per the rest of this thread, you can't
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 21
1
[LLVMdev] Just got bitten by accidentally using the wrong gcc
Joachim Durchholz wrote:
> Am Donnerstag, den 20.03.2008, 15:44 -0700 schrieb Tanya M. Lattner:
>
>> Its not just a matter of checking major/minor versions. It also depends on
>> the target and in some cases the OS.
>> http://llvm.org/docs/GettingStarted.html#brokengcc
>>
>> So for example, GCC 3.3.3 on Suse or GCC 3.4.0 on linux/x86
>> (32-bit) has
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 20
0
[LLVMdev] Just got bitten by accidentally using the wrong gcc
Am Donnerstag, den 20.03.2008, 15:44 -0700 schrieb Tanya M. Lattner:
> Its not just a matter of checking major/minor versions. It also depends on
> the target and in some cases the OS.
> http://llvm.org/docs/GettingStarted.html#brokengcc
>
> So for example, GCC 3.3.3 on Suse or GCC 3.4.0 on linux/x86
> (32-bit) has issues. Is it easy to check these kinds of things?
uname
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 21
0
[LLVMdev] Just got bitten by accidentally using the wrong gcc
> I guess it could be done for things like 4.1.1 or a couple of others on
> the list.
This gcc version always worked fine for me on ubuntu linux (though it
might have been 4.1.2, I don't recall).
Ciao,
Duncan.
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
2008 Mar 30
0
[LLVMdev] Compiling llvm-gcc on amd64 with 32 bits: assembler still carps
Am Sonntag, den 30.03.2008, 10:28 -0700 schrieb Tanya Lattner:
> On Mar 30, 2008, at 10:07 AM, Joachim Durchholz wrote:
> > Look at how $LLVM_CONFIGURE is built, the final value is
> >
> > --prefix=/home/jo --enable-optimized --build=i686-pc-linux-gnu
> > --host=i686-pc-linux-gnu --target=i686-pc-linux-gnu"
> >
>
> This looks likes its missing some
2008 Mar 21
0
[LLVMdev] Just got bitten by accidentally using the wrong gcc
Am Freitag, den 21.03.2008, 13:03 +0100 schrieb Duncan Sands:
> Hi Joachim,
>
> > I have to report that the Ubuntu gcc-4.1 will fail. 'make' would run
> > without giving more than a few warnings, but 'make install' will
> > complain that it doesn't know how to build one of the intermediate
> > targets and error out (some VMCore/tablegen file IIRC,
2008 Mar 30
0
[LLVMdev] Compiling llvm-gcc on amd64 with 32 bits: assembler still carps
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 I'm doing exactly that:
> > > export LLVM_GCC_SRC=$HOME/llvm-gcc-src
> >
2008 Mar 30
2
[LLVMdev] Compiling llvm-gcc on amd64 with 32 bits: assembler still carps
On Mar 30, 2008, at 12:39 PM, Joachim Durchholz wrote:
>
> Am Sonntag, den 30.03.2008, 10:28 -0700 schrieb Tanya Lattner:
>> On Mar 30, 2008, at 10:07 AM, Joachim Durchholz wrote:
>>> Look at how $LLVM_CONFIGURE is built, the final value is
>>>
>>> --prefix=/home/jo --enable-optimized --build=i686-pc-linux-gnu
>>> --host=i686-pc-linux-gnu
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 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 24
7
[LLVMdev] Potential breakage in llvm-gcc's ./configure
(Apologies if this appears twice, it seems to not have made it into the list. I added an update for SVN trunk.)
Just a quick heads-up for 2.2 and SVN trunk:
./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