I see. I needed it because a package management system was using pkg-config to check if libtool was available, and refusing to proceed because .pc file was missing.
I got around it by supplying my own pc file.it . In case someone else runs into this problem -- here's the file I used # Copyright 2012 Google Inc. All Rights Reserved. # # pkgconfig data file generated by googlify.sh (http://go/googlify). prefix=/usr/local/google/home/yaroslavvb/third_party/15_2/x86_64/libtool exec_prefix=${prefix} libdir=${exec_prefix}/lib includedir=${prefix}/include Name: libtool Description: libtool Version: 2.4 Libs: -L${libdir} Cflags: -I${includedir} On Sat, Oct 20, 2012 at 12:11 PM, Eric Blake <ebl...@redhat.com> wrote: > On 10/20/2012 12:45 AM, Yaroslav Bulatov wrote: >> Hi, I'm trying to build libtool, and the standard procedure does not >> generate any pkg-config files, any idea how to fix it? > > What's there to fix? It is intentional that current libtool doesn't use > pkg-config, and therefore does not produce .pc files. If you think it > should use pkg-config, then please provide patches and rationale for > those patches. > > -- > Eric Blake ebl...@redhat.com +1-919-301-3266 > Libvirt virtualization library http://libvirt.org > _______________________________________________ https://lists.gnu.org/mailman/listinfo/libtool
