Hi,
On Wed, 22 Jan 2025, at 20:37, Lars Uffmann wrote:
> Damn, now I forgot editing my sender email and exposed my
> for-private-use email. Is there a chance to delete the previous one and
> let me re-send it?
I don't think so, but in any case it wasn't that difficult to guess it, was it?
:)
On 2025-01-22 20:28:38, Andrej Shadura wrote:
It's not *just* a symlink. Pkgconf behaves differently depending on what name
it's called as. Have you actually tried it?
Yes, yes I had - and just did it again:
$ x86_64-linux-gnu-pkgconf --variable pc_path pkgconf
/usr/local/lib/i386-linux-gnu/
Damn, now I forgot editing my sender email and exposed my for-private-use
email. Is there a chance to delete the previous one and let me re-send it?
Hello,
On Wed, 22 Jan 2025, at 20:06, Lars Uffmann wrote:
> On 2025-01-22 19:41:18, Andrej Shadura wrote:
>> So, if you run x86_64-linux-gnu-pkgconf, what do you get?
>
> Well - as I said - it's just a symlink:
> $ ls -l /usr/bin/x86_64-linux-gnu-pkgconf
> lrwxrwxrwx 1 root root 7 Oct 20 20:10 /us
On 2025-01-22 19:41:18, Andrej Shadura wrote:
So, if you run x86_64-linux-gnu-pkgconf, what do you get?
Well - as I said - it's just a symlink:
$ ls -l /usr/bin/x86_64-linux-gnu-pkgconf
lrwxrwxrwx 1 root root 7 Oct 20 20:10 /usr/bin/x86_64-linux-gnu-pkgconf ->
pkgconf
So I get the same output
Hello,
On Wed, 22 Jan 2025, at 17:08, Lars Uffmann wrote:
> I ran into this same issue today, and would like to confirm the bug:
>
> 1) The workaround suggested by Andrej is not functional, because
> x86_64-linux-gnu-pkgconf (or pkg-config) is really just a symlink to
> whatever pkgconf binaries
I ran into this same issue today, and would like to confirm the bug:
1) The workaround suggested by Andrej is not functional, because
x86_64-linux-gnu-pkgconf (or pkg-config) is really just a symlink to whatever
pkgconf binaries are installed on the system.
2) The binary architecture of the pk
On Fri, 6 Jan 2023 20:50:30 -0300 Allan wrote:
When I try to check for a package using pkg-config it is not
able to find the package even that it is properly installed.
Workaround
$ env PKG_CONFIG_PATH="$PKG_CONFIG_PATH:/usr/lib/x86_64-linux-gnu/pkgconfig/"
pkg-config --modversion gthread-2.0
2
Package: pkg-config:amd64
Version: 1.8.0-12
When I try to check for a package using pkg-config it is not
able to find the package even that it is properly installed.
Current output
$ pkg-config --modversion gthread-2.0
Package gthread-2.0 was not found in the pkg-config search path.
Pe
9 matches
Mail list logo
