Subject: Re: Pkgsrc on Tru64. Libtool problem
To: Alexey Lebedev <lebedev@zhtw.org.ru>
From: Tobias Nygren <tnn+nbsd@nygren.pp.se>
List: pkgsrc-users
Date: 08/24/2006 09:59:39
Alexey Lebedev wrote:
> Hello!
>
> Did anyone test last pkgsrc on alpha processor under Tru64 5.1b?
>
> Bootstrap succeeded but I couldn't build almost any package. For example
> bzip2:
>
> avl@axp3:~$ more log
> ===> Checking for vulnerabilities in bzip2-1.0.3
> => Checksum SHA1 OK for bzip2-1.0.3.tar.gz.
> => Checksum RMD160 OK for bzip2-1.0.3.tar.gz.
> ===> Building for bzip2-1.0.3
>
> If compilation produces errors, or a large number of warnings,
> please read README.COMPILATION.PROBLEMS -- you might be able to
> adjust the flags in this Makefile to improve matters.
>
> ...
>
> libtool  --mode=compile cc -O2 -ieee -D_FILE_OFFSET_BITS=64 -c
> blocksort.c
> libtool: compile: libobj name `blocksort.lo' may not contain shell
> special characters.
> *** Error code 1
>
> Stop.
> bmake: stopped in /usr/pkgsrc/archivers/bzip2/work/bzip2-1.0.3
> *** Error code 1
>
> Stop.
> bmake: stopped in /usr/pkgsrc/archivers/bzip2
> ===>
> ===> There was an error during the ``build'' phase.
> ===> Please investigate the following for more information:
> ===>      * log of the build
> ===>      * /usr/pkgsrc/archivers/bzip2/work/.work.log
> ===>
> *** Error code 1
>
> Stop.
> bmake: stopped in /usr/pkgsrc/archivers/bzip2
> 	
>
> Any suggestions would be very appriciated.
>
> Best regards, Alexey Lebedev.
>   

I remember this problem, but I can't recall the fix. It might have
been a sed problem. Try to edit /usr/pkg/bin/libtool (it's a text file)
and remove the "special characters" test. I'll install a fresh Tru64
box and do a long overdue bulk build & regression hunt tonight.

-Tobias