Ondřej Surý wrote:
>
> On Linux, just put the path to /etc/ld.so.conf.d/local.conf and that should
> do the trick.
I'm usually using per-build install paths for experimentation or for easy
rollback, so I prefer not to fiddle with the global path. I make things
difficult for myself :-)
Tony.
--
PGK_CONFIG_PATH="/opt/build/tools/pkg-config"
^^^ there’s a typo and if you need to add paths to more libraries, you need to
use colon, like this:
PKG_CONFIG_PATH=/usr/local/opt/libxml2/lib/pkgconfig:/usr/local/opt/zlib/lib/pkgconfig:
(taken from my work machine with homebrew versions of
OK. Before I did not give you the full picture because I did not want to be to
verbose :-)
It should have been
export SERVERPLUS_DIR="/opt/serverplus”
git clone https://gitlab.isc.org/isc-projects/bind9.git
cd bind9
autoreconf -if
LIBUV_LIBS="-L$SERVERPLUS_DIR/dependencies/libuv/lib"
On 4/28/20 12:21 PM, Ondřej Surý wrote:
> On Linux, just put the path to /etc/ld.so.conf.d/local.conf and that should
> do the trick. I don’t know how to configure the dynamic linker on macOS.
runtime dynamic linked paths, subject to ENV var changes, are, imo, simply a
bad idea/recommendation.
LIBUV_LIBS="-L$/dependencies/libuv/lib“
JFTR this part of the line is wrong as it actually doesn’t contain the library
itself (just LDFLAGS).
You should really use the pkgconfig.
Ondrej
--
Ondřej Surý
ond...@isc.org
> On 28 Apr 2020, at 19:36, Eddy Hahn wrote:
>
>
> On 28 Apr 2020, at 21:15, Tony Finch wrote:
>
> (Building autoconfiscated code to link to libraries installed in /opt or
> ~/lib or wherever has been utterly horrible since the 1990s and libtool
> has made it much slower and harder to debug, so I don't expect it will
> ever work well.)
On
In my experience getting rpaths to work properly is a massive pain because
most autoconf/libtool build systems don't automatically set the rpath as
required for the --with-libwhatever=PATH options to work properly, and
they often prevent attempts to set rpath linker flags. In BIND there has
been a
Hi Eddy,
as I have already told you in the issue you’ve created, there error when
building comes from the configure step. The way you mangle LIBUV_CFLAGS and
LIBUV_LDFLAGS is wrong. You need to set correct PKG_CONFIG_PATH (to patch that
contains libuv.pc), so configure finds libuv.
To fix the
Hi,
I got the latest source and build tools.
1) autorecon -If. WORKED!
2) configure WORKED!
LIBUV_LIBS="-L$/dependencies/libuv/lib"
LIBUV_CFLAGS="-I$/dependencies/libuv/include"
CPPFLAGS=“-I$/dependencies/libuv/include" LDFLAGS='-flat_namespace
-force_flat_namespace' ./configure
9 matches
Mail list logo
