cmake fails to build on clean 2.3.3 installation

[diochnos]

I find it hard to believe that I am posting this ticket, but I can not see what I have done wrong.

In a nutshell: cmake fails to install on a new macports installation.

Background: There was a previous version of macports installed on the system (before the upgrade to Yosemite), which was uninstalled entirely (together with complete removal of the /opt/local/ directory). In particular, for the previous version I gave the following:

    $ sudo port -f uninstall installed 
    $ sudo port clean all 

For this version (2.3.3) I also gave a

    $ make clean

before I started.

This time I attempted a custom installation with the following command for configuration:

    $ env PATH=/usr/bin:/bin:/usr/sbin:/sbin CFLAGS="-pipe -Os" ./configure --prefix=/opt/macports/yosemite --with-applications-dir=/opt/macports/yosemite/Applications

Other than that

    $ make 
    $ sudo make install 
    $ sudo port selfupdate 
    $ sudo port upgrade outdated 

(everything as expected; meanwhile I also gave at some point xcode-select --install, so that's not a problem either)

Then:

    $ sudo port install cmake

fails on the last package, when attempting to bring in cmake.

Upon the error:

    $ sudo port clean cmake 
    $ sudo port install cmake

Same problem (even with a restart). Log attached. Running Xcode 6.1.1 on OS X 10.10.1.

[diochnos]

Log file

[mf2k (Frank Schima)]

In the future, please fill in the Port field and Cc the port maintainers (port info --maintainers cmake), if any.

[mf2k (Frank Schima)]

Forget my WikiFormatting comment. Reformatted with code tags.

[diochnos]

@mf2k: I will certainly try to remember to do so.

Meanwhile, I was able to install cmake using the classical approach of using the .pkg installer and performing the installation under /opt/local/. So, I guess the whole issue arises with the custom installation directory. On the other hand, I definitely prefer to have the ability to install macports under a custom install dir like the one I was trying to install stuff. It is much more convenient on migrations because in many cases I just transfer some configuration files from the directory that was dedicated to the previous OS release to the one for the newest OS release.

[michaelld (Michael Dickens)]

I don't know if this ticket is still an issue ... the build error is:

:info:build ld: warning: ignoring file /Library/Frameworks/libcurl.framework/libcurl, file was built for unsupported file format ( 0xFE 0xED 0xFA 0xCE 0x00 0x00 0x00 0x12 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x06 ) which is not the architecture being linked (x86_64): /Library/Frameworks/libcurl.framework/libcurl

This directory is a place to install non-System provided frameworks; 'port' provides 'curl' already, so I'd recommend removing this framework if you don't otherwise know what it's there for (and, it's for the wrong ABI arch anyway).

Then do:

sudo port clean cmake
sudo port selfupdate
sudo port install cmake

and see if that works. We try hard to be specific about dependencies / arguments when building, but we can't catch them all ;)

[michaelld (Michael Dickens)]

I'm closing this ticket as "works for me" since it does & I think the issue is with a foreign framework. If anyone disagrees, please reopen and respond on-ticket with more info.