On Mon, Oct 07, 2019 at 09:09:50PM +0100, Stuart Henderson wrote: > On 2019/10/07 21:37, Christopher Zimmermann wrote: > > 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? > > The same way it will discover /opt/include and /opt/lib on a linux box - > you tell it to look there.
Yes, of course I do. But there are two perspectives here. That of the port's maintainer and that of the upstream mainainer: - What's the preferred way to teach a build system our search paths ? - What's the preferred / most portable way for a piece of software to discover the search paths? Is it pkg-config, $CPATH / $LIBRARY_PATH, autoconf, something else? > > 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. > > Please don't do that on a machine you use to work on ports, seems like quite > a high risk of committing things that won't work on anybody else's machine. Ok. I removed those variables from my profile. Christopher -- http://gmerlin.de OpenPGP: http://gmerlin.de/christopher.pub CB07 DA40 B0B6 571D 35E2 0DEF 87E2 92A7 13E5 DEE1
signature.asc
Description: PGP signature
