Bug#361707: [Sven.Panne@BenQ.com: RE: [Openal-devel] [Fwd: Bug#361707: Causes FTBFS with GCC 4.2: '<anonymous>' has incomplete type]]

[Reinhard Tartler]

another posting from Sven. 

Will try to build openal cvs with gcc-4.2 the next days, perhaps I can
spot what gcc-4.2 mocks about.

Gruesse,
	Reinhard

----- Forwarded message from Sven Panne <Sven.Panne at BenQ.com> -----

Envelope-to: siretart at tauware.de
Delivery-date: Wed, 19 Apr 2006 11:38:38 +0200
Subject: RE: [Openal-devel] [Fwd: Bug#361707: Causes FTBFS with GCC 4.2: '<anonymous>' has incomplete type]
Date: Wed, 19 Apr 2006 11:38:36 +0200
From: Sven Panne <Sven.Panne at BenQ.com>
To: Reinhard Tartler <siretart at tauware.de>,
	openal-devel at opensource.creative.com
X-OriginalArrivalTime: 19 Apr 2006 09:38:38.0345 (UTC) FILETIME=[09454790:01C66395]
X-TM-AS-Product-Ver: SMEX-7.0.0.1345-3.52.1006-14394.000
X-TM-AS-Result: No--8.100000-8.000000-31
X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=0.94.4
X-Spam-Level: 
X-Spam-Status: No, score=0.1 required=5.5 tests=FORGED_RCVD_HELO 
	autolearn=disabled version=3.0.3

On second thoughts, I've changed the prototype of alcGetCurrentContext
to use void directly, not ALCvoid. This is consistent with the spec and
more in the spirit of the intended use of ALCvoid/ALvoid: Those types
should only be used via pointer types, meaning "pointer to some data of
statically unknown type". Having a "portable void" alone wouldn't make
much sense.

Nevertheless, I still consider this a bug in the GCC 4.2 snapshot you
are using.

Cheers,
   S.