Automake creation error.. generic or just me?

Tijl Coosemans tijl at FreeBSD.org
Wed Jul 25 16:38:11 UTC 2018


On Wed, 25 Jul 2018 22:43:05 +0800 Julian Elischer <julian at freebsd.org> wrote:
> I'm not exactly sure where the error come from.. possibly the find, if 
> stderr and stdout are not synchronous.
> 
> Has anyone else seen this?  or understand it?
> 
> 
> ===>  Building for automake-1.16.1  
> --- doc/aclocal.1 ---
> --- doc/automake.1 ---
> --- bin/automake ---
> 
> [...]ls pkg/All
> 
> /usr/bin/make  install-data-hook
>   chmod +x 
> '/usr/ports/devel/automake/work/stage/usr/local/share/automake-1.16/config.guess'
>   chmod +x 
> '/usr/ports/devel/automake/work/stage/usr/local/share/automake-1.16/config.sub'
>   chmod +x 
> '/usr/ports/devel/automake/work/stage/usr/local/share/automake-1.16/install-sh'
>   chmod +x 
> '/usr/ports/devel/automake/work/stage/usr/local/share/automake-1.16/mdate-sh'
>   chmod +x 
> '/usr/ports/devel/automake/work/stage/usr/local/share/automake-1.16/missing'
>   chmod +x 
> '/usr/ports/devel/automake/work/stage/usr/local/share/automake-1.16/mkinstalldirs'
>   chmod +x 
> '/usr/ports/devel/automake/work/stage/usr/local/share/automake-1.16/ylwrap'
>   chmod +x 
> '/usr/ports/devel/automake/work/stage/usr/local/share/automake-1.16/depcomp'
>   chmod +x 
> '/usr/ports/devel/automake/work/stage/usr/local/share/automake-1.16/compile'
>   chmod +x 
> '/usr/ports/devel/automake/work/stage/usr/local/share/automake-1.16/py-compile'
>   chmod +x 
> '/usr/ports/devel/automake/work/stage/usr/local/share/automake-1.16/ar-lib'
>   chmod +x 
> '/usr/ports/devel/automake/work/stage/usr/local/share/automake-1.16/test-driver'
>   chmod +x 
> '/usr/ports/devel/automake/work/stage/usr/local/share/automake-1.16/tap-driver.sh'
> find: 
> /usr/ports/devel/automake/work/stage/usr/local/lib/perl5/site_perl: No 
> such file or directory
> ====> Compressing man pages (compress-man)
> ===>  Installing for automake-1.16.1
> ===>   Registering installation for automake-1.16.1 as automatic  
> *** Error code 70

Possibly caused by https://svnweb.freebsd.org/ports?view=revision&revision=473539


More information about the freebsd-ports mailing list