Your message dated Thu, 08 Dec 2005 06:47:05 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#339859: fixed in gibraltar-bootcd 0.53
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; 19 Nov 2005 11:37:32 +0000
>From [EMAIL PROTECTED] Sat Nov 19 03:37:32 2005
Return-path: <[EMAIL PROTECTED]>
Received: from mail-out.m-online.net ([212.18.0.9])
by spohr.debian.org with esmtp (Exim 4.50)
id 1EdR2B-0002OE-Kq
for [EMAIL PROTECTED]; Sat, 19 Nov 2005 03:37:32 -0800
Received: from mail.m-online.net (svr20.m-online.net [192.168.3.148])
by mail-out.m-online.net (Postfix) with ESMTP id 50E6D705FD;
Sat, 19 Nov 2005 12:35:44 +0100 (CET)
Received: from atari.stigge.org (ppp-82-135-13-99.mnet-online.de [82.135.13.99])
by mail.m-online.net (Postfix) with ESMTP id 58DE0136C86;
Sat, 19 Nov 2005 12:36:20 +0100 (CET)
Received: from [192.168.5.99] (localhost [127.0.0.1])
by atari.stigge.org (Postfix) with ESMTP id 3B2491033FA4E;
Sat, 19 Nov 2005 12:36:26 +0100 (CET)
From: Roland Stigge <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: gibraltar-bootcd: FTBFS: C compiler cannot create executables /
Message-Id: <[EMAIL PROTECTED]>
Date: Sat, 19 Nov 2005 12:36:26 +0100 (CET)
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=-7.5 required=4.0 tests=BAYES_00,HAS_PACKAGE,
RCVD_IN_SORBS autolearn=no version=2.60-bugs.debian.org_2005_01_02
Package: gibraltar-bootcd
Version: 0.52
Severity: serious
Hi,
building the package gibraltar-bootcd in a clean sid build environment
(with pbuilder) on i386 results in:
=========================================================================
[...]
checking for C compiler default output file name... configure: error: C
compiler cannot create executables
[...]
Build BusyBox with Debugging symbols (CONFIG_DEBUG) [N/y/?] (NEW) make[1]:
Leaving directory
`/tmp/buildd/gibraltar-bootcd-0.52/debian/tmp-build/busybox-1.00'
Unable to locale crtbegin.o provided by gccUnable to locale crtbegin.o provided
by gccmake[1]: Entering directory
`/tmp/buildd/gibraltar-bootcd-0.52/debian/tmp-build/busybox-1.00'
gcc -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -o scripts/mkdep
/tmp/buildd/gibraltar-bootcd-0.52/debian/tmp-build/busybox-1.00/scripts/mkdep.c
[...]
install: cannot stat `busybox-1.00/busybox': No such file or directory
# now build the freeramdisk binary
/usr/bin/make freeramdisk
make[1]: Entering directory `/tmp/buildd/gibraltar-bootcd-0.52'
gcc -march=i386 -Os -fomit-frame-pointer -Wall -W -static -o freeramdisk
freeramdisk.c
freeramdisk.c:12: warning: return type defaults to 'int'
freeramdisk.c: In function 'main':
freeramdisk.c:29: warning: implicit declaration of function 'exit'
freeramdisk.c:29: warning: incompatible implicit declaration of built-in
function 'exit'
freeramdisk.c:32: warning: implicit declaration of function 'close'
freeramdisk.c:11: warning: unused parameter 'argc'
freeramdisk.c:33: warning: control reaches end of non-void function
make[1]: Leaving directory `/tmp/buildd/gibraltar-bootcd-0.52'
touch build-stamp
fakeroot debian/rules binary
dh_testdir
dh_testroot
dh_clean -k
dh_installdirs
# installing the files for the mkinitrd-cd binary package
install mkinitrd-cd/linuxrc
/tmp/buildd/gibraltar-bootcd-0.52/debian/mkinitrd-cd/usr/share/mkinitrd-cd/
cp mkinitrd-cd/initrd-common-definitions.sh
/tmp/buildd/gibraltar-bootcd-0.52/debian/mkinitrd-cd/usr/share/mkinitrd-cd/
cp mkinitrd-cd/probe-devs.sh
/tmp/buildd/gibraltar-bootcd-0.52/debian/mkinitrd-cd/usr/share/mkinitrd-cd/
install mkinitrd-cd/chown-wrapper
/tmp/buildd/gibraltar-bootcd-0.52/debian/mkinitrd-cd/usr/share/mkinitrd-cd/
install /tmp/buildd/gibraltar-bootcd-0.52/debian/tmp-build/discover
/tmp/buildd/gibraltar-bootcd-0.52/debian/mkinitrd-cd/usr/lib/mkinitrd-cd/
install: cannot stat
`/tmp/buildd/gibraltar-bootcd-0.52/debian/tmp-build/discover': No such file or
directory
make: *** [install] Error 1
=========================================================================
Thanks for considering.
--
DARTS - Debian Archive Regression Test Suite
http://darts.alioth.debian.org/
---------------------------------------
Received: (at 339859-close) by bugs.debian.org; 8 Dec 2005 14:51:21 +0000
>From [EMAIL PROTECTED] Thu Dec 08 06:51:21 2005
Return-path: <[EMAIL PROTECTED]>
Received: from katie by spohr.debian.org with local (Exim 4.50)
id 1EkN33-0002YS-Ke; Thu, 08 Dec 2005 06:47:05 -0800
From: Rene Mayrhofer <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
X-Katie: $Revision: 1.60 $
Subject: Bug#339859: fixed in gibraltar-bootcd 0.53
Message-Id: <[EMAIL PROTECTED]>
Sender: Archive Administrator <[EMAIL PROTECTED]>
Date: Thu, 08 Dec 2005 06:47:05 -0800
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: gibraltar-bootcd
Source-Version: 0.53
We believe that the bug you reported is fixed in the latest version of
gibraltar-bootcd, which is due to be installed in the Debian FTP archive:
gibraltar-bootcd_0.53.dsc
to pool/main/g/gibraltar-bootcd/gibraltar-bootcd_0.53.dsc
gibraltar-bootcd_0.53.tar.gz
to pool/main/g/gibraltar-bootcd/gibraltar-bootcd_0.53.tar.gz
gibraltar-bootsupport_0.53_i386.deb
to pool/main/g/gibraltar-bootcd/gibraltar-bootsupport_0.53_i386.deb
mkinitrd-cd_0.53_i386.deb
to pool/main/g/gibraltar-bootcd/mkinitrd-cd_0.53_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.
Rene Mayrhofer <[EMAIL PROTECTED]> (supplier of updated gibraltar-bootcd
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: Mon, 05 Dec 2005 23:21:50 +0000
Source: gibraltar-bootcd
Binary: mkinitrd-cd gibraltar-bootsupport
Architecture: source i386
Version: 0.53
Distribution: unstable
Urgency: low
Maintainer: Rene Mayrhofer <[EMAIL PROTECTED]>
Changed-By: Rene Mayrhofer <[EMAIL PROTECTED]>
Description:
gibraltar-bootsupport - Boot support for Gibraltar live CD-ROM
mkinitrd-cd - Creates an initrd image for booting from a live CD-ROM or USB dev
Closes: 339859
Changes:
gibraltar-bootcd (0.53) unstable; urgency=low
.
* Also support squashfs images from USB/CF media in addition to the older
cramfs images. squashfs has a better compression and thus produces smaller
images and does not have the restriction to roughly 256 MB of uncompressed
file system size.
* Support (nearly atomic) update of the USB/CF image with a single reboot
and option for fallback. This should make failed "firmware" upgrades
(nearly) impossible.
* Changed the old serial port speed of 9600 to a more contemporary
38400.
* Change priority from optional to extra to match the override file.
* mkinitrd-cd: Use the word matching option to grep when trying to figure
out if a kernel module should be copied or not. This fixed the useless
copying of some otherwise useless modules (e.g. "st").
* gibraltar-bootsupport: Also deal with interface names ath* in
setup.d/01set-ip-addresses (these are used by the madwifi driver).
* gibraltar-bootsupport: Updated var-defaults.tar.gz again.
* mkinitrd-cd: Rise the RAM disk size in syslinux.cfg from 4096 to 4608 kB
to provide more space for the (now larger) initrd images.
* mkinitrd-cd: Add more aliases to syslinux.cfg for various appliances and
the different stages of failed update attempts.
* gibraltar-bootsupport: Depend on iputils-arping, which is needed for
checking for IP address conflicts upon first bootup.
* gibraltar-bootsupport: Depend on xdelta, which is needed for the patching
scripts.
* Implement beepconsole with the beep utility even if we are not running on
a Linux console (but e.g. over serial). This is necessary for appliances
with serial console to beep during bootup.
* gibraltar-bootsupport: Add new utilities status-led and lan-bypass to
control hardware features of the iBASE FWA7204 appliance. Also include a
binary for checking if it is running on an iBASE appliance: check-ibase.
* gibraltar-bootsupport: Add a new setup.d script for configuring kernel
modules for the iBASE appliance: modules-ibase.
* gibraltar-bootsupport: Use /etc/iftab now for renaming interfaces
instead of /etc/network/interfaces. This avoids problems with interface
order, e.g. when using bridge interfaces.
* mkinitrd-cd: Don't include the discover binary in the "min" initrd images
(intended for 1.44 MB floppies) anymore. It just doesn't fit with newer
kernels.
* mkinitrd-cd: Depend on discover1-data | discover-data now, since the
package has been renamed for unstable.
Closes: #339859: gibraltar-bootcd: FTBFS: C compiler cannot create
executables /
* mkinitrd-cd: Fix the regular expression for extracting the module name
from the file name (and consequently to check if it needs to be copied to
the initrd image). Thanks to Andy Chittenden from BlueArc for finding
that issue.
* mkinitrd-cd: Add the isofs module to IDE_CD_MODS and SCSI_CD_MODS in
probe-devs.sh and cdboot_required_modules in mkinitrd-cd.conf. This makes
booting from CD work when the iso9660 filesystem has been compiled as a
module (like for the default Debian kernels) instead of statically. Again
thanks to Andy Chittenden from BlueArc for pointing that out.
* mkinitrd-cd: Fix the shell globbing to be able to deal with an empty list
of copied modules (e.g. when the kernel has been statically linked with
all required drivers). Thanks to Berk Akinci from Sun for spotting this
problem and suggesting the elegant fix of using "shopt -s nullglob".
* gibraltar-bootcd: Fixed saving the configuration data to the same image
that was used for booting the system. The problem was that, when the media
was already mounted, it did not get remounted even when it was originally
mounted with option "ro". Now, when saving to an already mounted
partition, it is remounted rw before and again ro after saving the
configuration so that this special case will work.
Files:
04652642288d7f03a78a239ec0c16591 615 admin extra gibraltar-bootcd_0.53.dsc
f59716dc162b9d4b911b9da57bf68445 9011234 admin extra
gibraltar-bootcd_0.53.tar.gz
8377da249a10e94894f767b0424c64fa 231642 admin extra mkinitrd-cd_0.53_i386.deb
98f7f997f960322c4e5b427f64bfa83c 89436 admin extra
gibraltar-bootsupport_0.53_i386.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
iD8DBQFDlXeDq7SPDcPCS94RAj4OAJ9BxS+z34Z1s+yONacukGJTxedlVwCfZC/m
0rQZEUlQ3CNDXeeK8LgcBiI=
=G8Dc
-----END PGP SIGNATURE-----
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
