-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi Albin,
Albin Tonnerre wrote:
| tags 482571 patch
| tags 483321 patch
| thanks
|
| Hello,
| I intend to NMU this package as part of the gcc-4.3 release goal.
| Patch fixing the issue attached.
I've contacted upstream author Chris Cannam about this issue, and he
told me that the next release (in a couple of weeks) will fix these
issues (see attached message), so I didn't see the point of applying it
as a Debian-specific patch for such a short time frame, especially
because -- according to my knowledge -- there's no software currently in
Debian that depends on these packages, and they don't have too much use
by themselves.
However, help is always welcome, so feel free to NMU in case you see fit.
I also have to mention that IANADD, so uploading is not just a matter of
a few commands for me.
Regards,
- --
cc
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (Darwin)
iEYEARECAAYFAkhWY7YACgkQGJRwVVqzMkMffwCfSxjH+QNzCKFA4vEj4MFnlN6H
tXUAoKJQM5qSGWIA5RQZZJ0VgX5YeXmL
=oGdg
-----END PGP SIGNATURE-----
--- Begin Message ---
On 26/05/2008, SZÉKELYI Szabolcs <[EMAIL PROTECTED]> wrote:
> Vamp SDK has just completed its way into the Debian unstable repository.
> However, it looks like it has a problem when built on sparc.
>
> You can find an extract of the build log at
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=482571
That report refers to gcc-4.3. The current Vamp plugin SDK release
(1.2) should not build with gcc-4.3 in any architecture, because some
#includes are missing. Previous versions of gcc's supporting
libraries apparently included these headers from other headers, at
variance with the standards, and that has been fixed in 4.3.
This change has been an enormous headache -- it affects a huge amount
of C++ code that mixes the C++ standard library with C library
functions. Very few programmers (myself obviously included)
consistently check that they have the right #includes every time they
add a call to a C library function; they just rely on the compiler to
tell them if they haven't. Every project I actively work on has been
affected, and although I have the necessary fixes, in SVN at least,
for all of them, I haven't always had time to roll out a proper
release yet.
Anyway... the build is fixed in the Vamp plugin SDK SVN repository
(since SVN revision 762) and will be fixed in the next release, which
is not very far away (it will be another bugfix-only, API-compatible
release). I attach below the patch that was necessary to fix this
problem.
Thanks,
Chris
vamp-plugin-sdk-gcc-4.3.diff
Description: Binary data
--- End Message ---
