libaudiofile-dev: not compiled for current gcc

[Debian Bug Importer]

Automatically imported from Debian bug report #327104 http://bugs.debian.org/327104

[Debian Bug Importer (debzilla)]

Automatically imported from Debian bug report #327104 http://bugs.debian.org/327104

[Debian Bug Importer (debzilla)]

Message-Id: <email address hidden>
Date: Wed, 07 Sep 2005 12:50:23 -0400
From: John Covici <email address hidden>
To: Debian Bug Tracking System <email address hidden>
Subject: libaudiofile-dev: not compiled for current gcc

Package: libaudiofile-dev
Version: 0.2.6-6
Severity: grave
Justification: renders package unusable

This package oes back to March and looks like it was compiled under Gcc 3 -- but it is useless under current Sid. Could you recompile and release?

Thanks.

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'stable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.13
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages libaudiofile-dev depends on:
ii libaudiofile0 0.2.6-6 Open-source version of SGI's audio
ii libc6-dev 2.3.5-6 GNU C Library: Development Librari

libaudiofile-dev recommends no packages.

-- no debconf information

[Steve Langasek (vorlon)]

On Wed, Sep 07, 2005 at 12:50:23PM -0400, John Covici wrote:
> Package: libaudiofile-dev
> Version: 0.2.6-6
> Severity: grave
> Justification: renders package unusable

> This package oes back to March and looks like it was compiled under
> Gcc 3 -- but it is useless under current Sid. Could you recompile and
> release?

What is that supposed to mean? There's no reason for a package built
with gcc 3 to be unusable, and you failed to include a description of
any problems you're experiencing.

--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
<email address hidden> http://www.debian.org/

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Wed, 7 Sep 2005 15:31:11 -0700
From: Steve Langasek <email address hidden>
To: John Covici <email address hidden>, <email address hidden>
Subject: Re: Bug#327104: libaudiofile-dev: not compiled for current gcc

--C1iGAkRnbeBonpVg
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Wed, Sep 07, 2005 at 12:50:23PM -0400, John Covici wrote:
> Package: libaudiofile-dev
> Version: 0.2.6-6
> Severity: grave
> Justification: renders package unusable

> This package oes back to March and looks like it was compiled under=20
> Gcc 3 -- but it is useless under current Sid. Could you recompile and=20
> release?

What is that supposed to mean? There's no reason for a package built
with gcc 3 to be unusable, and you failed to include a description of
any problems you're experiencing.

--=20
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
<email address hidden> http://www.debian.org/

--C1iGAkRnbeBonpVg
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFDH2ovKN6ufymYLloRAlZiAKCpVYyQm4GZxfy09oaB0QQggYO8fACgqoYs
WRISA1c3Ld7dm2tWgE/pyn8=
=D67l
-----END PGP SIGNATURE-----

--C1iGAkRnbeBonpVg--

[Matthias Klose (doko)]

package builds fine.

[Steve Langasek (vorlon)]

On Thu, Sep 08, 2005 at 02:36:02AM -0400, John covici wrote:
> on Wednesday 09/07/2005 Steve Langasek(<email address hidden>) wrote
> > On Wed, Sep 07, 2005 at 07:36:13PM -0400, John covici wrote:
> > > I have a program which uses libaudiofile and since the last upgrade

> > Since the last upgrade of what, exactly?

> > > it is giving very strange results and I do know that sometimes a
> > > different compiler does make a difference -- particularly in those
> > > static libraries -- is this incorrect?

> > The C ABI for Linux has not changed since the switch to ELF a decade
> > ago. If this were a C++ library, then applications built with g++ 4.0
> > would fail to *link* against a version of the library built with g++ 3,
> > but that's not the case here. Any problems specific to static libs
> > would almost certainly be caused by ABI changes within glibc (NSS
> > modules), which are unrelated to the compiler version.

> > So, what do you mean by "strange results"?

> OK, what confused me was that the shared modules -- it seems were
> rebuilt as of August 31, but not the static libs and I thought that
> this would cause a problem -- so I may have to check elsewhere for my
> answer.

Ok. Since I can't see how anything you've described represents a
libaudiofile-dev bug at this point, I'm going to go ahead and close this
bug report; please feel free to reopen it if you find other evidence
pointing to a bug in the package.

Cheers,
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
<email address hidden> http://www.debian.org/

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Thu, 8 Sep 2005 02:50:11 -0700
From: Steve Langasek <email address hidden>
To: John covici <email address hidden>, <email address hidden>
Subject: Re: Bug#327104: libaudiofile-dev: not compiled for current gcc

--7JfCtLOvnd9MIVvH
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Thu, Sep 08, 2005 at 02:36:02AM -0400, John covici wrote:
> on Wednesday 09/07/2005 Steve Langasek(<email address hidden>) wrote
> > On Wed, Sep 07, 2005 at 07:36:13PM -0400, John covici wrote:
> > > I have a program which uses libaudiofile and since the last upgrade

> > Since the last upgrade of what, exactly?

> > > it is giving very strange results and I do know that sometimes a
> > > different compiler does make a difference -- particularly in those
> > > static libraries -- is this incorrect?

> > The C ABI for Linux has not changed since the switch to ELF a decade
> > ago. If this were a C++ library, then applications built with g++ 4.0
> > would fail to *link* against a version of the library built with g++ 3,
> > but that's not the case here. Any problems specific to static libs
> > would almost certainly be caused by ABI changes within glibc (NSS
> > modules), which are unrelated to the compiler version.

> > So, what do you mean by "strange results"?

> OK, what confused me was that the shared modules -- it seems were
> rebuilt as of August 31, but not the static libs and I thought that
> this would cause a problem -- so I may have to check elsewhere for my
> answer.

Ok. Since I can't see how anything you've described represents a
libaudiofile-dev bug at this point, I'm going to go ahead and close this
bug report; please feel free to reopen it if you find other evidence
pointing to a bug in the package.

Cheers,
--=20
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
<email address hidden> http://www.debian.org/

--7JfCtLOvnd9MIVvH
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFDIAlTKN6ufymYLloRAmGLAKCPzXGQfH3NFEMe++E4L44iz8eTfACgqZRC
ZWPLoQHaPqlO9jvv1G3jLX4=
=OFXh
-----END PGP SIGNATURE-----

--7JfCtLOvnd9MIVvH--