BUG: esound will not build because of hardwired /usr/bin references

[x11@…]

I tried to upgrade esound yesterday from 2.34 to 2.35. The build failed because libtool did not know what to do with

-framework Coreaudio and did not pass it forward to the link stage. I found

that the error shows up if you have

libtool installed through dp, or perhaps it is just a feature of defining

--prefix=${prefix}. The configure

script creates a local link ltmain.sh which points to

${prefix}/share/libtool/ltmain.sh. But hardcoded somewhere

in the scripts that come with the source are calls to /usr/bin/libtool, and

when it calls the linked ltmain.sh

script, that script must not know what to do with -framework Coreaudio. When

you see the error, the directive

-framework Coreaudio is at the end of the final libtool handoff to the linker

stage, but it is not in the command

libtool creates for ld. Moving into the install directory and changing the

symlinked file to point to

/usr/share/libtool/ltmain.sh then calling `port install esound' works.

It seems that someone would have seen this before.

[pogma@…]

Either update the package to libtool-1.5.14 (allows -framework through when building shared libraries, you need 1.5.18 (not yet out) to work when building both shared libs and apps), or use -Wl,- framework,Carbon etc..

Peter

[x11@…]

(In reply to comment #1) I thought that I stated I had ${prefix}/bin/libtool (1.5.16) installe, but I must have cut that part of my comments. The problem then appears to be somewhere either in the esound configure script (because regardless of the file to which ./ltmain.sh points, the linker command always calls /usr/bin/libtool), or it is because ${prefix}/share/libtool/ltmain.sh does not yet recognize darwin8 as a darwin system.

[mww@…]

assign to maintainer

[danchr@…]

Unassigning since I no longer use DarwinPorts.

[markd@…]

This problem is no longer reproducible and this should be closed.

[danchr@…]

I'm back.

[danchr@…]

Resolved WFM as per comment #5.