libbert @0.0.1: install_name not set

[afbrand@…]

LibBERT fails to build with the following included int he output:

Could not open libbert.dylib: Error opening or reading file (referenced from /opt/local/lib/libbert_capi.dylib)
DEBUG: Marking /opt/local/lib/libbert_capi.dylib as broken

The file seems in tact, however:

ll /opt/local/lib/libbert.dylib
-rwxr-xr-x  1 root  admin  69096 May  8 01:57 /opt/local/lib/libbert.dylib*

[afbrand@…]

Correction: Meant to add error details to summary.

[kurthindenburg (Kurt Hindenburg)]

Cc Me!

[kurthindenburg (Kurt Hindenburg)]

It doesn't appear to be an active project and there is nothing in macports that depends on it. Perhaps it should be removed? What were you installing it for?

[afbrand@…]

Replying to khindenburg@…:

It doesn't appear to be an active project and there is nothing in macports that depends on it. Perhaps it should be removed? What were you installing it for?

I too see that this project hasn't been updated in many years. I don't have any hard dependency on it. I was exploring it as part of some new Erlang development. I wouldn't object if it would make more sense to remove it.

[ryandesign (Ryan Carsten Schmidt)]

The build simply isn't setting the libraries' install_names correctly. We could fix that.

[ryandesign (Ryan Carsten Schmidt)]

And that's because it's building with cmake but not using the cmake portgroup, even though I mentioned it in comment:ticket:33120:1.

[ryandesign (Ryan Carsten Schmidt)]

Fixed by adding the cmake portgroup in r148864.