Re: bulk builds

[Jonathan Perkin <jperkin%pkgsrc.org@localhost>]

* On 2015-07-08 at 09:34 BST, Richard PALO wrote:

> Jonathan, looks like we've a problem with directory naming with multilib gcc between ABI=32 and ABI=64
> from your i386 bulk build:
> >   CXXLD    mesa_dri_drivers.la
> > g++: error: /opt/tools/gcc49/lib/gcc/x86_64-sun-solaris2.11/4.9.2/32/crtbegin.o: No such file or directory
> > g++: error: /opt/tools/gcc49/lib/gcc/x86_64-sun-solaris2.11/4.9.2/32/crtend.o: No such file or directory

Yeh, the problem is that gcc49 was bumped but libtool still hard codes the
old path:

  $ grep crtbegin /opt/local/bin/libtool
  predep_objects="/usr/lib/amd64/crti.o /usr/lib/amd64/values-Xa.o /opt/tools/gcc49/lib/gcc/x86_64-sun-solaris2.11/4.9.2/crtbegin.o"

  $ /opt/tools/sbin/pkg_info -qL gcc49 | grep crtbegin
  /opt/tools/gcc49/lib/gcc/x86_64-sun-solaris2.11/4.9.3/32/crtbegin.o
  /opt/tools/gcc49/lib/gcc/x86_64-sun-solaris2.11/4.9.3/crtbegin.o

i.e. 4.9.2 vs 4.9.3.

In our release builds we've patched libtool to remove these hard coded
paths and instead rely on GCC to do the right thing:

  https://github.com/joyent/pkgsrc/commit/d59ce5f512dea0189e8f5d83cbf9ac4894ba227f

I'd like to get this into the next libtool update, it matches other
platforms and avoids problems like this.

For now I'll manually remove libtool for the upstream-trunk builds and let
it rebuild to pick up the new path.

Thanks,

-- 
Jonathan Perkin       www.perkin.org.uk
github.com/jperkin  twitter.com/jperkin