Created attachment 251331 [details] complete build log Encountered on CURRENT 15.0: gmake[4]: Entering directory '/usr/ports/devel/binutils/work-native/binutils-2.40/binutils' /bin/sh ./libtool --tag=CC --mode=link cc -W -Wall -Wstrict-prototypes -Wmissing-prototypes -Wshadow -I/usr/local/include -O2 -pipe -fstack-protector-strong -isystem /usr/local/include -fno-strict-aliasing -Wl,--undefined-version -fstack-protector-strong -o readelf readelf.o version.o unwind-ia64.o dwarf.o demanguse.o elfcomm.o ../libctf/libctf-nobfd.la /usr/local/lib/libintl.so -Wl,-rpath -Wl,/usr/local/lib ../libiberty/libiberty.a -lz -L/usr/local/lib -lzstd -Llib -lmsgpack-c ../libsframe/libsframe.la -L/usr/local/lib cd: lib: No such file or directory libtool: link: cannot determine absolute directory name of `lib' gmake[4]: *** [Makefile:1055: readelf] Error 1
I believe it might be a problem with devel/msgpack-c -- which binutils can use as an optional dependency. Uninstalling msg-pack-c might let you build binutils. This is how the pkg-config file for msg-pack-c appears after I have installed 6.0.1 via pkg on FreeBSD-15: /usr/local/libdata/pkgconfig/msgpack-c.pc prefix=/usr/local exec_prefix=/usr/local libdir=lib includedir=include I believe "libdir" and "include" should be set relatively to ${prefix}...
(In reply to Marcin Cieślak from comment #1) Correct. I'm running 15-CURRENT here and have no problems whatsoever with binutils. I can either close this or you can reassign this to the devel/msgpack-c maintainer.
https://github.com/msgpack/msgpack-c/pull/1124/files I have submitted this to fix this upstream