Slackware64 + opencv + PKG_CONFIG_PATH
Hi, I work with opencv, and use Slackware64 -current, but now I get this error: opencv.pc not in PKG_CONFIG_PATH.
It's strange because have always work, I check PKG_CONFIG_PATH and get this: /usr/local/lib64/pkgconfig:/usr/lib64/pkgconfig:/usr/local/lib64/pkgconfig Why /usr/local/lib/pkgconfig desapere? Thank's, sorry my bad english |
Your PKG_CONFIG_PATH env variable is set for a 64-bit environment. /usr/local/lib/pkgconfig is for 32-bit meta-data (*.pc) files.
I don't know whether Slackware64 is multilib or not. Assuming it is, I don't know what the Slackware way for dealing with 32-bit and 64-bit paths is. You could define two env variables PKG_CONFIG_PATH32="/usr/local/lib/pkgconfig:/usr/lib/pkgconfig" and PKG_CONFIG_PATH64="/usr/local/lib64/pkgconfig:/usr/lib64/pkgconfig". When you build 32-bit packages, set PKG_CONFIG_PATH="${PKG_CONFIG_PATH32}". Use PKG_CONFIG_PATH64 when building 64-bit packages. |
Quote:
|
Well, having lib and lib64 would be the *most* FHS compliant. I wonder whether the toolchain is built multilib or if the intention is to install precompiled 32-bit binaries and libraries? I don't know enough about Slackware to know how much of a PITA it would be for pkgtools to accomodate both ABI. I'd guess not real tough since it's (AFAIK) just shell scripts. The PackManUtil (bunch of shell scripts) I use on my multilib CLFS machines handles both ABI.
|
Quote:
Quote:
|
All times are GMT -5. The time now is 07:39 PM. |