libplist 1.8 does not compile with clang

[ja_macports@…]

But it does if I do:

sudo port install libplist configure.compiler=llvm-gcc-4.2

[mparchet@…]

Cc Me!

[mparchet@…]

Hello,

I'm updating my macport version from 2.0.3 to 2.0.4. My Xcode version is 4.3. I have several warning Warning: Xcode appears to be installed but xcodebuild is unusable; some ports will likely fail to build.

Can you help me please ?

Best regards

mparchet

[barrasstim@…]

CC me!

[ryandesign (Ryan Carsten Schmidt)]

Has duplicate #33624.

[ryandesign (Ryan Carsten Schmidt)]

Replying to mparchet@…:

I'm updating my macport version from 2.0.3 to 2.0.4. My Xcode version is 4.3. I have several warning Warning: Xcode appears to be installed but xcodebuild is unusable; some ports will likely fail to build.

If you still need help with this, please ask on the macports-users mailing list; it has nothing to do with this ticket.

[mparchet@…]

Hello, I wrote an email to macport userp mailing list but I diem't have any answer

Can you help me please ?

Best regards

mparchet

[larryv (Lawrence Velázquez)]

Replying to mparchet@…:

I wrote an email to macport userp mailing list but I diem't have any answer

You did get an answer. Ryan replied and asked you to check whether you have installed Xcode properly. You never followed up.

Please stop posting comments on this ticket, as it is completely unrelated to the problem you are having.

[mparchet@…]

See attachment for more details as main2.log

[mparchet@…]

Hello,

Sorry It desen't work but all is up to date exept amarok witch I can't install amarok @2.4.3 because libplist 1.8 donpt compile.

Her's below my consol output.

sudo port install amarok @2.4.3
--->  Computing dependencies for amarok
--->  Dependencies to be installed: libgpod libplist
--->  Building libplist
Error: Target org.macports.build returned: shell command failed (see log for details)
Error: Failed to install libplist
Log for libplist is at: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_textproc_libplist/libplist/main.log
Error: The following dependencies were not installed: libgpod libplist
Error: Status 1 encountered during processing.
To report a bug, see <http://guide.macports.org/#project.tickets>

Can you help me please ?

Best regards

mparchet

[ryandesign (Ryan Carsten Schmidt)]

Michael, the log you attached above​ says:

make[2]: *** No rule to make target `libcnary/CMakeFiles/libcnary.dir/node.c.o', needed by `src/libplist.1.1.8.dylib'.  Stop.

Since I also note from the log that MacPorts is starting 8 make jobs on your system, this could be a parallel build problem -- again a totally different problem from the one this ticket is about. You could work around this by appending "build.jobs=1" to your port install command.

Then, you attached yet another main.log to ​the email you sent to the mailing list. That log says:

error: non-void function 'base64decode' should return a value [-Wreturn-type]

That finally sounds like a clang-related build error, the one described in this ticket, and which you should be able to work around by using the command given in this ticket's description.

That also seems like the case for the main.log Lawrence Velázquez attached to ​his mailing list post:

error: non-void function 'node_insert' should return a value [-Wreturn-type]

[ryandesign (Ryan Carsten Schmidt)]

Replying to ryandesign@…:

this could be a parallel build problem

I confirmed this problem and disabled parallel building for this port in r90905. That still leaves the clang issue.

[larryv (Lawrence Velázquez)]

Replying to ryandesign@…:

That also seems like the case for the main.log Lawrence Velázquez attached to ​his mailing list post:

error: non-void function 'node_insert' should return a value [-Wreturn-type]

Switching to llvm-gcc did correct the problem. For some reason I thought I didn't have system llvm-gcc anymore, but I double-checked and it's still there.

[ryandesign (Ryan Carsten Schmidt)]

In r90911 I forced the port to use llvm-gcc-4.2 instead of clang. Better would be to report the problem to the developers of the software so they can fix this in a future version. Maintainer, or someone, can you please do that, and post a link to the upstream bug report here? Thanks.