Comment # 12
on bug 8494
from Guy Harris
(In reply to comment #11)
> Guy's suggestion re behaviour implemented in r48398, which I think is now
> enough to close this bug.
>
> I don't have the autoconf-fu to implement it taking the version number as an
> argument to --with-libnl, but that's less important I think.
I've checked that in.
On non-Linux platforms, --with-libnl and --without-libnl just produces a
warning that it's irrelevant; configuration continues, ignoring the flag.
On Linux:
if no option is supplied, it finds the newest version of libnl it can (3,
then 2, then 1), builds with that if found, builds without libnl if it didn't
find any version;
if --with-libnl is supplied, it finds the newest version of libnl it can
(3, then 2, then 1), builds with that if found, and fails if it didn't find any
version;
if --with-libnl=VERSION is supplied, it tries to find the specified version
(VERSION is 1, 2, or 3), builds with that if found, and fails if it didn't find
that version;
if --without-libnl is supplied, it doesn't bother trying to find libnl, and
builds without it.
You are receiving this mail because:
- You are watching all bug changes.