Open GoogleCodeExporter opened 9 years ago
$(qexec) merely keeps the command from being echo'd, you can override that with
'make V=1'.
The problem here is: '/usr/bin/env: bad interpreter'. The shebang uses that to
pick up the first perl in PATH using env rather than the shell, cf. perlrun [1].
In your case you either don't have it or it's elsewhere, e.g., /bin/env. What
system are you running this under?
[1] http://perldoc.perl.org/perlrun.html
Original comment by jz...@google.com
on 7 Feb 2015 at 4:14
[deleted comment]
[deleted comment]
Any update?
Original comment by fgalli...@google.com
on 12 Feb 2015 at 11:05
I haven't had a chance to look any further, there is a workaround as described.
Original comment by jz...@google.com
on 12 Feb 2015 at 11:41
This works for me out of the box using a recent release [1], modulo needing to
force yasm due to configure's use of which.
# target is being set merely for clarity
$ ../configure --as=yasm --target=x86_64-linux-gcc
As mentioned a similar report 'bad interpreter: No such file or directory' can
be made to occur by changing the command to something non-existent. In this
case if env is there was rtcd.pl modified at all? If it were dos line endings
for instance you'd get ': bad interpreter ...' which isn't quite right. I don't
see anything odd in the output, so most likely not.
Do you have any exotic shell options set?
[1] nixos-minimal-14.12.428.acfbdf7-x86_64-linux.iso
Original comment by jz...@google.com
on 19 Feb 2015 at 11:29
Original comment by renganat...@google.com
on 26 Feb 2015 at 11:09
Original issue reported on code.google.com by
codyo...@gmail.com
on 6 Feb 2015 at 5:13