Closed Bug 471350 Opened 17 years ago Closed 17 years ago

Broken configure script?

Categories

(SeaMonkey :: Build Config, defect)

x86_64
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: rekcahx, Unassigned)

Details

User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.8.1.19) Gecko/20081204 Iceape/1.1.14 (Debian-1.1.14-1) Build Identifier: http://releases.mozilla.org/pub/mozilla.org/seamonkey/releases/2.0a2/source/seamonkey-2.0a2.source.tar.bz2 I tried to compile Seamonkey-2.0a2 from source, but the configure script detects my compiler wrong. Here is all output from script: --cut-here-- $ ./configure Adding configure options from ./.mozconfig: --enable-application=suite --enable-optimize --enable-update-channel=beta --enable-update-packaging --disable-debug --disable-tests --enable-codesighs loading cache ./config.cache checking host system type... x86_64-unknown-linux-gnu checking target system type... x86_64-unknown-linux-gnu checking build system type... x86_64-unknown-linux-gnu checking for gawk... no checking for mawk... mawk checking for gcc... /tools/gcc-4.1.1/bin/gcc checking whether the C compiler (/tools/gcc-4.1.1/bin/gcc -gstabs+ ) works... no configure: error: installation or configuration problem: C compiler cannot create executables. --cut-here-- And here is last few lines from config.log: --cut-here-- configure:2270: checking whether the C compiler (/tools/gcc-4.1.1/bin/gcc -gstabs+ ) works configure:2286: /tools/gcc-4.1.1/bin/gcc -o conftest -gstabs+ conftest.c 1>&5 ./configure: line 2285: /tools/gcc-4.1.1/bin/gcc: No such file or directory configure: failed program was: #line 2281 "configure" #include "confdefs.h" main(){return(0);} --cut-here-- Anyway, I'm a Debian user, and my system is Sid/unstable amd64. $ ls -lh `which gcc` lrwxrwxrwx 1 root root 7 2008-12-21 17:40 /usr/bin/gcc -> gcc-4.3 $ file `which gcc-4.3` /usr/bin/gcc-4.3: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.8, stripped Reproducible: Always Steps to Reproduce: 1. tar jxvf seamonkey-2.0a2.source.tar.bz2 2. ./configure Actual Results: Unable to configure Expected Results: Executable binary.
Assignee: nobody → build-config
Component: General → Build Config
QA Contact: general → build-config
It seems quite likely that this is an error in your build environment. Our configure scripts use AC_PROG_CC to find a C compiler in your $PATH like every other configure script on the planet.
Version: unspecified → Trunk
Btw, this .tar.bz2 contains .mozconfig, and it defines variables CC and CXX. $ grep tools .mozconfig CC=/tools/gcc-4.1.1/bin/gcc CXX=/tools/gcc-4.1.1/bin/g++ These paths are not correct for my build environment.
We should not include the .mozconfig, it just happens to be the one we used for compiling the release builds. I'll avoid packaging it for Alpha 3.
Timo, do you still have the same problem with the 2.0a3 tarball?
Assignee: build-config → nobody
QA Contact: build-config → build-config
No reply from the original reporter. Closing as Incomplete.
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.