Re: no .pc file

2012-10-26 Thread Mike Frysinger
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

Re: Libtool is linking the wrong library (location) in and I can't figure out what's causing it.

2012-10-26 Thread Dan Nicholson
On Oct 27, 2012 1:25 AM, "Jim Lynch" wrote: > > I have two fairly identical gnu make/build projects. One of them works fine but the other is looking for the library in the wrong place. The difference I see is that one of them has this: > > ibtool: link: g++ -std=c++0x -g -O2 -o loggerd loggerd-f

Re: no .pc file

2012-10-26 Thread Richard Purdie
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

Re: no .pc file

2012-10-26 Thread Mike Frysinger
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

Re: no .pc file

2012-10-26 Thread Yaroslav Bulatov
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

Re: no .pc file

2012-10-26 Thread Mike Frysinger
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

Re: Building libltdlc.la?

2012-10-26 Thread Yaroslav Bulatov
Thanks, the relevant variable turns out to be AC_LIBLTDL_CONVENIENCE, and the way get libltdlc from regular configure make is the following: ./configure --enable-ltdl-convenience make This complains about "WARNING: unrecognized options: --enable-ltdl-convenience", but it builds libltdlc.la noneth

Re: no .pc file

2012-10-26 Thread Bob Friesenhahn
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

Libtool is linking the wrong library (location) in and I can't figure out what's causing it.

2012-10-26 Thread Jim Lynch
I have two fairly identical gnu make/build projects. One of them works fine but the other is looking for the library in the wrong place. The difference I see is that one of them has this: ibtool: link: g++ -std=c++0x -g -O2 -o loggerd loggerd-fieldlist.o loggerd-t2m.o loggerd-loggercounters.

Re: no .pc file

2012-10-26 Thread Yaroslav Bulatov
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

Re: no .pc file

2012-10-26 Thread Eric Blake
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