Opened 7 years ago

Closed 7 years ago

#42990 closed defect (invalid)

ImageMagick @6.8.8-3_1 won't build for OS X 10.9.2

Reported by: twilsonco@… Owned by: ryandesign (Ryan Schmidt)
Priority: Normal Milestone:
Component: ports Version: 2.2.1
Keywords: mavericks Cc:
Port: ImageMagick

Description (last modified by ryandesign (Ryan Schmidt))

Have followed migration instructions wiki:Migration, and most packages now build.

Log attached. Errors in configure, then fails to build.

Attachments (2)

main.log (185.2 KB) - added by twilsonco@… 7 years ago.
log file
main.2.log (183.4 KB) - added by twilsonco@… 7 years ago.
log for ImageMagick to 6.8.8-9

Download all attachments as: .zip

Change History (12)

Changed 7 years ago by twilsonco@…

Attachment: main.log added

log file

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

Description: modified (diff)
Keywords: mavericks added; ImageMagick Mavericks 10.9.2 removed
Owner: changed from macports-tickets@… to ryandesign@…

The log says:

:info:build magick/fourier.c:895:29: warning: implicitly declaring library function 'cabs' with type 'double (_Complex double)'
:info:build         magnitude_pixels[i]=cabs(forward_pixels[i]);
:info:build                             ^
:info:build magick/fourier.c:895:29: note: please include the header <complex.h> or explicitly provide a declaration for 'cabs'
:info:build magick/fourier.c:895:34: error: passing 'fftw_complex' (aka 'double [2]') to parameter of incompatible type '_Complex double'
:info:build         magnitude_pixels[i]=cabs(forward_pixels[i]);
:info:build                                  ^~~~~~~~~~~~~~~~~

fftw-3 was just updated to version 3.3.4. Maybe this version of ImageMagick is not compatible with that version of fftw-3.

comment:2 Changed 7 years ago by ryandesign (Ryan Schmidt)

Actually, it continues to build fine for me.

I just updated ImageMagick to 6.8.8-9 in r118121. Does that work for you?

If not, please verify whether or not you have installed the command line tools by running xcode-select --install.

comment:3 Changed 7 years ago by twilsonco@…

xcode-select --install hasn't worked since upgrading to 10.9.2 for me. I've installed command line tools from the apple developer site though. I assume it has the same effect. I tried installing r118121 with a port file downloaded manually and with one obtained with subversion.

In both cases, I get an error that "Unable to execute port: Could not open file:". I also set full permissions to the directory with the port file and /opt and all subdirectories have 755 permissions.

I think I'm doing something stupid...

comment:4 Changed 7 years ago by ryandesign (Ryan Schmidt)

Since it's been more than 30 minutes since I committed it, you should only need to "sudo port selfupdate" and then be able to "sudo port install ImageMagick".

Changed 7 years ago by twilsonco@…

Attachment: main.2.log added

log for ImageMagick to 6.8.8-9

comment:5 Changed 7 years ago by twilsonco@…

The errors occur regarding data types and fftw. This problem seems unnecessary. I recently uninstalled all packages, reinstalled macports and reinstalled everything. It was then that these packages gave errors. I used to do all this stuff (gcc, openmpi) manually. I may have broken something in my ignorance that is only now becoming evident...

comment:6 Changed 7 years ago by ryandesign (Ryan Schmidt)

You mentioned in #42991 that you replaced the links to compilers in /usr/bin with GNU versions. That's problematic in the best of cases on OS X, and as of Mavericks, that's positively poisonous, since GNU gcc uses a different C++ runtime than clang and you cannot mix them. More info at wiki:FAQ#libcpp. I see numerous differences between your log and mine regarding basic detection of standard system headers and capabilities. Please undo the changes you made in /usr/bin, clean ImageMagick, and try again.

comment:7 Changed 7 years ago by twilsonco@…

Since I'm really smart, I actually replaced the g++ and gcc links in /usr/bin rather than renaming them and adding my own (which I now realize is only slightly less stupid). Aside from adding links to the installations of openmpi and gcc I used to have, I didn't make any changes. I've deleted the links to openmpi and replaced the gcc and g++ links with links pointing to the gcc and g++ in .../Xcode.app/Contents/Developer/usr/bin/, but the problem persists. Is this not where they were originally referenced?

Looking over the log file, configure for ImageMagick is specifying /usr/bin/clang and /usr/bin/clang++ explicitly, so it shouldn't have made a difference that I changed /usr/bin/gcc right?

Otherwise, do you know a way to have Xcode reinstall everything that needs to be in /usr/...? Will a full reinstall of Xcode and command line tools do the trick? Does it mean anything that I am one of the people who suffer from this http://stackoverflow.com/questions/19691701/failed-to-install-command-line-tools-on-osx-mavericks ?

comment:8 in reply to:  7 Changed 7 years ago by ryandesign (Ryan Schmidt)

Replying to twilsonco@…:

Since I'm really smart, I actually replaced the g++ and gcc links in /usr/bin rather than renaming them and adding my own (which I now realize is only slightly less stupid). Aside from adding links to the installations of openmpi and gcc I used to have, I didn't make any changes. I've deleted the links to openmpi and replaced the gcc and g++ links with links pointing to the gcc and g++ in .../Xcode.app/Contents/Developer/usr/bin/, but the problem persists. Is this not where they were originally referenced?

They were originally shims, whose exact functioning is not known to me.

Looking over the log file, configure for ImageMagick is specifying /usr/bin/clang and /usr/bin/clang++ explicitly, so it shouldn't have made a difference that I changed /usr/bin/gcc right?

It should mean that, however some ports may not always be UsingTheRightCompiler, and may instead use "gcc", which would be a problem.

Otherwise, do you know a way to have Xcode reinstall everything that needs to be in /usr/...? Will a full reinstall of Xcode and command line tools do the trick?

Reinstalling the command line tools, using the installer Apple provides on the developer web site, should be enough.

Does it mean anything that I am one of the people who suffer from this http://stackoverflow.com/questions/19691701/failed-to-install-command-line-tools-on-osx-mavericks ?

To the best of my knowledge, the error message that the software is not available on the server actually means that the software has already been installed on your computer.

comment:9 Changed 7 years ago by twilsonco@…

Reinstall of Xcode, command line tools, and macports seems to have done the trick. Can install now.

Thanks so much for the help.

Please mark ticket as solved.

comment:10 Changed 7 years ago by ryandesign (Ryan Schmidt)

Resolution: invalid
Status: newclosed

Ok, glad you got it working.

Note: See TracTickets for help on using tickets.