Last Comment Bug 721744 - configure: error: mozilla/js/src/ctypes/libffi/configure failed for ctypes/libffi
: configure: error: mozilla/js/src/ctypes/libffi/configure failed for ctypes/li...
: regression
Product: Core
Classification: Components
Component: JavaScript Engine (show other bugs)
: Trunk
: x86 Mac OS X
: -- normal (vote)
: ---
Assigned To: general
: Jason Orendorff [:jorendorff]
Depends on:
Blocks: 719659
  Show dependency treegraph
Reported: 2012-01-27 07:07 PST by Bob Clary [:bc:]
Modified: 2012-01-27 15:23 PST (History)
2 users (show)
See Also:
Crash Signature:
QA Whiteboard:
Iteration: ---
Points: ---
Has Regression Range: ---
Has STR: ---

config.log (57.11 KB, text/plain)
2012-01-27 07:07 PST, Bob Clary [:bc:]
no flags Details
$objdir/js/src/config.log (19.76 KB, text/plain)
2012-01-27 12:50 PST, Bob Clary [:bc:]
no flags Details
$objdir/js/src/ctypes/libffi/config.log (10.02 KB, text/plain)
2012-01-27 12:51 PST, Bob Clary [:bc:]
no flags Details

Description Bob Clary [:bc:] 2012-01-27 07:07:20 PST
Created attachment 592128 [details]

On Mac OS X 10.5 with the default gcc 4.2, configure fails in js due to 719659

checking whether the C compiler works... no
configure: error: in `/work/mozilla/builds/nightly/mozilla/firefox-debug/js/src/ctypes/libffi':
configure: error: C compiler cannot create executables
See `config.log' for more details.
configure: error: /work/mozilla/builds/nightly/mozilla/js/src/ctypes/libffi/configure failed for ctypes/libffi
configure: error: /work/mozilla/builds/nightly/mozilla/js/src/configure failed for js/src
Comment 1 Justin Wood (:Callek) 2012-01-27 07:14:38 PST
Fixed by backout (in Bug 721625) this may reappear though if the patch ever re-lands. (merge cset)
Comment 2 Jeff Walden [:Waldo] (remove +bmo to email) 2012-01-27 12:14:43 PST
Bob, is that the config.log you meant to upload?  It doesn't contain the error in your comment.  Did you upload the libffi config.log, or some other one?

The one you uploaded shows that the two arguments that were added work just fine, which is what confuses me.
Comment 3 Bob Clary [:bc:] 2012-01-27 12:43:04 PST
Waldo, damn. I just included the overall Firefox config.log and not the js/src config. Let me rebuild with your patch and include the proper one.
Comment 4 Bob Clary [:bc:] 2012-01-27 12:50:26 PST
Created attachment 592223 [details]

is this better?
Comment 5 Bob Clary [:bc:] 2012-01-27 12:51:55 PST
Created attachment 592224 [details]
Comment 6 Jeff Walden [:Waldo] (remove +bmo to email) 2012-01-27 14:15:00 PST
Comment 5 gets the right thing.  In that, I see this:

configure:3249: checking for gcc
configure:3265: found /usr/bin/gcc
configure:3276: result: gcc
configure:3505: checking for C compiler version
configure:3514: gcc --version >&5
i686-apple-darwin9-gcc-4.0.1 (GCC) 4.0.1 (Apple Inc. build 5493)
Copyright (C) 2005 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO

configure:3525: $? = 0
configure:3514: gcc -v >&5
Using built-in specs.
Target: i686-apple-darwin9
Configured with: /var/tmp/gcc/gcc-5493~1/src/configure --disable-checking -enable-werror --prefix=/usr --mandir=/share/man --enable-languages=c,objc,c++,obj-c++ --program-transform-name=/^[cg][^.-]*$/s/$/-4.0/ --with-gxx-include-dir=/include/c++/4.0.0 --with-slibdir=/usr/lib --build=i686-apple-darwin9 --with-arch=apple --with-tune=generic --host=i686-apple-darwin9 --target=i686-apple-darwin9
Thread model: posix
gcc version 4.0.1 (Apple Inc. build 5493)

4.0.1!?!?!  Why in the world is that being found?

I hate autoconf.
Comment 7 Bob Clary [:bc:] 2012-01-27 14:30:39 PST
Ah, Firefox's global configure

$ grep gcc-4.2 configure
    # we prefer gcc-4.2 over gcc on older darwin, so
      for ac_prog in $CC gcc-4.2 gcc

I bet js's configures don't do that. I suppose I could just set CC if that is used in js's other configures.
Comment 8 Bob Clary [:bc:] 2012-01-27 15:02:59 PST
fyi, setting CC=gcc-4.2 and CXX=g++-4.2 on my Mac OS X 10.5 works.
Comment 9 Jeff Walden [:Waldo] (remove +bmo to email) 2012-01-27 15:23:08 PST
Hmm, if js's configure isn't doing that, it totally should, I think.

Note You need to log in before you can comment on or make changes to this bug.