Opened 9 years ago

Closed 9 years ago

Last modified 9 years ago

#47609 closed defect (worksforme)

fftw fails at destroot when texinfo ports is installed

Reported by: numaryu Owned by: seanfarley (Sean Farley)
Priority: Normal Milestone:
Component: ports Version: 2.3.3
Keywords: haspatch Cc: petrrr
Port: fftw

Description

fftw fails when processing fftw.info file with the texinfo port installed. The older version provided by OSX (/usr/bin/makeinfo) works fine. I don't know what's the best way to solve this issue, but at least the attached patch suggested for a similar defect (#45971) works.

Attachments (2)

Portfile.patch (426 bytes) - added by numaryu 9 years ago.
fftw.log (244.5 KB) - added by numaryu 9 years ago.

Download all attachments as: .zip

Change History (16)

Changed 9 years ago by numaryu

Attachment: Portfile.patch added

Changed 9 years ago by numaryu

Attachment: fftw.log added

comment:1 Changed 9 years ago by ryandesign (Ryan Carsten Schmidt)

Cc: sean@… removed
Keywords: haspatch added; texinfo removed
Owner: changed from macports-tickets@… to sean@…

There's no need to enclose MAKEINFO=/usr/bin/makeinfo in quotation marks.

comment:2 Changed 9 years ago by nerdling (Jeremy Lavergne)

This means fftw needs updated upstream.

Regarding the temporary patch: which OS version work this way? been tested?

comment:2 Changed 9 years ago by Ionic (Mihai Moldovan)

Please do not use system makeinfo. Fix up the issue.

comment:3 Changed 9 years ago by numaryu

I've tested on 10.9.5, makeinfo 4.8.

comment:4 Changed 9 years ago by IvoClarysse (Ivo Clarysse)

Note that this issue has been fixed upstream, and that this fix is incorporated in the fftw-3 port.

comment:5 Changed 9 years ago by petrrr

Cc: petr@… added

Cc Me!

comment:6 Changed 9 years ago by seanfarley (Sean Farley)

Resolution: worksforme
Status: newclosed

I can't reproduce this at all. Maybe the newer version of makeinfo fixed this? I'm going to mark this as 'worksforme'.

comment:7 Changed 9 years ago by numaryu

There still exists the problem. Please use the source mode.

comment:8 Changed 9 years ago by seanfarley (Sean Farley)

Yes, I did. Since fftw 2.x is dead, the real question is why are you still using it?

comment:9 Changed 9 years ago by numaryu

I'm using it because our scientific simulation code uses it. I personally do not mind if macports gives up supporting fftw2. But, aren't there users other than me?

comment:10 Changed 9 years ago by seanfarley (Sean Farley)

From http://www.fftw.org:

If you are still using FFTW 2.x, please note that FFTW 2.x was last updated in 1999 and it is obsolete.

That was 15 years ago. I spent part of my research updating fftw2 code to fftw3 and it didn't take that long.

comment:11 Changed 9 years ago by numaryu

Yes, I know. But, the code is not my own. There are many users, and one of my colleague prefers the fftw2 interface over fftw3.

comment:12 in reply to:  11 Changed 9 years ago by seanfarley (Sean Farley)

Replying to ryusuke.numata@…:

Yes, I know. But, the code is not my own. There are many users, and one of my colleague prefers the fftw2 interface over fftw3.

The code I had to fix wasn't my own, either :-) Your college is 15 years behind the times. Newer processors and memory architectures have come out that the fftw team has written code for ... but only in the 3.x version. I can't help but emphasize fifteen years. For what it's worth, I know for a fact the fftw 2.x series has a broken mpi implementation.

Of course, you could argue that your patch is small enough and low impact so as to be a minimal intrusion. After I give my talk at Berkeley tomorrow, I'll probably consider adding it since it doesn't break things anymore than they are already broken.

comment:13 Changed 9 years ago by numaryu

thanks for your consideration.

Note: See TracTickets for help on using tickets.