On 2008-01-03 19:21 -0500, Philip Schuchardt wrote:
[down with top-posters]
> Okay, so I just built the development version, usually the most stable
> (ironic).
>
> I get the same hash table warning issues.
>
> Loch does work and doesn't segfault on my machine. Did you rebuild
> your lox
On Thu, Jan 03, 2008 at 11:14:45PM +, Wookey wrote:
> All these appear to be in wx headers, so maybe they are not really
> anything to do with therion, and all I should do is add
> -fno-strict-aliasing to the build to stop them appearing.
That's probably the simplest fix.
> But I'd like
On 2008-01-03 13:13 -0500, Philip Schuchardt wrote:
> Hmmm, runs on my AMD64 box. I'm also running Gentoo and not Debian,
> but that shouldn't matter.
Which version? Plain 0.5.1 tarball?
If I do
make debian-config; cd loch; make
the resulting loch still segfaults on running.
Wookey
--
Okay, so I just built the development version, usually the most stable
(ironic).
I get the same hash table warning issues.
Loch does work and doesn't segfault on my machine. Did you rebuild
your lox models? There was a binary file bug in lox file that only
effects AMD64 arches.
Philip
On Thu, Jan 03, 2008 at 04:42:27PM +, Wookey wrote:
> I think the reason is that the build uses:
> $(shell wx-config --libs --gl-libs) to list the wx libs so gets all of
> them. I haven't fixed this yet as I'm not sure what the best fix is.
> Should we just list the libs that actually are
Hmmm, runs on my AMD64 box. I'm also running Gentoo and not Debian,
but that shouldn't matter.
Philip Schuchardt
On Jan 3, 2008, at 11:42 AM, Wookey wrote:
> I finally got round to uploading the work I did in January to Debian
> proper. So there is now a current Therion in unstable as well
