Opened 19 years ago
Closed 19 years ago
#61 closed defect (fixed)
New <c:configure> command fails
Reported by: | Chandler Carruth <chandlerc@…> | Owned by: | cmlenz |
---|---|---|---|
Priority: | major | Milestone: | 0.5 |
Component: | Recipe commands | Version: | dev |
Keywords: | Cc: | ||
Operating System: |
Description
The configure command correctly runs "./configure", but the script dies very early on:
[INFO ] Executing build step "configure" [INFO ] checking build system type... i686-pc-linux-gnu [INFO ] checking host system type... i686-pc-linux-gnu [INFO ] checking target system type... i686-pc-linux-gnu [INFO ] checking for a BSD-compatible install... /usr/bin/install -c [INFO ] checking whether build environment is sane... yes [INFO ] checking for gawk... gawk [ERROR ] configure: error: C compiler cannot create executables [INFO ] checking whether make sets $(MAKE)... yes [ERROR ] See `config.log' for more details. [INFO ] checking for gcc... gcc [ERROR ] Build step configure failed [WARNING ] Build step configure failed
Attachments (0)
Change History (3)
comment:1 Changed 19 years ago by Chandler Carruth <chandlerc@…>
comment:2 Changed 19 years ago by cmlenz
- Milestone set to 0.5
- Status changed from new to assigned
The actual command executed should be displayed in --debug mode, actually.
comment:3 Changed 19 years ago by cmlenz
- Resolution set to fixed
- Status changed from assigned to closed
The problem here was that the CFLAGS and CXXFLAGS were quoted. That is appropriate when invoking ./configure through the shell, but fails when invoking it programmatically.
In addition, the current working directory wasn't be set, so ./configure created its output files in the directory that bitten-slave was being run from.
Both of these problems should be fixed in [251].
things that would be useful in finding out why this happens:
With either/both of these, I can probably find the problem.