atlas @3.10.1_3: configuration fails

[jdgleeson]

:info:configure make: /usr/bin/gcc-4.0 -m32 -force_cpusubtype_ALL: Command not found
:info:configure make: *** [atlconf_misc.o] Error 127

Log attached

[jdgleeson]

This is on OS X 10.5.8 PPC (dual G5)

[Veence (Vincent)]

There is something wrong in the sense that you should not get the --cc=/usr/bin/gcc-4.0. I freely admit I have not tested the Portfile on my G5 MacPro. I’ll try to fix it today, or tonight at worse. I also apologize for transforming you into the perfect guineapig each time Atlas Portfile gets updated! Cheers!

[jmroot (Joshua Root)]

It's trying to execute the compiler and cflags as a single string. Same error happens with any command if you do that:

$ 'clang -m32 -force_cpusubtype_ALL'
zsh: command not found: clang -m32 -force_cpusubtype_ALL

[Veence (Vincent)]

Yes, that’s part of it. But it should not chose gcc-4.0 as a compiler, and that’s because the option is called too soon during the build, at a time where ${configure.cc} is not yet set.

[Veence (Vincent)]

John, there were several bugs at stake. They should be fixed in r104573 (tested on my ppc64 machine). Please try again and report any error you still might find. Vincent

[Veence (Vincent)]

Darn, I forgot to change something. r104574 should fix everything.

[jdgleeson]

Vince, I think the configuration problems are fixed. Now I get fatal errors during tuning. I think this is a problem I need to report upstream, unrelated to configuration. I've attached the log file so you can look at it and see if you agree. I'm trying again to see if the problem is repeatable.

[jdgleeson]

log of build failure

[jdgleeson]

Atlas installed on the second attempt!! It took about 12 hours. Perhaps other tasks I was running during the first attempt interfered with the tuning process.

[jdgleeson]

It installed only libatlas.a and libsatlas.dylib; no thread library. Unfortunately, I erroneously thought the -k option kept log files. I'm re-installing atlas with 'keeplogs yes' in my macports.conf. I'll open a new ticket when I have a log file.

[larryv (Lawrence Velázquez)]

Replying to jdgleeson@…:

Unfortunately, I erroneously thought the -k option kept log files.

It does. Did you run port install -k atlas or port -k install atlas? (I don’t even know if the former works, lol.)

[Veence (Vincent)]

That’s a pity you didn’t keep the log. I looked at your previous logs, the configure script correctly detects you have two processors and set the number of threads to two.

There was a slight bug about the vectorizing unit, I have added some lines in the Portfile to force the use of the Altivec unit (-V 2 somewhere).

[jdgleeson]

Replying to larryv@…:

Replying to jdgleeson@…:

Unfortunately, I erroneously thought the -k option kept log files.

It does. Did you run port install -k atlas or port -k install atlas? (I don’t even know if the former works, lol.)

So I wasn't dreaming. I thought I had regularly saved logs using -k (port -k install atlas) when I first started using MacPorts about a year ago so I could study them. It looks like I've uncovered some bug in the atlas port.

[cooljeanius (Eric Gallager)]

Cc Me!

[Veence (Vincent)]

Nobody seems to care anymore. I close this bug, which is somehow unrelated to Atlas anyway. Please reopen a new ticket if necessary.