On Fri, May 25, 2012 at 01:20:46PM -0400, Robert Simmons wrote:
> On Fri, May 25, 2012 at 12:56 PM, Wesley Shields wrote:
> > On Fri, May 25, 2012 at 12:21:54PM -0400, Robert Simmons wrote:
> >> On Thu, May 24, 2012 at 8:38 PM, Wesley Shields wrote:
> >> > On Tue, May 22, 2012 at 06:29:20PM -0400
On Fri, May 25, 2012 at 12:56 PM, Wesley Shields wrote:
> On Fri, May 25, 2012 at 12:21:54PM -0400, Robert Simmons wrote:
>> On Thu, May 24, 2012 at 8:38 PM, Wesley Shields wrote:
>> > On Tue, May 22, 2012 at 06:29:20PM -0400, Robert Simmons wrote:
>> >> On Tue, May 22, 2012 at 5:14 PM, Wesley Sh
On Fri, May 25, 2012 at 12:21:54PM -0400, Robert Simmons wrote:
> On Thu, May 24, 2012 at 8:38 PM, Wesley Shields wrote:
> > On Tue, May 22, 2012 at 06:29:20PM -0400, Robert Simmons wrote:
> >> On Tue, May 22, 2012 at 5:14 PM, Wesley Shields wrote:
> >> > On Tue, May 22, 2012 at 03:08:31PM -0400,
On Thu, May 24, 2012 at 8:38 PM, Wesley Shields wrote:
> On Tue, May 22, 2012 at 06:29:20PM -0400, Robert Simmons wrote:
>> On Tue, May 22, 2012 at 5:14 PM, Wesley Shields wrote:
>> > On Tue, May 22, 2012 at 03:08:31PM -0400, Robert Simmons wrote:
>> >> On Tue, May 22, 2012 at 8:57 AM, Wesley Shi
On Tue, May 22, 2012 at 06:29:20PM -0400, Robert Simmons wrote:
> On Tue, May 22, 2012 at 5:14 PM, Wesley Shields wrote:
> > On Tue, May 22, 2012 at 03:08:31PM -0400, Robert Simmons wrote:
> >> On Tue, May 22, 2012 at 8:57 AM, Wesley Shields wrote:
> >> > As the person who committed this update I
On Tue, May 22, 2012 at 5:14 PM, Wesley Shields wrote:
> On Tue, May 22, 2012 at 03:08:31PM -0400, Robert Simmons wrote:
>> On Tue, May 22, 2012 at 8:57 AM, Wesley Shields wrote:
>> > As the person who committed this update I will take responsibility for
>> > seeing this through. Would you mind o
On Tue, May 22, 2012 at 03:08:31PM -0400, Robert Simmons wrote:
> On Tue, May 22, 2012 at 8:57 AM, Wesley Shields wrote:
> > As the person who committed this update I will take responsibility for
> > seeing this through. Would you mind opening a PR with this patch and CC
> > both myself and the ma
On Tue, May 22, 2012 at 8:57 AM, Wesley Shields wrote:
> As the person who committed this update I will take responsibility for
> seeing this through. Would you mind opening a PR with this patch and CC
> both myself and the maintainer so it can be properly tracked. I will
> work with both of you t
On Tue, May 22, 2012 at 12:34:47AM -0400, Robert Simmons wrote:
> On Tue, May 15, 2012 at 12:51 PM, Robert Simmons wrote:
> > On Tue, May 15, 2012 at 5:46 AM, Dewayne Geraghty
> > wrote:
> >> Thanks for the updates Robert.
> >>
> >> I've pursued building heimdal on a custom FreeBSD9-Stable jail b
On Tue, May 15, 2012 at 12:51 PM, Robert Simmons wrote:
> On Tue, May 15, 2012 at 5:46 AM, Dewayne Geraghty
> wrote:
>> Thanks for the updates Robert.
>>
>> I've pursued building heimdal on a custom FreeBSD9-Stable jail built without
>> crypto (openssl, heimdal,...); and forced the selection of b
On Tue, May 15, 2012 at 5:46 AM, Dewayne Geraghty
wrote:
> Thanks for the updates Robert.
>
> I've pursued building heimdal on a custom FreeBSD9-Stable jail built without
> crypto (openssl, heimdal,...); and forced the selection of bdb throughout the
> range 5 to 41 via the following ports.conf se
Thanks for the updates Robert.
I've pursued building heimdal on a custom FreeBSD9-Stable jail built without
crypto (openssl, heimdal,...); and forced the selection of bdb throughout the
range 5 to 41 via the following ports.conf setting
*: WITH_BDB_VER=5
...
*: WITH_BDB_VER=41
Combined with
secu
I've determined
that there are actually two problems: configure finds the version of
BDB that is built into FreeBSD:
checking db.h usability... yes
checking db.h presence... yes
checking for db.h... yes
checking db_185.h usability... yes
checking db_185.h presence... yes
checking for db_185.h... y
On Fri, May 11, 2012 at 1:15 PM, Matthias Andree wrote:
> Am 11.05.2012 04:42, schrieb Robert Simmons:
>
>> And, this is the version of BerkeleyDB that it compiles and installs
>> to satisfy the BDB backend that I enabled during config:
>> db41-4.1.25_4
>
> Try with the newest BDB that builds. Cha
Am 11.05.2012 04:42, schrieb Robert Simmons:
> And, this is the version of BerkeleyDB that it compiles and installs
> to satisfy the BDB backend that I enabled during config:
> db41-4.1.25_4
Try with the newest BDB that builds. Chances are versions 4.4 and beyond
are better-behaved, chances are t
15 matches
Mail list logo