gccld outputs shell scripts that try to start lli without specifying a full
path name.  The problem with 
this is that if you change your path so that it doesn't have lli in it, you
suddenly can't run "binaries" that 
llvm-gcc outputs.

The workaround is to edit the script so that it specifies the full path name of
lli, or to use the CBE or 
LLC instead.

I ran across this when playing with the test suite for GNU ed-0.2; it resets
the PATH before running any 
tests.

Hrm, what do you suggest doing to fix this?  I guess we could have the shell
script hardcode the path to lli, based on the path to gccld...

-Chris

I'm not sure... I really don't like hardcoded paths. We could do something like

#!/bin/sh
lli=${LLVM_INTERP-lli}
exec $lli ...options... /full/path/to/file.bc

This would give us the ability to use the LLVM_INTERP environment variable as a workaround.

That works for me.  You could also have multiple fall-backs, like trying the
LLIINTERP var, then lli in the path, then the hardcoded one...

-chris

Any thoughts on this bug Brian?

-Chris

patch is in...

http://mail.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20040503/014180.html