On Fri, 26 Oct 2012 23:07:50 +0100, Richard Purdie wrote:
> As one of the people looking after the Yocto Project (which includes an
> build system targeted at embedded devices), I have to say I see less
> problems with pkg-config than with libtool and I'm once again being
> asked to remove all .l
On Friday 26 October 2012 14:27:32 Bob Friesenhahn wrote:
> On Fri, 26 Oct 2012, Yaroslav Bulatov wrote:
> > Oops my badthat was a bad paste from some auto-generated code.
> >
> > This is basically a modified version of .pc file I get when building
> > zlib. Not sure how useful this is because
On Fri, 2012-10-26 at 13:27 -0500, Bob Friesenhahn wrote:
> On Fri, 26 Oct 2012, Yaroslav Bulatov wrote:
>
> > Oops my badthat was a bad paste from some auto-generated code.
> >
> > This is basically a modified version of .pc file I get when building
> > zlib. Not sure how useful this is becau
On Friday 26 October 2012 16:26:29 Yaroslav Bulatov wrote:
please don't top post
> Sorry for confusing terminology, I actually needed pc file for libltdl
> not libtool The .pc file above seems to have solved my problem
the proposed .pc file is incorrect for libltdl. you need to specify -lltdl i
Sorry for confusing terminology, I actually needed pc file for libltdl
not libtool The .pc file above seems to have solved my problem
For reference, the reason pc file was needed was because the toolchain
I'm using is doing something along these lines for each dependency of
fontforge (one of the d
On Friday 26 October 2012 01:05:10 Yaroslav Bulatov wrote:
> 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.
your package management system sounds broken. providing .pc files f
On Fri, 26 Oct 2012, Yaroslav Bulatov wrote:
Oops my badthat was a bad paste from some auto-generated code.
This is basically a modified version of .pc file I get when building
zlib. Not sure how useful this is because you need to update "prefix"
in this file manually each time you rebuild
Oops my badthat was a bad paste from some auto-generated code.
This is basically a modified version of .pc file I get when building
zlib. Not sure how useful this is because you need to update "prefix"
in this file manually each time you rebuild libtool. Ideally the .pc
file would be generated
On 10/25/2012 11:05 PM, Yaroslav Bulatov wrote:
> 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
> run
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 2
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 fi
11 matches
Mail list logo
