Hi,
Just to add to what dBera said:
On 12/3/07, Henry S. Thompson <[EMAIL PROTECTED]> wrote:
> produces a segfault with the following trace:
>
> at (wrapper managed-to-native) System.String.InternalAllocateStr
> (int) <0x4>
> at (wrapper managed-to-native) System.String.InternalAllocateSt
> I run on a Fedore 6 box which is managed centrally, i.e. I do not have
> root privileges. I have been able in the past to install beagle (up
> through 0.2.18) by a modest amount of hacking about and installing
> other things as well, including my own mono-1.2.2.1, in my own local
> tree.
>
> But
I have what I'm sure is a minority problem, but would welcome any
suggestions.
I run on a Fedore 6 box which is managed centrally, i.e. I do not have
root privileges. I have been able in the past to install beagle (up
through 0.2.18) by a modest amount of hacking about and installing
other things
Hi,
I'm pleased to announce the release of Beagle 0.3.0. This is a new
major release.
As of this release, libbeagle is distributed as a separate tarball
from Beagle, which makes building of lower-level components which
could depend on libbeagle (like GTK+) easier by removing a circular
dependenc
