On Mon, Jan 30, 2006 at 12:02:54AM +0100, Krister Walfridsson wrote:
> pkgsrc bulk build results
> NetBSD 1.6.2/i386
> [...]
> sysutils/xentools20                bouyer@NetBSD.org

===> Configuring for xentools20-2.0.7nb5
=> "Fixing hardcoded paths."
===> Building for xentools20-2.0.7nb5
/bin/mkdir -p /tmp/bulktmp/sysutils/xentools20/work/xen-2.0/tools/libxc/xen/NetBSD
/bin/cp /usr/pkgsrc/sysutils/xentools20/files/xenio.h /tmp/bulktmp/sysutils/xentools20/work/xen-2.0/tools/libxc/xen/NetBSD
gmake[1]: Entering directory `/tmp/bulktmp/sysutils/xentools20/work/xen-2.0/tools/libxutil'
/usr/pkg/bin/gmake libxutil.so  libxutil.so.2.0 libxutil.so.2.0.0 libxutil.a
gmake[2]: Entering directory `/tmp/bulktmp/sysutils/xentools20/work/xen-2.0/tools/libxutil'
gcc -I/usr/pkg/include/python2.3 -I/usr/include -I/usr/pkg/include -DPIC -O2 -I/usr/pkg/include/python2.3 -I/usr/include -I/usr/pkg/include -m32 -march=i686 -m32 -march=i686 -Wall -Werror -O3 -fno-strict-aliasing -Wp,-MD,.build.d -m32 -march=i686 -Wall -Werror -O3 -fno-strict-aliasing -Wp,-MD,.allocate.opic.d -fPIC -c -o allocate.opic allocate.c
cc1: Invalid option `32'

This package has not changed (or at last, no relevant changes) since
2005Q4 and it used to build fine on 1.6.2 (at last it didn't appear broken
in bulk builds). Any idea what's causing this ?

-- 
Manuel Bouyer <bouyer@antioche.eu.org>
     NetBSD: 26 ans d'experience feront toujours la difference
--