similar to: [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

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

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

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

Am Sonntag, den 30.03.2008, 15:45 -0700 schrieb Tanya Lattner: > 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 > >>> > >>>

On Mar 30, 2008, at 11:22 PM, Joachim Durchholz wrote: > > Am Sonntag, den 30.03.2008, 15:45 -0700 schrieb Tanya Lattner: >> 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

Am Montag, den 31.03.2008, 00:02 -0700 schrieb Tanya Lattner: > On Mar 30, 2008, at 11:22 PM, Joachim Durchholz wrote: > > > Am Sonntag, den 30.03.2008, 15:45 -0700 schrieb Tanya Lattner: > >> On Mar 30, 2008, at 12:39 PM, Joachim Durchholz wrote: > >> > >>> OK, I now have > >>> > >>> LLVM_VERSION_INFO=kurier-bootstrap

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,

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 > >

*bump* Anybody got a clue? I can post a full transcript of a shell session that reproduces the error if that helps. To reiterate the original problem: I'm trying to compile LLVM-GCC on an Ubuntu 64-bit box, with a 32-bit target (to avoid potential problems with PIC and such). I get errors like Error: suffix or operands invalid for `push' as soon as the make process tries to assemble

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

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

On Mar 22, 2008, at 3:37 PM, Joachim Durchholz wrote: > Am Samstag, den 22.03.2008, 09:45 -0500 schrieb Andrew Lenharth: >> officially support for llvm-gcc4.0 has been dropped. >> unofficially I still keep llvm-gcc4.0 compiling because I need it for >> some stuff. But this will only last until I can use 4.2. > > OK, that's a clear roadmap. > Please do not rely

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

My Emails a week or so back were about installing Rstudio and the R shiny server on Debian. I was using an old Toshiba laptop as a sandbox for that and it would only install i386 (same for Ubuntu). Using the information at https://cran.r-project.org/bin/linux/debian/ I did get to the point where I had R 3.5.2, Rstudio and the server on there (with some help from Dirk that is in the list archives).

Joachim Durchholz wrote: > Since llvm cannot generate code for amd64 at this time, this translates > to an additional constraint on --target, restricting me to --target=i686 > only. llvm can generate code for amd64, but shared libs don't work, and bootstrapping doesn't work (PR1711). Still, if you want to compile it as 32-bit, does it work if you run configure like this (without

Am Samstag, den 22.03.2008, 09:45 -0500 schrieb Andrew Lenharth: > officially support for llvm-gcc4.0 has been dropped. > unofficially I still keep llvm-gcc4.0 compiling because I need it for > some stuff. But this will only last until I can use 4.2. OK, that's a clear roadmap. Maybe the docs should be updated to reflect this status? They still present 4.0 as if it were the default

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',

Dear Dirk, I have had the exactly same problem like Ivo and his solution worked for me. Hence the USE=f77 flag is NOT a typo but a Gentoo quirk. As far as modifying the configure script is concerned, I believe that it is certainly possible to perform said check (if 'f77 --version == f2c' then die) only on x86_64 platforms. And I'd argue it is f2c's fault. AMD64 linux distros have

My appologies, this estimation is about right, I spent last week at COMPSTAT in prague and didn't follow the list closely. Inspite of this fact I believe my posting is not entirely out of date. regards Diman Todorov ------------------------------ You are 8 days behind the times -- take a look at the current R-devel. On Sun, 29 Aug 2004, Diman Todorov wrote: > Dear Dirk, > I