From mboxrd@z Thu Jan  1 00:00:00 1970
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Problem building a version update of rng-tools
Date: Wed, 03 May 2023 13:07:44 +0100
Message-ID: <E2756128-8CB0-40F3-8FA3-CC5F2608160C@ipfire.org>
In-Reply-To: <00ee5141-f5ec-cefe-79a0-2f4e6d1f2851@ipfire.org>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============6638407170745489614=="
List-Id: <development.lists.ipfire.org>

--===============6638407170745489614==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

Hello Adolf,

Normally you should not need to add anything extra for this to work. The comp=
iler should know where to search for libraries.

If pkg-config is being used, this might be a little bit different.

> On 3 May 2023, at 13:02, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
>=20
> Hi All,
>=20
>=20
> There is a new version for rng-tools so I thought I would do an update but =
it kept stopping saying that it required libcap and could not find it.
>=20
> I noted that the libcap libs are in /lib and not in /usr/lib as the other p=
ackages that rng-tools looks for have their libs. (openssl, libxml2, curl, ja=
nsson)
>=20
> The new version has a flag for the ./configure called libcap_LIBS which can=
 be used to override pkg-config.
>=20
> I tried that in various ways such as libcap_LIBS=3D"/lib" or libcap_LIBS=3D=
"/lib/libcap.so.2.67" and others, but none of them worked. The ./configure st=
ill ended up with the message
>=20
> checking for libcap... no
> configure: error: libcap is required
>=20
> I then noticed that libcap.pc is in /lib/pkgconfig/ while all the other pac=
kages being searched for are in /usr/lib/pkgconfig/

This should indeed be installed to /usr/lib/pkgconfig.

I don=E2=80=99t have a problem with simply changing =E2=80=94-prefix=3D/ to =
=E2=80=94-prefix=3D/usr for libcap, because we don=E2=80=99t support a split =
/usr directory anyways. That should make it easier.

> I then manually did a copy of libcap.pc to /usr/lib/pkgconfig/ and then re =
ran just the rng-tools build and it then successfully found libcap and comple=
ted the build. So the problem is definitely to do withy the unusual location =
for the library files of libcap.

Do we have any other packages that install .pc files into funny places?

> So the question I have is what is the best way to deal with this.
>=20
> Should I add into the libcap lfs a line that copies the libcap.pc to /usr/l=
ib/pkgconfig/ or
>=20
> is can someone tell me what I am doing wrong with the libcap_LIBS flag for =
./configure
>=20
>=20
> Regards,
>=20
> Adolf.
>=20

-Michael

--===============6638407170745489614==--