Closed Bug 473963 Opened 17 years ago Closed 17 years ago

TM: cannot build JS shell - Native@NANOJIT_ARCH@.h in Makefile

Categories

(Core :: JavaScript Engine, defect)

x86
Linux
defect
Not set
normal

Tracking

()

RESOLVED INVALID

People

(Reporter: igor, Unassigned)

Details

With the current TM tip, http://hg.mozilla.org/tracemonkey/rev/d77738e770cd , I cannot build js shell using configure. After fresh autoconf-2.13 and running configure in an empty dir on Ubuntu 8.04 I got with make: make[2]: Leaving directory `/scratch/igor/build/js/x/shell' /home/igor/build/js/x/config/nsinstall ... /home/igor/m/tm/js/src/nanoj\ it/Native.h Native@NANOJIT_ARCH@.h ... /home/igor/build/js/x/config/nsinstall: cannot access Native@NANOJIT_ARCH@.h: No such file or directory make[1]: *** [export] Error 1 m It looks like Native@NANOJIT_ARCH@.h has not properly expanded.
Did you run autoconf-2.13 in js/src? I haven't seen anyone else having this problem, and that error just looks like you didn't run autoconf correctly. jorendorff: check those damn configure scripts in!
(In reply to comment #1) > Did you run autoconf-2.13 in js/src? Yes, I did.
It seems the problem comes from using 32-bit chroot environment on 64-bit Linux. But the bug itself is a recent thing - the last week I have used repeatedly configure/make within the same chroot without any troubles.
Well, bsmedberg changed the way NANOJIT_ARCH is set in bug 463172, but it should always be either set to something or empty, not @NANOJIT_ARCH@, which is the bit that configure substitutes.
(In reply to comment #2) > (In reply to comment #1) > > Did you run autoconf-2.13 in js/src? > > Yes, I did. Actually I have run autoconf, not autoconf-2.13 judging by the shell history. With autoconf-2.13 everything works as before.
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.