On Mon, 2005-06-06 at 21:46 -0400, Jan Schaumann wrote:
> Georg Schwarz <georg.schwarz@freenet.de> wrote:
> > > I think I got it.  The problem appears when ABI=64 is in mk.conf.  When
> > > this happens, LIBABISUFFIX is automatically set to 64, and it seems that
> > > buildlink will only allow -L directories that end in that string.
> > > Therefore, it correctly uses /usr/lib64 but traps ${PREFIX}/lib, as it
> > > doesn't have the 64 suffix.
> > > 
> > > If this is the reason... I don't know how to fix it.
> > 
> > one quick and dirty fix might be to set LIBABISUFFIX= in mk.conf (did that
> > on my IRIX 5.3 system where the ABI stuff is partially meaningless anyway).
> > Then of course the /usr/lib64 stuff is no longer added.
> > 
> > mk/bsd.pkg.mk has
> > 
> > CONFIGURE_ARGS+=        --x-libraries=${X11BASE}/lib${LIBABISUFFIX}
> > 
> > mk/bsd.pkg.use.mk has
> > 
> > .if defined(USE_X11)
> > X11_LDFLAGS+=           ${COMPILER_RPATH_FLAG}${X11BASE}/lib${LIBABISUFFIX}
> > X11_LDFLAGS+=           -L${X11BASE}/lib${LIBABISUFFIX}
> > .endif
> > 
> > Here one could add the same thing without ${LIBABISUFFIX} (and if one did
> > it very nicely the above would only be added if ${LIBABISUFFIX} was nonempty)
> > 
> > I do not see at first glance though where X11_LDFLAGS is actually being
> > used later on.
> 
> Actually, I believe this problem in particular is not related to
> X11_LDFLAGS, but rather to BUILDLINK_LIBDIRS.  The attached patch should
> fix the problem Julio reported.

Won't this change make buildlink also use directories such as /usr/lib
while it should be using /usr/lib64?

-- 
Julio M. Merino Vidal <jmmv84@gmail.com>
http://www.livejournal.com/users/jmmv/
The NetBSD Project - http://www.NetBSD.org/