#32881: fftw-3 gcc46 variant builds with clang ----------------------------------+----------------------------------------- Reporter: stefan@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.0.3 Keywords: | Port: fftw-3 ----------------------------------+----------------------------------------- Comment(by stefan@…): Here is the missing info (can't change the summary): fftw-3 @3.3 +gcc46 XCode 4.2.1 OS X 10.7.2 -- Ticket URL: <https://trac.macports.org/ticket/32881#comment:1> MacPorts <http://www.macports.org/> Ports system for Mac OS

#32881: fftw-3 gcc46 variant builds with clang ----------------------------------+----------------------------------------- Reporter: stefan@… | Owner: ram@… Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.0.3 Keywords: | Port: fftw-3 ----------------------------------+----------------------------------------- Comment(by krogalon@…): Hi, after looking at the Portfile of fftw-3 more closely, it seems to me that the default c compiler is never set. Only the fortran compiler with configure.f77, which only affects the fortran wrappers to the library. Whereas in the fftw (version 2) package, the compiler is set for each variant with configure.compiler . Is the new behavior intentional? Doesn't it make more sense to compile the whole library with the compiler selected with the variant? -- Ticket URL: <https://trac.macports.org/ticket/32881#comment:3> MacPorts <http://www.macports.org/> Ports system for Mac OS

#32881: fftw-3 gcc46 variant builds with clang ----------------------------------+----------------------------------------- Reporter: stefan@… | Owner: ram@… Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.0.3 Keywords: | Port: fftw-3 ----------------------------------+----------------------------------------- Comment(by krogalon@…): Hi! It doesn't fail to build, it uses clang. Which went against my expectation that, using variant +gcc46, gcc 4.6 would be used to build the package. I don't understand why only the fortran bindings should be compiled with gcc 4.6, but the c part (i.e., the actual library, if I'm not mistaken) with the current standard compiler. I would suggest to change the Portfile such that the gccX variants selects both the fortran and the c compiler (with configure.compiler), as it is done in the fftw package. And other packages, like octave for example. Unless there's a good reason not to, of course. -- Ticket URL: <https://trac.macports.org/ticket/32881#comment:6> MacPorts <http://www.macports.org/> Ports system for Mac OS

#32881: fftw-3 gcc46 variant builds with clang ----------------------------------+----------------------------------------- Reporter: stefan@… | Owner: ram@… Type: enhancement | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.0.3 Keywords: | Port: fftw-3 ----------------------------------+----------------------------------------- Comment(by ram@…): The attached patch will cause the selected compiler to be used when building the entire port instead of the just the fortran wrappers. This isn't a complete patch as with this applied the variant descriptions are no longer correct, they currently state that the `gcc*` variants: "`create Fortran wrappers using gcc*`". But after the application of this patch, the whole port is built using this compiler, so if this patch is applied then these variant descriptions will also need to change. In addition it also needs to be ported to `fftw-3-single` and `fftw-3-long` so all `fftw-3` ports are consistent. -- Ticket URL: <https://trac.macports.org/ticket/32881#comment:8> MacPorts <http://www.macports.org/> Ports system for Mac OS

#32881: fftw-3 gcc46 variant builds with clang ----------------------------------+----------------------------------------- Reporter: stefan@… | Owner: ram@… Type: enhancement | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.0.3 Keywords: | Port: fftw-3 ----------------------------------+----------------------------------------- Comment(by s.schwandter@…): Hi! I'm the original bug reporter, but due to my old email address not working anymore, I had to create a new account. The patch does exactly what I was suggesting, yes. -- Ticket URL: <https://trac.macports.org/ticket/32881#comment:10> MacPorts <http://www.macports.org/> Ports system for Mac OS