llvm dev - Mar 2008 - [LLVMdev] llvm/test: suffix or operands invalid for `push'

Am Freitag, den 29.02.2008, 15:37 -0800 schrieb Eric
Christopher:
> Aaah. Try:
> 
> .../configure --host=i686-pc-linux-gnu --target=i686-pc-linux-gnu
> 
> and see if that works. If it doesn't it may need some more configure  
> love, but it might happen.
Good to read that! I was slowly approaching despair.

Seems to make a *far* slower compile though. Or it's compiling more code
- can't tell.

Results after
  ./configure ...
  make clean
  make
  cd test
  make
are...

... no joy. Still exactly the same messages.

Interestingly enough, dejagnu still insists that the host is
x86_64-unknown-linux-gnu.

What next?

Regards,
Jo

On Feb 29, 2008, at 4:05 PM, Joachim Durchholz wrote:
>
> Am Freitag, den 29.02.2008, 15:37 -0800 schrieb Eric Christopher:
>> Aaah. Try:
>>
>> .../configure --host=i686-pc-linux-gnu --target=i686-pc-linux-gnu
>>
>> and see if that works. If it doesn't it may need some more
configure
>> love, but it might happen.
>
> Good to read that! I was slowly approaching despair.
>
> Seems to make a *far* slower compile though. Or it's compiling more  
> code
> - can't tell.
>
> Results after
>  ./configure ...
>  make clean
>  make
>  cd test
>  make
> are...
>
> ... no joy. Still exactly the same messages.
>
> Interestingly enough, dejagnu still insists that the host is
> x86_64-unknown-linux-gnu.
Is this configuring llvm or llvm-gcc? Seems to work just fine for  
configure; make; make check with llvm.

-eric

Am Freitag, den 29.02.2008, 18:15 -0800 schrieb Eric
Christopher:
> Is this configuring llvm or llvm-gcc?
This is inside the llvm-2.2 directory.
> Seems to work just fine for  
> configure; make; make check with llvm.
Trying "make check" from the llvm directory instead of
"make" from
llvm/test... doesn't work.

Retrying from scratch, here's the transcript:

# I had set up $PATH like this:
$ which llvm-gcc llvm-g++
/home/jo/bin/llvm-gcc
/home/jo/bin/llvm-g++
# ... and $HOME/bin like this:
$ ll $HOME/bin
 llvm-g++ -> /home/jo/Delta/llvm-gcc4.2-2.2-x86-linux-RHEL4/bin/llvm-g++
 llvm-gcc -> /home/jo/Delta/llvm-gcc4.2-2.2-x86-linux-RHEL4/bin/llvm-gcc

# Reset to initial state:
$ rm -rf llvm-2.2 llvm-gcc4.2-2.2-x86-linux-RHEL4
$ tar xzf llvm-2.2.tar.gz
$ tar xzf llvm-gcc4.2-2.2-x86-linux-RHEL4.tar.gz

# Configure & install
$ cd llvm-2.2
# I'm trying the --build option, too.
$ ./configure --prefix=$HOME CC=gcc-4.2 CXX=g++-4.2 \
  --build=x86_64-pc-linux-gnu \
  --host=i686-pc-linux-gnu --target=i686-pc-linux-gnu
$ make
$ make check
# Host is still wrong.
# Not sure whether the warnings are a problem.
# The used description files might be for x86_64 though.
...
Target is i686-pc-linux-gnu
Host   is x86_64-unknown-linux-gnu
...
Using /usr/share/dejagnu/baseboards/unix.exp as board description file
for target.
Using /usr/share/dejagnu/config/unix.exp as generic interface file for
target.
WARNING: Couldn't find tool config file for unix, using default.
WARNING: Assuming target board is the local machine (which is probably
wrong).
You may need to set your DEJAGNU environment variable.
...FAIL: /home/jo/Delta/llvm-2.2/test/C
++Frontend/2006-11-30-NoCompileUnit.cpp
Failed with exit(1) at line 2
while running: as NoCompileUnit.s -o NoCompileUnit.o
NoCompileUnit.s: Assembler messages:
NoCompileUnit.s:33: Error: suffix or operands invalid for `push'
NoCompileUnit.s:52: Error: suffix or operands invalid for `pop'
NoCompileUnit.s:64: Error: suffix or operands invalid for `push'
NoCompileUnit.s:83: Error: suffix or operands invalid for `pop'
NoCompileUnit.s:95: Error: suffix or operands invalid for `push'
NoCompileUnit.s:116: Error: suffix or operands invalid for `pop'
NoCompileUnit.s:128: Error: suffix or operands invalid for `push'
NoCompileUnit.s:225: Error: suffix or operands invalid for `pop'
NoCompileUnit.s:237: Error: suffix or operands invalid for `push'
NoCompileUnit.s:243: Error: suffix or operands invalid for `push'
NoCompileUnit.s:268: Error: suffix or operands invalid for `pop'
NoCompileUnit.s:269: Error: suffix or operands invalid for `pop'
...

I'm not sure what to make of that "tool config file" warning.

Regards,
Jo