Re[3]: Finding dependencies in lib64 or lib

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On On Thu, 11 Feb 2010 mpsuzuki wrote:
On Thu, 11 Feb 2010 19:00:12 +0300
Konstantin Andreev <andreev@xxxxxxxxx> wrote:
Unfortunately, pkg-config does not distinct instruction sets (32/64 bit). Sadly, pkg-config authors refuse to support instruction sets.

Could you give me more info about the discussion about this issue with pkg-config author? I could not find such in recent posts in pkg-config mail list archive.

Regards,
mpsuzuki

Certainly. Look into attachments, please.

--
Konstantin Andreev.
--- Begin Message ---
Hi,

  I'd like pkgconfig to transparently find 64bit libs on platforms
where they're available when I build 64bit.  Is this supported in
pkgconfig?  Should the distro provide a /usr/lib64/pkgconfig
directory, containing pc files that point to 64bit libs, or is there a
better way?

Thanks,
Kent

--
Kent Yoder
IBM LTC Security Dev.

--- End Message ---
--- Begin Message ---
* Kent Yoder 

|   I'd like pkgconfig to transparently find 64bit libs on platforms
| where they're available when I build 64bit.  Is this supported in
| pkgconfig?  Should the distro provide a /usr/lib64/pkgconfig
| directory, containing pc files that point to 64bit libs, or is there a
| better way?

No, pkg-config doesn't handle multiple targets yet.  There are a few
proposals about how to handle that, including some patches, but I have
been holding that off until I see something which I am happy with and
which will support any kind of cross-compilation well.

-- 
Tollef Fog Heen                                                        ,''`.
UNIX is user friendly, it's just picky about who its friends are      : :' :
                                                                      `. `' 
                                                                        `-  

--- End Message ---
--- Begin Message ---
I am current working a project to port a package to ppc64. There is an
existing ppc32 port for this package.

The problem I see is that when I run:

	pkg-config --libs glib-2.0 gthread-2.0

I get 

	-pthread -L/opt/gnome/lib -lgthread-2.0 -lglib-2.0

which is wrong for a powerpc64 target. It should be:

	-pthread -L/opt/gnome/lib64 -lgthread-2.0 -lglib-2.0

This is --version 20. Lot of projects use libtool and pkg-config as park
of configure. And many of these projects fail to build for powerpc64. 

64-bit PowerPC is fully biarch and supports 32-bit and 64-bit
applications an libraries equally well. But 32-bit is the default. The
distros build 32- and 64-bit bit versions of most packages so we
normally full set of libraries in &lt;prefix&gt;/lib and &lt;prefix&gt;/lib64.

Is there a way to tell pkg-config to pick the &lt;prefix&gt;/lib64 set and
ignore the &lt;prefix&gt;/lib ?

--- End Message ---
--- Begin Message ---
* Steven Munroe 

| Is there a way to tell pkg-config to pick the <prefix>/lib64 set and
| ignore the <prefix>/lib ?

Have you tried compiling pkg-config with --libdir=/opt/gnome/lib64 ?
I believe that should solve your problem.

-- 
Tollef Fog Heen
UNIX is user friendly, it's just picky about who its friends are


--- End Message ---
_______________________________________________
Autoconf mailing list
Autoconf@xxxxxxx
http://lists.gnu.org/mailman/listinfo/autoconf

[Index of Archives]     [GCC Help]     [Kernel Discussion]     [RPM Discussion]     [Red Hat Development]     [Yosemite News]     [Linux USB]     [Samba]

  Powered by Linux