Re: PowerPC macppc cross compile problem with libtool

On 12/28/20 1:52 PM, Bob McGowan wrote:
> Hi,
>
> My old Mac G3 B&W is now running NetBSD 9.1, with a new kernel cross 
> compiled on my Debian Gnu/Linux system.
>
> I'm now trying to cross compile Samba4 and have come up against a 
> problem with the libtool portion.
>
> The specific error from 'bmake' is:
>
> => Build dependency libxslt-[0-9]*: NOT found
> => Verifying package-install for ../../textproc/libxslt
> => Bootstrap dependency digest>=20010302: found digest-20190127
> => Checksum SHA1 OK for libxslt-1.1.34.tar.gz
> => Checksum RMD160 OK for libxslt-1.1.34.tar.gz
> => Checksum SHA512 OK for libxslt-1.1.34.tar.gz
> ===> Installing dependencies for libxslt-1.1.34nb4
> => Tool dependency cross-libtool-base-powerpc>=2.4.2nb9: NOT found
> => Verifying package-install for ../../cross/cross-libtool-base
> => Bootstrap dependency digest>=20010302: found digest-20190127
> ===> Installing binary package of cross-libtool-base-x86_64-2.4.6nb5
> pkg_add: package `cross-libtool-base-x86_64-2.4.6nb5' already recorded 
> as installed
> ERROR: [depends.mk] A package matching 
> ``cross-libtool-base-powerpc>=2.4.2nb9'' should
> ERROR:     be installed, but one cannot be found.  Perhaps there is a
> ERROR:     stale work directory for ../../cross/cross-libtool-base?
> *** Error code 1
>
> Stop.
> bmake[1]: stopped in 
> /home/rmcgowan/src/netbsd/usr/pkgsrc/textproc/libxslt
> *** Error code 1
>
> Stop.
> bmake: stopped in /home/rmcgowan/src/netbsd/usr/pkgsrc/net/samba4
>
> The problem begins with a message from 'pkg_add' about 
> cross-libtool-base... being recorded as installed but not being found.
>
> There is also the section in .../pkgsrc/doc/HOWTO-use-crosscompile 
> that tells me to run a 'pkg_add' with various options to "install" 
> libtool scripts.
>
> Since I'm on a Linux box, I don't have a pkg_add in my PATH.  I did 
> find a file in .../pkgsrc/bootstrap/work/sbin/ with the right name and 
> that is x86_64 so that should probably be what I should be using.  
> There are also other instances of pkg_add in other locations.
>
> No mention is made of options to use, environment variables, etc. to 
> run this within the pkgsrc space as an unprivileged user.
>
> Any recommendations?
>
> Thanks,
>
> Bob
>
I just figured out the pkg_add problem was because I had not added the 
required sbin directory to my PATH.  So that bit is solved.

I still would like to know just how to run the pkg_add command for 
libtool.  The "HOWTO..." simply says:

     pkg_add -m powerpc 
/path/to/powrpc/All/cross-libtool-base-powerpc-<version>.tgz

Running this from the cross-libtool-base directory, after 'bmake 
package', the command returns almost instantly, with no output but an 
exit status of zero, indicating it was "successful".

I find there are 3 files in /.../pkg/bin: libtool libtoolize shlibtool

Apparently this is what was needed because 'bmake package' ran past the 
point of the original error.

Apologies for the noise.

Bob