On Sun, Mar 16, 2008 at 11:40:46PM -0400, [EMAIL PROTECTED] wrote: > I did cvs co -rOPENBSD_4_3 src > > built a release and installed it > > I then did cvs co -rOPENBSD_4_3 ports > > ran a bulk build > > tried this on amd64 and i386 > > amd64 completed fine > > i386 - gettext fails because: > > ===> Building package for gettext-0.16.1 > Create /scratch/4.3/packages/i386/all/gettext-0.16.1.tgz > Switching to /usr/ports/devel/gettext/pkg/PFRAG.shared > Error in package: > /usr/ports/devel/gettext/w-gettext-0.16.1/fake-i386//usr/local/lib/libasprintf.so.1.0 > does not exist > Error in package: > /usr/ports/devel/gettext/w-gettext-0.16.1/fake-i386//usr/local/include/autosprintf.h > does not exist > Error in package: > /usr/ports/devel/gettext/w-gettext-0.16.1/fake-i386//usr/local/info/autosprintf.info > does not exist > Error in package: > /usr/ports/devel/gettext/w-gettext-0.16.1/fake-i386//usr/local/lib/libasprintf.a > does not exist > Error in package: > /usr/ports/devel/gettext/w-gettext-0.16.1/fake-i386//usr/local/lib/libasprintf.la > does not exist > Error in package: > /usr/ports/devel/gettext/w-gettext-0.16.1/fake-i386//usr/local/share/doc/libasprintf/autosprintf_all.html > does not exist > > So I installed another i386 box. Same steps, same problem. They share > the distfiles (via NFS) with the amd64 box, so it's the same source, and > the checksums match. But neither i386 box recurses into the libasprintf > directory and builds it, so it's missing at package time. > > I noticed that the i386 packages snapshot has gettext, so I assume this > is some kind of bizarre local problem. > > Has anyone seen something similar to this? Is there something in the > snapshots that isn't in -stable?
It builds fine here @i386, on a one-week old system with devel/gettext from 4_3 tag. And it _does_ recurse in libasprintf directory. Landry
