#20361: (trunk) fftw-3 +gcc43: failure during configure phase, compiler does not recognize -arch flag ---------------------------------+------------------------------------------ Reporter: simon@… | Owner: ram@… Type: defect | Status: assigned Priority: Normal | Milestone: MacPorts 1.8.0 Component: ports | Version: 1.8.0 Keywords: fftw-3 -arch | Port: fftw-3 ---------------------------------+------------------------------------------ Changes (by jmr@…): * cc: jmr@… (added) * milestone: => MacPorts 1.8.0 Comment: Replying to [comment:8 toby@…]:
It's possible that the configure.compiler setting gets used earlier, and setting in the variant is too late for the arch_flag_supported check to operate correctly.
Yeah, configure.archflags gets appended to configure.{c,cxx,f}flags before variants are executed. There are a couple of issues here: first, I don't think any fortran compiler supports -arch, so we should probably always use -m32/-m64 in configure.f*flags. Second, it's probably a bad idea to be appending to those variables at all, since there's really no time you can do it without the potential for getting it wrong. I think the convention just has to be that configure.archflags will be added to the right environment variable during configure, but if you are patching CFLAGS into a Makefile manually or whatever you'll just have to specifically put the archflags in there as well. -- Ticket URL: <http://trac.macports.org/ticket/20361#comment:11> MacPorts <http://www.macports.org/> Ports system for Mac OS