Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 24 Apr 2019 12:14:41 +0200
From:      Jesper Christensen <vol@Update.UU.SE>
To:        Willem Offermans <Willem@Offermans.Rompen.nl>
Cc:        freebsd-ports@freebsd.org, freebsd-stable@freebsd.org
Subject:   Re: ltmain.sh not found
Message-ID:  <20190424101441.GA7495@Update.UU.SE>
In-Reply-To: <083A2F75-E5A5-4A5E-AB70-63EC0217DE19@Offermans.Rompen.nl>
References:  <083A2F75-E5A5-4A5E-AB70-63EC0217DE19@Offermans.Rompen.nl>

next in thread | previous in thread | raw e-mail | index | archive | help
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@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@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20190424101441.GA7495>