Opened 3 years ago
Closed 3 years ago
#63723 closed defect (invalid)
lighttpd @1.4.60: Configure failure with gcc5
Reported by: | evanmiller (Evan Miller) | Owned by: | ryandesign (Ryan Carsten Schmidt) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.7.1 |
Keywords: | Cc: | mascguy (Christopher Nielsen) | |
Port: | lighttpd |
Description
Not sure if it's lighttpd, gcc5, or legacysupport, but somebody is passing -arch
to gcc-mp-5 during configure and it is failing.
configure:3768: checking whether the C compiler works configure:3790: /opt/local/bin/gcc-mp-5 -pipe -Os -std=c99 -I/opt/local/include/LegacySupport -arch ppc -I/opt/local/include -I/opt/local/include/LegacySupport -L/opt/local/lib -Wl,-headerpad_max_install_names -lMacportsLegacySupport -arch ppc conftest.c >&5 gcc-mp-5: error: unrecognized command line option '-arch' gcc-mp-5: error: unrecognized command line option '-arch' configure:3794: $? = 1 configure:3832: result: no configure: failed program was: | /* confdefs.h */ | #define PACKAGE_NAME "lighttpd" | #define PACKAGE_TARNAME "lighttpd" | #define PACKAGE_VERSION "1.4.61" | #define PACKAGE_STRING "lighttpd 1.4.61" | #define PACKAGE_BUGREPORT "https://redmine.lighttpd.net/projects/lighttpd/boards/2" | #define PACKAGE_URL "https://www.lighttpd.net/" | #define PACKAGE "lighttpd" | #define VERSION "1.4.61" | /* end confdefs.h. */ | | int | main () | { | | ; | return 0; | } configure:3837: error: in `/opt/local/var/macports/build/_Users_emiller_macports.local_www_lighttpd/lighttpd/work/lighttpd-1.4.61': configure:3839: error: C compiler cannot create executables See `config.log' for more details
Attachments (2)
Change History (8)
Changed 3 years ago by evanmiller (Evan Miller)
Attachment: | lighttpd-config.log added |
---|
Changed 3 years ago by evanmiller (Evan Miller)
Attachment: | lighttpd-main.log added |
---|
comment:1 Changed 3 years ago by evanmiller (Evan Miller)
comment:2 Changed 3 years ago by mascguy (Christopher Nielsen)
Cc: | mascguy added |
---|
comment:3 Changed 3 years ago by ryandesign (Ryan Carsten Schmidt)
Is MacPorts selecting the gcc5 compiler for this port or did you do it manually? Manually selecting compilers by overriding configure.compiler
on the command line is a useful debugging tool but is not expected to be used for real builds and in general we only support building ports with the compiler MacPorts selected, not arbitrary compilers.
comment:4 Changed 3 years ago by ryandesign (Ryan Carsten Schmidt)
The log says:
:debug:configure Preferred compilers: apple-gcc-4.2 gcc-4.0 macports-gcc-7 macports-gcc-6 macports-gcc-5 macports-clang-3.4 macports-clang-3.3
This does make me suspicious about why gcc5 is being used, since it is 5th in the list; I would have expected the first compiler in the list to be used.
comment:5 Changed 3 years ago by evanmiller (Evan Miller)
GCC5 was manually selected. I chose it in order to provide a more narrowly tailored compiler blacklist.
This appears to be a bug in base affecting PPC when building ports with GCC 4.6 through GCC 6. I am working on a solution here:
https://github.com/evanmiller/macports-base/commit/2fc005a6222cda4ba6bdc39b62340f7251bef5e3
comment:6 Changed 3 years ago by ryandesign (Ryan Carsten Schmidt)
Resolution: | → invalid |
---|---|
Status: | assigned → closed |
Ok, then I would consider this report invalid.
If you have trouble building the port with the compiler MacPorts selected for you, please do report that.
Seeing the same error configuring
openldap-devel
usingconfigure.compiler=macports-gcc-4.9
. This port does not use LegacySupport, so it appears to be some kind of issue in base that has incorrect information about which GCC versions support-arch
.