openssh 5.0p1_0 build failure

[hanche@…]

It seems to look for libcom_err in a location where it does not exist. There is one in /usr/lib, but it is not used.

/usr/bin/gcc-4.0 -o ssh ssh.o readconf.o clientloop.o sshtty.o sshconnect.o sshconnect1.o
  sshconnect2.o -L. -Lopenbsd-compat/ -L/opt/local/lib -L/opt/local/lib -L/opt/local/lib
  -fstack-protector-all -lssh -lopenbsd-compat -lcrypto -lz  -dynamic -O2 -Wall
  -Wpointer-arith -Wuninitialized -Wsign-compare -Wno-pointer-sign -fstack-protector-all
  -Wl,-search_paths_first -lgssapi_krb5 -lkrb5 -lk5crypto -lcom_err -lresolv

ld: file not found: /opt/local/lib/libcom_err.1.dylib

This is on PPC, macosx 10.5.4.

[jmr@…]

Assigning to maintainer.

[vinc17@…]

Could you type:

which krb5-config
krb5-config --libs gssapi

You should get something like:

/usr/bin/krb5-config

and

-L/usr/lib -Wl,-search_paths_first -lgssapi_krb5 -lkrb5 -lk5crypto -lkrb5support -lcom_err -lresolv

Note the /usr/lib here.

[hanche@…]

krb5-config is /opt/local/bin/krb5-config, provided by heimdal.

; krb5-config --libs gssapi
-L/opt/local/lib -lgssapi -lheimntlm -lkrb5 -lhx509 -lcom_err -lcrypto -lasn1 -lroken -lresolv
; /usr/bin/krb5-config --libs gssapi
-dynamic -Wl,-search_paths_first -lgssapi_krb5 -lkrb5 -lk5crypto -lcom_err -lresolv

No /usr/lib in sight in either. (I have heimdal because gnome-vfs depends on it, and a whole host of other stuff depends on gnome-vfs in turn.)

[vinc17@…]

You should uninstall heimdal (or install the latest version, but that one is useless anyway, as no ports should depend on heimdal any longer). In particular, the latest version of gnome-vfs no longer depends on heimdal (the system kerberos from Mac OS X replaces it); you can check that with "port info gnome-vfs". It is possible that MacPorts still says that some ports depend on heimdal even if they are no longer activated. If after the upgrade, some ports no longer work, you need to reinstall them (don't forget the "port clean ...") so that they are linked against the right libraries.

For more information, see the other bugs related to heimdal (may be closed).

[hanche@…]

Yep, uninstalling heimdal fixed it. Clearly, the output of “port dependents heimdal” can be misleading when you have deactivated but installed ports. How hard would it be to provide a meaningful error message in these cases?

[vinc17@…]

Replying to hanche@…:

Yep, uninstalling heimdal fixed it. Clearly, the output of “port dependents heimdal” can be misleading when you have deactivated but installed ports. How hard would it be to provide a meaningful error message in these cases?

I don't know, but bug #11501 is about this.

I'm closing this bug as this was due to an old version of heimdal and the bug has already been fixed on this side.

[vinc17@…]

Well, in fact, fixing #11501 would not necessarily avoid the warning because heimdal would have to be uninstalled first, while the old versions of ports depending on heimdal would still be installed. To solve this kind of problem, MacPorts would have to introduce a Conflict field and resolve dependencies and conflicts on a set of ports.

[anonymous]

Milestone Port Bugs deleted