No as I said I was using an OS/X build made of the latest CVS, and the
windows Dev Build from the main Gnu site. I can try the attached zip files
and see if there is a difference. If It does fail and you are using latest
snapshots it might indicate something wrong with the builds themselves. I¹ll
[EMAIL PROTECTED] wrote on
09/04/2008 17:45:39:
On 4/9/08 9:40 AM, Massimiliano Maini [EMAIL PROTECTED]
com wrote:
[You have an icon in the toolbar to switch direction, quicker]
Can you tell me if, right after you have launched gnubg (before starting
a session), switching
On 4/10/08 1:30 AM, Massimiliano Maini [EMAIL PROTECTED]
wrote:
Sorry to bother with this agin, but are you using the exes I provided in my
previuos emails ?
http://www.gnubg.org/media/windows/gnubg-0.90-20080408-NOGLADE-exes-WMT.zip
On 4/10/08 2:01 AM, Massimiliano Maini [EMAIL PROTECTED]
wrote:
Michael Petch [EMAIL PROTECTED] wrote on 10/04/2008 09:34:33:
No as I said I was using an OS/X build made of the latest CVS, and
the windows Dev Build from the main Gnu site.
You mean on www.gnubg.org ? I make these
Is it at all possible you have some incorrect DLL on your path somewhere
(Maybe a development one you built up yourself recently?) that is different
than what a normal gnubg install has. Almost beginning to think the issue is
not with your executables but some DLL it is loading (gtk, atk etc).
[EMAIL PROTECTED] wrote on
10/04/2008 10:14:45:
Is it at all possible you have some incorrect DLL on your path
somewhere (Maybe a development one you built up yourself recently?)
that is different than what a normal gnubg install has. Almost
beginning to think the issue is not with your
On 4/10/08 2:22 AM, Massimiliano Maini [EMAIL PROTECTED]
wrote:
I did the same (almost): removed everything previously installed (including
.gnubg dir), installed this (not even my latest exes in the separate zip):
Maybe its opengl/hardware/driver issue??? I mean its about the only thing
left
On 4/10/08 2:32 AM, Michael Petch [EMAIL PROTECTED] wrote:
On 4/10/08 2:22 AM, Massimiliano Maini [EMAIL PROTECTED]
wrote:
I did the same (almost): removed everything previously installed (including
* Massimiliano Maini [EMAIL PROTECTED] [080410 10:15]:
Michael Petch [EMAIL PROTECTED] wrote on 10/04/2008 09:34:33:
No as I said I was using an OS/X build made of the latest CVS, and
the windows Dev Build from the main Gnu site.
You mean on www.gnubg.org ? I make these windows builds
On Wed, Apr 9, 2008 at 11:58 PM, Michael Petch [EMAIL PROTECTED] wrote:
Howdy,
I have put away changes to support OS/X sound with Quicktime (The way it was
previously), and fixed up the multithreaded code to only align the stack on
X86 processors. I am unsure this has to be done on the
On Wed, Apr 9, 2008 at 11:58 PM, Michael Petch [EMAIL PROTECTED] wrote:
Howdy,
I have put away changes to support OS/X sound with Quicktime (The way it was
previously), and fixed up the multithreaded code to only align the stack on
X86 processors. I am unsure this has to be done on the
From: [EMAIL PROTECTED]
The alignment of the stack seems to be something gcc specific. Perhaps
we need/want it on ppc-mac as well? Jon, can we use the aligned gcc
attribute instead like in sse.h:
This was added to get around a bug in gcc that miss-aligns the stack of new
threads. It might
On 4/10/08 4:14 AM, Jonathan Kinsey [EMAIL PROTECTED] wrote:
From: [EMAIL PROTECTED]
The alignment of the stack seems to be something gcc specific. Perhaps
we need/want it on ppc-mac as well? Jon, can we use the aligned gcc
attribute instead like in sse.h:
This was added to get
Most of this was answered in my other email, except a few comments:
On 4/10/08 3:39 AM, Christian Anthon [EMAIL PROTECTED] wrote:
quicktime: thx. I'm considering using libao/audiofile for sound
instead of esd. I suppose that libao will use a quicktime backend by
default and that would work
* Michael Petch [EMAIL PROTECTED] [080410 02:00]:
I'll try it today (with you patches). Thanks for the cookbook.
Ciao
Achim
___
Bug-gnubg mailing list
Bug-gnubg@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-gnubg
On 4/10/08 3:37 AM, Christian Anthon [EMAIL PROTECTED] wrote:
On Wed, Apr 9, 2008 at 11:58 PM, Michael Petch [EMAIL PROTECTED]
wrote:
Howdy,
I have put away changes to support OS/X sound with Quicktime (The way it was
previously), and fixed up the multithreaded code to only align the
On Thu, Apr 10, 2008 at 12:00 PM, Michael Petch [EMAIL PROTECTED] wrote:
Now I'm glad you picked up on the Target. The reality is (in my mind) that
the appropriate check is target, not host. My intent is to properly
create a cross compile environment for OS/X (Since Intel and X86 builds can
On 4/10/08 5:11 AM, Christian Anthon [EMAIL PROTECTED] wrote:
target only applies to things like building cross-compilers where:
build: where you build your compiler
host: where you want to run your newly build compiler
target: what platform you want your newly build compiler to produce
I don't get that because I don't have SSE on PPC. I'll look into it. A
hcommon header file must be defining that symbol twice.
On 4/10/08 7:05 AM, Achim Mueller [EMAIL PROTECTED] wrote:
* Achim Mueller [EMAIL PROTECTED] [080410 11:01]:
* Michael Petch [EMAIL PROTECTED] [080410 02:00]:
I'll
Achim, I have a feeling I know what's happening. My hunch is that the
Quicktime framework for Intel (not PPC) includes mm_malloc.h somewhere
(Probably uses MMX for sound processing) which ends up colliding with the
mm_malloc defined in gnubg's lib directory.
I believe it might be considered a
20 matches
Mail list logo
