Subject: Re: converters/libiconv fails to build on Solaris
To: Jeremy C. Reed <firstname.lastname@example.org>
From: Raymond Meyer <email@example.com>
Date: 05/25/2007 16:23:10
On Fri, 25 May 2007 09:57:34 -0500 (CDT)
"Jeremy C. Reed" <firstname.lastname@example.org> wrote:
> On Fri, 25 May 2007, Raymond Meyer wrote:
> > On Fri, 25 May 2007 15:34:04 +0100
> > Raymond Meyer <email@example.com> wrote:
> > > ===> Building for libiconv-1.11
> > > builddir="`pwd`"; cd libcharset && /opt/pkg/bin/bmake all
> > > && /opt/pkg/bin/pax -rw lib/libcharset.la lib/.libs "$builddir/"
> > > && /opt/pkg/bin/pax -rw include/*.h "$builddir/" cd lib
> > > && /opt/pkg/bin/bmake all cd lib && /opt/pkg/bin/bmake all cd srclib
> > > && /opt/pkg/bin/bmake all sh: line 5: cd: srclib: No such file or
> > > directory *** [all] Error code 1
> > > 1 error
> > >
> > > Any ideas?
> > Well it only fails to build with the above error message when I have the
> > following set in my mk.conf:
> > WRAPPER_UPDATE_CACHE=no
> > MAKE_FLAGS+=-j1
> > Can anyone think of why this happens?
> Instead of using MAKE_FLAGS+=-j1 use MAKE_JOBS=1.
I'm building packages on quad CPU Sun machine, I thought setting MAKE_FLAGS was
the only way to start multiple make jobs. The package above was failing to
build, so I set MAKE_FLAGS+=-j1, hoping it would eliminate race conditions, but
it was still failing.
If I set MAKE_JOBS=6, do I need to set WRAPPER_UPDATE_CACHE=no? I remember a
long time ago, without setting this variable packages would fail to build with