[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: 2.0.1 configure fails on FreeBSD, patch included
From: |
Mark . Burgess |
Subject: |
Re: 2.0.1 configure fails on FreeBSD, patch included |
Date: |
Mon, 22 Apr 2002 20:33:25 +0200 (MET DST) |
But first you need to know where to look for it!! So far
I have seen three or four conventions for placing headers and
libraries.
M
On 22 Apr, Tim Auckland wrote:
> This may be a bit crude, but you could match header with library by
> grep-ing for the version string, eg:
>
> $ egrep -i DB_VERSION_STRING /usr/include/db3/db.h
> #define DB_VERSION_STRING "Sleepycat Software: Berkeley DB 3.2.9:
> (January 24, 2001)"
>
> $ grep 'Sleepycat Software: Berkeley DB 3.2.9: (January 24, 2001)'
> /usr/lib/libdb-3.2.so
> Binary file /usr/lib/libdb-3.2.so matches
>
> Tim
>
>> -----Original Message-----
>> From: address@hidden [mailto:address@hidden
>> Sent: Monday, April 22, 2002 9:27 AM
>> To: Tim Auckland
>> Cc: address@hidden
>> Subject: Re: 2.0.1 configure fails on FreeBSD, patch included
>>
>>
>>
>> The problem is not so much testing for the features as
>> finding the libs which contain them and matching header file
>> with library,
>>
>> Mark
>>
>>
>> On 22 Apr, Tim Auckland wrote:
>> >> >> Anyone volunteering? I've enough other stuff to do...
>> >> >
>> >> > High on my TODO list for this week (No. 2 after
>> something a little
>> >> > more pressing).
>> >> >
>> >> > Mike.
>> >>
>> >> Wonderful, that makes 3 people, I think. But note
>> carefully, that not
>> >> all of the distributed db libraries work, because
>> sleepycat changed
>> >> the API in version 3.x something. That is what makes this all so
>> >> difficult.
>> >
>> > Autoconf can test for most API features directly. If you know what
>> > features you depend on, you should just be able to scan all the
>> > plausible library install locations and pick the first one
>> that works,
>> > and not worry about picking the *best* one.
>> >
>> > Tim
>> >
>> > _______________________________________________
>> > Bug-cfengine mailing list
>> > address@hidden
>> http://mail.gnu.org/mailman/listinfo/bug-> cfengine
>>
>>
>>
>>
>>
>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>> Work: +47 22453272 Email: address@hidden
>> Fax : +47 22453205 WWW : http://www.iu.hio.no/~mark
>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>
>>
>>
>
> _______________________________________________
> Bug-cfengine mailing list
> address@hidden
> http://mail.gnu.org/mailman/listinfo/bug-cfengine
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Work: +47 22453272 Email: address@hidden
Fax : +47 22453205 WWW : http://www.iu.hio.no/~mark
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
- Re: 2.0.1 configure fails on FreeBSD, patch included, (continued)
- Re: 2.0.1 configure fails on FreeBSD, patch included, Mark . Burgess, 2002/04/22
- Re: 2.0.1 configure fails on FreeBSD, patch included, Tim Auckland, 2002/04/22
- Re: 2.0.1 configure fails on FreeBSD, patch included, Mark . Burgess, 2002/04/22
- Re: 2.0.1 configure fails on FreeBSD, patch included, David Masterson, 2002/04/22
- Re: 2.0.1 configure fails on FreeBSD, patch included, Tim Auckland, 2002/04/22
- Re: 2.0.1 configure fails on FreeBSD, patch included, Michael Beattie, 2002/04/22
- Re: 2.0.1 configure fails on FreeBSD, patch included, Michael Beattie, 2002/04/23
- Re: 2.0.1 configure fails on FreeBSD, patch included, Michael Beattie, 2002/04/23
- Re: 2.0.1 configure fails on FreeBSD, patch included, Michael Beattie, 2002/04/23
RE: 2.0.1 configure fails on FreeBSD, patch included, Tim Auckland, 2002/04/22
- Re: 2.0.1 configure fails on FreeBSD, patch included,
Mark . Burgess <=
RE: 2.0.1 configure fails on FreeBSD, patch included, Tim Auckland, 2002/04/22