Re: general problem with pkgsrc on 64bit linux

[russell_mcmanus%yahoo.com@localhost]

Min Sik Kim <minskim%NetBSD.org@localhost> writes:

> > But then the question remains of where it is happening,
> 
> I reported this problem in 2006 (PR 34108).
> 
> See mk/buildlink3/buildlink3.mk:
> 
> BUILDLINK_LIBDIRS.${_pkg_}?=    lib${LIBABISUFFIX}
> .  if !empty(BUILDLINK_DEPMETHOD.${_pkg_}:Mfull)
> BUILDLINK_RPATHDIRS.${_pkg_}?=  ${BUILDLINK_LIBDIRS.${_pkg_}}
> .  else
> BUILDLINK_RPATHDIRS.${_pkg_}?=  # empty
> .  endif
> .endfor
> 
> 
> LIBABISUFFIX is set to 64 in mk/platform/Linux.mk.  So
> BUILDLINK_RPATHDIRS.${_pkg_} has lib64, and later ${BUILDLINK_PREFIX.$
> {_pkg_}}/BUILDLINK_RPATHDIRS.${_pkg_} is added to BUILDLINK_LDFLAGS.
> 
> So the problem occurs when one of the dependencies is a native library
> and it is buildlinked (e.g., zlib on Linux).
> 
> 
> > and how to make it stop happening.
> 
> Sorry, no idea.

I think this calls for someone who understands the guts of pkgsrc
pretty well.

pkgsrc gurus, if you are listening, please help!  This is inhibiting
my use of pkgsrc at work in a big way, and I'd very much appreciate
any assistance you could provide.

Thanks in advance,

-russ