On 22 Jun 2008, at 20:03, Richard Frith-Macdonald wrote:
On 20 Jun 2008, at 23:50, Gregory John Casamento wrote:
I used SuSE for a while and had a similar issue. I thought that,
by now, SuSE would have resolved it's 64 bit issues, but I see
that's not the case. *sighs*
GNUstep works
Hi,
On Thu, 19 Jun 2008 11:47:02 +0100
Schmielau, Tim [EMAIL PROTECTED] wrote:
| I have two quad core 64 bit Xeon machines with SLES 10 sharing the same home
directory where a fresh GNUstep installation (startup 0.20.0), gcc-4.2.4 and
ffcall libraries reside. On one of the machines, GNUstep
I have two quad core 64 bit Xeon machines with SLES 10 sharing the same home
directory where a fresh GNUstep installation (startup 0.20.0), gcc-4.2.4 and
ffcall libraries reside. On one of the machines, GNUstep runs fine, on the
other one every GNUstep application I've tried so far segfaults.
On 20 Jun 2008, at 23:50, Gregory John Casamento wrote:
I used SuSE for a while and had a similar issue. I thought that, by
now, SuSE would have resolved it's 64 bit issues, but I see that's
not the case. *sighs*
GNUstep works fine on Debian when compiled 64-bit, so this is
definitely
I have two quad core 64 bit Xeon machines with SLES 10 sharing the same home
directory where a fresh GNUstep installation (startup 0.20.0), gcc-4.2.4 and
libffi libraries reside. On one of the machines, GNUstep runs fine, on the
other one every GNUstep application I've tried so far segfaults.
- Original Message
From: Tim Schmielau [EMAIL PROTECTED]
To: gnustep-dev@gnu.org
Sent: Thursday, June 19, 2008 11:28:44 AM
Subject: GNUstep apps segfault on AMD64
I have two quad core 64 bit Xeon machines with SLES 10 sharing the same home
directory where a fresh GNUstep installation (startup
