llvm-3.0 +universal build fails when using Apple's gcc driver-driver (Tiger, Leopard, SL)

[spacecataz]

Greetings. I am trying to install netcdf-fortran +universal. Many of the dependencies install without issue until llvm-3.0 (when upgrading gcc45, likely to universal). The log file, attached, is not helping. Any thoughts?

[ryandesign (Ryan Carsten Schmidt)]

Since this was not a clean attempt, please "sudo port clean llvm-3.0", then try again, then attach the new main.log file.

[spacecataz]

build log

[spacecataz]

My apologies; fixed. Note that I can only get the error through installing netcdf-fortran +universal.

[ryandesign (Ryan Carsten Schmidt)]

I wonder if it's a parallel build problem. Does it get any further or finish if you turn off parallel building, like this:

sudo port install llvm-3.0 +universal build.jobs=1

[spacecataz]

Replying to ryandesign@…:

I wonder if it's a parallel build problem. Does it get any further or finish if you turn off parallel building, like this:

sudo port install llvm-3.0 +universal build.jobs=1

No, this does not seem to change anything.

[a.sewall.ford@…]

I've also experiencing this issue, the call to link libLLVM-3.0.dylib (line 3632 in the attached log) is failing silently and the dylib is not being linked or place in the appropriate location.

I am experiencing the same error using build.jobs=1.

[a.sewall.ford@…]

Cc Me!

[ryandesign (Ryan Carsten Schmidt)]

Has duplicates #34688 and #34704.

[jeremyhu (Jeremy Huddleston Sequoia)]

That looks to me like the bug in the gcc driver-driver which I fixed in apple-gcc42 with r91374. Apple's llvm-gcc uses the same driver-driver that they used for gcc-4.2, so it would have the same bug.

We can probably fix this by using clang in this case.

[jeremyhu (Jeremy Huddleston Sequoia)]

Although I expect the bug exists on Tiger and Leopard as well (which don't have clang available from XCode). I use apple-gcc-4.2 as my Tiger and Leopard default compiler, so that should work for both of those old cats, but that raises more dependency cycle concerns...

[petrsnd@…]

I've noticed that there hasn't been any activity on this issue for a couple weeks. Is there a way to work around this problem? I have a Mac 10.6 machine that I would really like to put gcc46 on. Can I request an earlier version of llvm-3.0 before this problem came up? I'm pretty new to MacPorts.

[jeremyhu (Jeremy Huddleston Sequoia)]

Please use the suggested workaround for now:

sudo port -v install llvm-3.0 configure.compiler=apple-gcc-4.2

[jeremyhu (Jeremy Huddleston Sequoia)]

Or:

sudo port -v install llvm-3.0 configure.compiler=clang

[andrewjacka@…]

Hi - How soon are we likely to have a solution to this? Not being able to install gcc is starting to be a major show-stopper.

Also slightly new to ports - The workaround that you suggest above... That doesn't seem to do much. As soon as you then try and install gcc, it goes back and tries to install/build llvm-3.0 with the same error.

[ryandesign (Ryan Carsten Schmidt)]

Replying to andrewjacka@…:

The workaround that you suggest above... That doesn't seem to do much. As soon as you then try and install gcc, it goes back and tries to install/build llvm-3.0 with the same error.

Jeremy's workaround above was supposed to result in a successful llvm-3.0 installation. If that's not what happened for you, please attach the main.log from the failed llvm-3.0 build attempt.

[andrewjacka@…]

Ah - Nope just worked it out (missing +universal from the command Jeremy used). My bad...

Replying to ryandesign@…:

Replying to andrewjacka@…:

The workaround that you suggest above... That doesn't seem to do much. As soon as you then try and install gcc, it goes back and tries to install/build llvm-3.0 with the same error.

Jeremy's workaround above was supposed to result in a successful llvm-3.0 installation. If that's not what happened for you, please attach the main.log from the failed llvm-3.0 build attempt.

[lucasvickers@…]

Cc Me!

[jeremyhu (Jeremy Huddleston Sequoia)]

r97624