[Pkg-alsa-devel] Bug#591481: Bug#591481: Bug#591481: libasound2-dev: /usr/include/alsa/global.h:137: error: redefinition of ???struct timeval???

[John Simpson]

On Tue, Aug 3, 2010 at 3:52 PM, Elimar Riesebieter <riesebie at lxtec.de> wrote:
> * John Simpson [100803 14:57 -0500]:
>> On Tue, Aug 3, 2010 at 12:18 PM, Elimar Riesebieter <riesebie at lxtec.de> wrote:
>> > * John Lindgren [100803 09:22 -0400]:
>> >> Package: libasound2-dev
>> >> Version: 1.0.23-1
>> >> Severity: normal
>> >>
>> >> With -std=c99 and -D_BSD_SOURCE, there is a conflict between time.h and
>> >> alsa/global.h.
>> >>
>> >> #include <time.h>
>> >> #include <alsa/asoundlib.h>
>> >>
>> >> $ gcc -c -std=c99 -D_BSD_SOURCE -Wall test.c
>> >> In file included from /usr/include/alsa/asoundlib.h:44,
>> >>                  from test.c:2:
>> >> /usr/include/alsa/global.h:137: error: redefinition of ???struct timeval???
>> >> /usr/include/alsa/global.h:142: error: redefinition of ???struct timespec???
>> >
>> > So what do you expect Debian Alsa maintainers can do at this point?
>>
>> What is it exactly that the "Debian Alsa maintainers" do?
>
> Maintaining the Debian ALSA packages
>
>> Where should Debian Alsa bugs be reported?
>
> If the bug is Debian ALSA packages related to the Debian BTS
>
>> If a developer trying to use the Debian Alsa Package should not
>> discuss bugs on the pkg-alsa-dev mailing list, where should that
>> developer discuss them?
>
> The Debian ALSA packages are based on the raw ALSA sources. The
> packages are prepared to build on the (maeanwhile 12 or so) suported
> archs. So if one wants to change the build environment and found a
> bug this is really _not_ Debian related. If we can point out this we
> recommend to file the _non_ Debian related bug to upstream. Those
> bugs are not distribution related and should be (if any) fixed
> upstream. This is users fault, though.
>
>>
>> I am sure I missed something somewhere.
>
> Of course yes ;-)
>
> Elimar
>
> --
>  The path to source is always uphill!
>                                -unknown-

I finally found this (in the .diff file that "apt-get source
libasound2-dev" retrieves):
--- alsa-lib-1.0.14sa.orig/debian/copyright
+++ alsa-lib-1.0.14sa/debian/copyright
@@ -0,0 +1,35 @@
+This package was debianized by Wichert Akkerman 7 Jun 1998.
+Masato Taruishi took over on 17 Oct 1999.
+Since September 2002 it has been maintained by the participants in
+the pkg-alsa project at alioth.debian.org.
+
+Bugs in the source code (as opposed to bugs in the packaging) are best
+reported to the upstream bug tracking system:
+
+  https://bugtrack.alsa-project.org/alsa-bug
+
+The source code was downloaded from the ALSA homepage:
+
+  http://alsa.sourceforge.net
+
+alsa-lib
+--------


Perhaps that information could be placed here ->
http://lists.alioth.debian.org/mailman/admin/pkg-alsa-devel/?VARHELP=general/info
and here ->
http://lists.alioth.debian.org/mailman/admin/pkg-alsa-devel/?VARHELP=general/welcome_msg
as documented at
http://staff.imsa.edu/~ckolar/mailman/mailman-administration-v2.html

That way, when end-users (PEOPLE who "just want this thing to work")
get as far as seeing this:

   [1|user at Nokia-N810-43-7|~]cat alsa-lib_1.0.14sa-2maemo2.dsc
   Format: 1.0
   Source: alsa-lib
   Version: 1.0.14sa-2maemo2
   Binary: lib32asound2-dev, lib64asound2, lib32asound2,
libasound2-dev, libasound2, libasound2-doc, libasound2-dbg,
lib64asound2-dev
   Maintainer: Debian ALSA Maintainers <pkg-alsa-devel at lists.alioth.debian.org>

... and go to that list to get help from the exspurts, they can be
redirected to the appropriate forum.

THAT is "what" I "expect Debian Alsa maintainers can do at this point?" !

just my halfpence