Your message dated Wed, 14 Sep 2005 15:17:06 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#328285: fixed in ladspa-sdk 1.1-4
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--------------------------------------
Received: (at submit) by bugs.debian.org; 14 Sep 2005 16:25:26 +0000
>From [EMAIL PROTECTED] Wed Sep 14 09:25:26 2005
Return-path: <[EMAIL PROTECTED]>
Received: from pcp0010373886pcs.howard01.md.comcast.net 
(pcp0010744200pcs.howard01.md.comcast.net) [68.48.97.27] 
        by spohr.debian.org with esmtp (Exim 3.36 1 (Debian))
        id 1EFa4c-0001OU-00; Wed, 14 Sep 2005 09:25:26 -0700
Received: from orthrus ([192.168.0.2])
        by pcp0010744200pcs.howard01.md.comcast.net with esmtp (Exim 3.36 #1 
(Debian))
        id 1EFa5O-0007Ta-00; Wed, 14 Sep 2005 12:26:14 -0400
Received: from furrm by orthrus with local (Exim 3.36 #1 (Debian))
        id 1EFa4V-000463-00; Wed, 14 Sep 2005 12:25:19 -0400
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Mike Furr <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: FTBFS on m68k
X-Mailer: reportbug 3.17
Date: Wed, 14 Sep 2005 12:25:19 -0400
Message-Id: <[EMAIL PROTECTED]>
Sender: Mike Furr <[EMAIL PROTECTED]>
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 
        (1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Level: 
X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE 
        autolearn=no version=2.60-bugs.debian.org_2005_01_02

Package: ladspa-sdk
Version: 1.1-3
Severity: serious

ladspa-sdk FTBFS on m68k due to an ICE[1]:
make[1]: Entering directory `/build/buildd/ladspa-sdk-1.1/src'
cc -I. -O3 -fPIC -o plugins/amp.o -c plugins/amp.c
plugins/amp.c: In function '_init':
plugins/amp.c:314: internal compiler error: Segmentation fault

m68k is known to particularly buggy on high optimization levels.  Many
packages have worked around this bug by using -O2 (the recommended
optimization flag anyway).

Cheers,
-Mike

1 -
http://buildd.debian.org/fetch.php?&pkg=ladspa-sdk&ver=1.1-3&arch=m68k&stamp=1124660092&file=log&as=raw

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

Versions of packages ladspa-sdk depends on:
ii  libc6                         2.3.5-6    GNU C Library: Shared libraries an
ii  libgcc1                       1:4.0.1-6  GCC support library
ii  libstdc++6                    4.0.1-6    The GNU Standard C++ Library v3

ladspa-sdk recommends no packages.

-- no debconf information

---------------------------------------
Received: (at 328285-close) by bugs.debian.org; 14 Sep 2005 22:18:22 +0000
>From [EMAIL PROTECTED] Wed Sep 14 15:18:22 2005
Return-path: <[EMAIL PROTECTED]>
Received: from katie by spohr.debian.org with local (Exim 3.36 1 (Debian))
        id 1EFfYw-0007Jc-00; Wed, 14 Sep 2005 15:17:06 -0700
From: Junichi Uekawa <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
X-Katie: $Revision: 1.56 $
Subject: Bug#328285: fixed in ladspa-sdk 1.1-4
Message-Id: <[EMAIL PROTECTED]>
Sender: Archive Administrator <[EMAIL PROTECTED]>
Date: Wed, 14 Sep 2005 15:17:06 -0700
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 
        (1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Level: 
X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER 
        autolearn=no version=2.60-bugs.debian.org_2005_01_02

Source: ladspa-sdk
Source-Version: 1.1-4

We believe that the bug you reported is fixed in the latest version of
ladspa-sdk, which is due to be installed in the Debian FTP archive:

ladspa-sdk_1.1-4.diff.gz
  to pool/main/l/ladspa-sdk/ladspa-sdk_1.1-4.diff.gz
ladspa-sdk_1.1-4.dsc
  to pool/main/l/ladspa-sdk/ladspa-sdk_1.1-4.dsc
ladspa-sdk_1.1-4_i386.deb
  to pool/main/l/ladspa-sdk/ladspa-sdk_1.1-4_i386.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Junichi Uekawa <[EMAIL PROTECTED]> (supplier of updated ladspa-sdk package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.7
Date: Thu, 15 Sep 2005 06:58:48 +0900
Source: ladspa-sdk
Binary: ladspa-sdk
Architecture: source i386
Version: 1.1-4
Distribution: unstable
Urgency: low
Maintainer: Junichi Uekawa <[EMAIL PROTECTED]>
Changed-By: Junichi Uekawa <[EMAIL PROTECTED]>
Description: 
 ladspa-sdk - sample tools for linux-audio-dev plugin architecture
Closes: 328285
Changes: 
 ladspa-sdk (1.1-4) unstable; urgency=low
 .
   * m68k ICE workaround; reduce optimization to -O2 from -O3
     02_m68k_workaround.dpatch (closes: #328285)
Files: 
 ad28a7e7b8ac206512ef1ec1d55b27f4 593 sound optional ladspa-sdk_1.1-4.dsc
 cf50ff13dbe8f6d20a2d1530369b0485 4594 sound optional ladspa-sdk_1.1-4.diff.gz
 2f6d1b11cfb0c59e9aef2996afb7c4e8 39624 sound optional ladspa-sdk_1.1-4_i386.deb

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

iD8DBQFDKJ7a2Dd9TugeVcERArbWAJ4jIVZFaIRN/cvCarr/2WAlvxjBKgCeLD5a
wP1FlDDx2PZFUy5fKX4V1r0=
=DL8h
-----END PGP SIGNATURE-----


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to