On Wed, 24 Apr 2019, Willem Offermans wrote:> Dear FreeBSD friends, > > Almost every third port update ends with ``configure.ac:6: error: required file './ltmain.sh' not found``. > See output below! > > I can copy ltmain manually: cp -p /usr/local/share/libtool/build-aux/ltmain.sh ., but this is quite > cumbersome. > > Does anyone know a more elegant solution? > > > Erroneous example: > > > => SHA256 Checksum OK for libinotify-kqueue-libinotify-kqueue-20180201_GH0.tar.gz. > ===> Patching for libinotify-20180201_1 > ===> libinotify-20180201_1 depends on package: autoconf>=2.69 - found > ===> libinotify-20180201_1 depends on package: automake>=1.16.1 - found > ===> libinotify-20180201_1 depends on executable: libtoolize - found > ===> Configuring for libinotify-20180201_1 > configure.ac:6: installing './compile' > configure.ac:6: installing './config.guess' > configure.ac:6: installing './config.sub' > configure.ac:2: installing './install-sh' > configure.ac:6: error: required file './ltmain.sh' not found > configure.ac:2: installing './missing' > Makefile.am: installing './depcomp' > autoreconf-2.69: automake failed with exit status: 1 > *** Error code 1 > > Stop. > make: stopped in /usr/ports/devel/libinotify > > ===>>> make build failed for devel/libinotify > ===>>> Aborting update > > ===>>> Update for libinotify-20180201 failed > ===>>> Aborting update > > > Wiel Offermans > Willem at Offermans.Rompen.nl > >FWIW I had this problem myself after rebulding a few ports, and in that case it turned out to be gawk being broken due to it depending on a version of libreadline.so that was no longer present. A quick ldd `which gawk` will tell you if that's the problem in your case too and, if that is the case, rebuilding gawk should fix it. /Jesper> > > _______________________________________________ > freebsd-stable at freebsd.org mailing list > lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe at freebsd.org"
Dear Jesper and FreeBSD friends, Thank you for your response. Unfortunately it is probably not gawk in my case, which causes trouble. However, your response indicates that the problem will be solved after I have updated/reinstalled the guilty one. So for the time being, I have to push some updates/(re)installations by hand myself and pray that it will hit the guilty port. I guess that is the easiest way. If this is not working, I will consider to look at autoreconf. Wiel Offermans Willem at Offermans.Rompen.nl> On 24 Apr 2019, at 12:14, Jesper Christensen <vol at Update.UU.SE> wrote: > > ldd `which gawk`