On Mon, Oct 07, 2019 at 06:44:01PM +0200, Jeremie Courreges-Anglas wrote:
> After ports lock. I know that at least newer samba versions depend on
> the pkgconfig file to detect LMDB; other ports may do so.
>
> Can you please give a rationale / use case? Are some projects requiring
> this because some Linux distros started to ship a .pc not provided by
> upstream?
>
> Nit below,
>
> > +post-install:
> > + ${SUBST_CMD} -c -m 0444 ${FILESDIR}/lmdb.pc ${PREFIX}/lib/pkgconfig/liblmdb.pc
>
> This ought to use -m ${SHAREMODE}.
done.
On Mon, Oct 07, 2019 at 06:28:19PM +0100, Stuart Henderson wrote:
> On 2019/10/07 18:26, Stuart Henderson wrote:
> > On 2019/10/07 18:06, Christopher Zimmermann wrote:
> > >
> > > Hi,
> > >
> > > can this go in now or should I wait until after ports lock?
> >
> > Definitely wait.
I'll wait.
> seeing as upstream don't build a pc file themselves: what is trying to
> use this?
I am trying to use this to fix this issue:
https://github.com/Drup/ocaml-lmdb/issues/27
It might well be that I'm on the wrong path here. And since this is a
problem I've been wondering about for several years now let me ask more
generically:
How is an arbitrary piece of software supposed to
discover /usr/local/include and /usr/local/lib? I routinely set
CPATH=/usr/local/include:/usr/X11R6/include
LIBRARY_PATH=/usr/local/lib:/usr/X11R6/lib
in my /etc/profile and therefore never hit such issues.
But since this is not the default, how is any piece of software supposed
to discover its search paths?
Christopher
--
http://gmerlin.de
OpenPGP: http://gmerlin.de/christopher.pub
CB07 DA40 B0B6 571D 35E2 0DEF 87E2 92A7 13E5 DEE1
No comments:
Post a Comment