Re: ltmain.sh not found
Dear FreeBSD friends, No, I have not yet considered using poudriere. I’m using portmaster for years now and I was too lazy to look for a better/another tool. When I have time, I will dig into poudriere. I assume there is documentation/tutorial around that will get me going. The man pages will also be helpful. Thank you for your suggestion. Wiel Offermans wil...@offermans.rompen.nl > On 25 Apr 2019, at 14:58, Andreas Nilsson wrote: > > > > On Thu, Apr 25, 2019 at 2:28 AM Kevin Oberman <mailto:rkober...@gmail.com>> wrote: > On Wed, Apr 24, 2019 at 9:05 AM Christoph Moench-Tegeder <mailto:c...@burggraben.net>> > wrote: > > > ## Willem Offermans (wil...@offermans.rompen.nl > > <mailto:wil...@offermans.rompen.nl>): > > > > > 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. > > > > There's sysutils/bsdadminscripts, which provides pkg_libchk: that's a > > tool for checking if any port misses a shared library. It has been > > rather helpful back when I was using portupgrade... > > > > Regards, > > Christoph > > > > I believe bsdadminscripts has been withdrawn. You should use "pkg check -B" > to check. > -- > Kevin Oberman, Part time kid herder and retired Network Engineer > E-mail: rkober...@gmail.com <mailto:rkober...@gmail.com> > PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 > > > Have you considered using poudriere to build your packages? It usually avoids > these types of failures. > > Best regards > Andreas ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: ltmain.sh not found
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 wil...@offermans.rompen.nl > On 24 Apr 2019, at 12:14, Jesper Christensen wrote: > > ldd `which gawk` ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: ltmain.sh not found
Dear FreeBSD friends, Ports tree should be up to date. $ svnlite info /usr/ports/ Path: /usr/ports Working Copy Root Path: /usr/ports URL: svn://svn0.eu.freebsd.org/ports/head Relative URL: ^/head Repository Root: svn://svn0.eu.freebsd.org/ports Repository UUID: 35697150-7ecd-e111-bb59-0022644237b5 Revision: 499718 Node Kind: directory Schedule: normal Last Changed Author: tobik Last Changed Rev: 499718 Last Changed Date: 2019-04-23 08:12:45 +0200 (Tue, 23 Apr 2019) I had recently updated from FreeBSD 11.2 to 12.0. Thereafter I have run ``portmaster -ad``, then the problems appear. It should be something simple like running autoreconf during update/installation. But I don’t know yet how to build this in into the ports and portmaster. Wiel Offermans wil...@offermans.rompen.nl > On 24 Apr 2019, at 09:08, Dima Pasechnik wrote: > > On Wed, Apr 24, 2019 at 7:58 AM Willem Offermans > wrote: >> 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? > > see > https://www.gnu.org/software/automake/manual/html_node/Error-required-file-ltmain_002esh-not-found.html > > That is, teach the script in question to run autoreconf, if you want > this to work. > > > HTH > Dima >> >> >> 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 >> wil...@offermans.rompen.nl >> >> >> >> >> ___ >> freebsd-po...@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-ports >> To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
ltmain.sh not found
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 wil...@offermans.rompen.nl ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
ltmain not found
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 wil...@offermans.rompen.nl ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Crontab Question
Dear FreeBSD friends, Yes, specifying whole directories is a bit counterintuitive, but you get used to it. To me it became part of crontab, with only a vague understanding of why. Probably all of us went through this process of incorporation once. Wiel Offermans wil...@offermans.rompen.nl > On 12 Apr 2019, at 00:38, Software Info wrote: > > Thanks so much for all the replies. It was true that I had to hardcode every > path but thankfully it is working now. Really appreciate the assistance. > > > Kind Regards > SI > > > > From: Richard Mackerras > Sent: Thursday, April 11, 2019 11:53 AM > To: Software Info > Cc: Walter Cramer; freebsd-stable@freebsd.org; Jonathan Chen > Subject: Re: Crontab Question > > In your script put a few commands outputting to a check file > > pwd > /tmp/checkfile > > Add a few more like > > ENV >> /tmp/checkfile > > Just to make sure it really is in the directory you expect with the > environment you expect. > > If you want it to be run as you never use the root crontab unless you want > really crap security. > > Cheers > > > Sent from my iPad > >> On 11 Apr 2019, at 16:29, Software Info wrote: >> >> Well thanks for all the input. I just have to tp keep working at it. Again, >> much appreciated. >> >> >> Regards >> SI >> >> Sent from Mail for Windows 10 >> >> From: Walter Cramer >> Sent: Wednesday, April 10, 2019 4:40 PM >> To: Software Info >> Cc: Jonathan Chen; freebsd-stable@freebsd.org >> Subject: RE: Crontab Question >> >>> On Wed, 10 Apr 2019, Software Info wrote: >>> >>> OK. So although the script is located in my home directory, it doesn’t >>> start there? Sorry but I don’t quite understand. Could you explain a >>> little further please? >> >> Both 'cp' and 'ls' are located in /bin. But if I run the 'ls' command in >> /root, 'ls' can't find 'cp' (unless I tell it where to look) - even though >> /bin *is* in my PATH - >> >> server7:/root # ls cp >> ls: cp: No such file or directory >> server7:/root # ls /bin/cp >> /bin/cp >> >> Where the system looks for *commands*, to execute, is different from where >> it looks for other files, which those commands use. The latter is >> generally only the current directory (unless you tell it otherwise). >> When cron runs a script as root, "current directory" will be /root. >> >> BUT - for security and other reasons, it would be better to have cron run >> your script as you (not root), and as '/home/me/myscript' (instead of >> adding your home directory to PATH in /etc/crontab). >> >> -Walter >> >> ___ >> freebsd-stable@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-stable >> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" > > ___ > freebsd-stable@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
