Re: latest sbin/pkg updates seem to break HEAD

On Sat, Oct 26, 2013 at 02:42:49PM +0200, Rainer Hurling wrote:
> Am 26.10.2013 13:04, schrieb Matthias Andree:
> > Am 26.10.2013 12:56, schrieb Rainer Hurling:
> >> After svn update my 11.0-CURRENT box to r257152, the build breaks.
> >> Obviously there is something wrong with the newest patches for sbin/pkg
> >> (or libcrypt). Am I the only one observing this?
> >>
> >> Any help is appreciated,
> >> Rainer Hurling
> >>
> >>
> >> [..snip..]
> >> ===> usr.sbin/pkg (all)
> > ...
> >> cc  -O2 -pipe  -I/usr/src/usr.sbin/pkg/../../contrib/libyaml/include
> >> -std=gnu99 -Qunused-arguments -fstack-protector -Wsystem-headers -Werror
> >> -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes
> >> -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual
> >> -Wwrite-strings -Wswitch -Wshadow -Wunused-parameter -Wcast-align
> >> -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls
> >> -Wold-style-definition -Wmissing-variable-declarations -Wno-pointer-sign
> >> -Wno-empty-body -Wno-string-plus-int
> >> -L/usr/obj/usr/src/tmp/usr/lib/private -rpath /usr/lib/private -o pkg
> >> pkg.o dns_utils.o config.o -larchive -lelf -lfetch -lyaml -lsbuf -lssl
> >>
> >> /usr/obj/usr/src/tmp/usr/bin/ld: D: invalid DSO for symbol
> >> `EVP_PKEY_free' definition
> >> /usr/obj/usr/src/tmp/lib/libcrypto.so.7: could not read symbols: Bad value
> >> cc: error: linker command failed with exit code 1 (use -v to see invocation)
> >> *** Error code 1
> >> Stop.
> >> make[4]: stopped in /usr/src/usr.sbin/pkg

This should be fixed now. Sorry about that. It was compiling fine
without -lcrypto for me.

> > 
> > These can happen if a library is missing, for instance, -lcrypto is
> > apparently not mentioned on the linker's command line, but AFAIR the
> > clang linker accepts no unresolved symbols from .so when linking
> > executables, and -lssl likely needs -lcrypto.  This avoids run-time
> > surprises due to missing dependencies (on libcrypto, in this case).
> > 
> > Try pasting that command line with -lcrypto added after -lssl, and if
> > that helps, try to debug where the -lcrypto has been or gets lost, or
> > should get added.
> > 
> > HTH
> 
> Yep, adding -lcrypto seems to help. I patched usr.sbin/pkg/Makefile for it.
> 
> But I am wondering if nobody else has this problem? I did not change my
> systems sources before.
> 
> Many thanks for your fast reply and help,
> Rainer
> 
> 
> 
> --- Makefile.orig	2013-10-26 08:33:50.000000000 +0200
> +++ Makefile	2013-10-26 14:26:06.000000000 +0200
> _at__at_ -7,7 +7,7 _at__at_
>  CFLAGS+=-I${.CURDIR}/../../contrib/libyaml/include
>  .PATH:	${.CURDIR}/../../contrib/libyaml/include
>  DPADD=	${LIBARCHIVE} ${LIBELF} ${LIBFETCH} ${LIBYAML} ${LIBSBUF}
> -LDADD=	-larchive -lelf -lfetch -lyaml -lsbuf -lssl
> +LDADD=	-larchive -lelf -lfetch -lyaml -lsbuf -lssl -lcrypto
>  USEPRIVATELIB=	yaml
> 
>  .include <bsd.prog.mk>
> 
> _______________________________________________
> freebsd-current_at_freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe_at_freebsd.org"