Hello Martin,
I got this response from Upstream. I haven't look more deeply into the
problem, but on the one side, in the bug you claim the bug was in the
package, but upstream claims the bug is in gcc-4.2. Can you comment on
that? TIA!
Gruesse,
Reinhard
----- Forwarded message from Sven Panne <[EMAIL PROTECTED]> -----
Envelope-to: [EMAIL PROTECTED]
Delivery-date: Tue, 18 Apr 2006 15:58:11 +0200
Subject: RE: [Openal-devel] [Fwd: Bug#361707: Causes FTBFS with GCC 4.2:
'<anonymous>' has incomplete type]
Date: Tue, 18 Apr 2006 15:58:09 +0200
From: Sven Panne <[EMAIL PROTECTED]>
To: Reinhard Tartler <[EMAIL PROTECTED]>,
[EMAIL PROTECTED]
X-OriginalArrivalTime: 18 Apr 2006 13:58:11.0500 (UTC)
FILETIME=[212E66C0:01C662F0]
X-TM-AS-Product-Ver: SMEX-7.0.0.1345-3.52.1006-14392.000
X-TM-AS-Result: No--5.800000-8.000000-4
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
Well, AFAIK GCC 4.2 has not been released yet, so this can only be some
intermediate (buggy) version used in Debian. The CVS HEAD of the
"portable" OpenAL implementation and ALUT both work with GCC 3.3.5,
4.0.3 and 4.1.0 plus various VisualStudio versions, so I don't see any
need for action here. Looking at the offending lines in <AL/alc.h>, it
looks like the GCC 4.2 snapshot used in Debian has some problems with
stuff like:
typedef void ALCvoid;
extern int foo(ALCvoid);
Regarding release dates: A new freealut version could be released quite
soon (no major visible changes apart from 2 added API entry points), but
I'm not so sure about the "portable" module itself. When somebody
finally finds a real fix for the current problem caused by multiple
alutInit/alutExit calls, a new release could be made quickly, too, I
think.
Cheers,
S.
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf
> Of Reinhard Tartler
> Sent: Freitag, 14. April 2006 23:15
> To: [EMAIL PROTECTED]
> Subject: [Openal-devel] [Fwd: Bug#361707: Causes FTBFS with
> GCC 4.2: '<anonymous>' has incomplete type]
>
> A heads up: openal 0.0.8 doesn not build with GCC 4.2.
> Perhaps you could take a look into this before releasing the
> next version?
>
> btw, do you have an estimation for the next release of
> openal/freealut?
----- End forwarded message -----
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
