[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#328604: marked as done (make sets MACHINE_ARCH=i486 (should be i386))



Your message dated Fri, 16 Sep 2005 19:47:17 -0700
with message-id <E1EGSjV-0000Dd-00@spohr.debian.org>
and subject line Bug#328604: fixed in freebsd5-buildutils 5.4-3
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; 16 Sep 2005 10:44:38 +0000
>From rmh@aybabtu.com Fri Sep 16 03:44:38 2005
Return-path: <rmh@aybabtu.com>
Received: from 216.red-62-57-140.user.auna.net (khazad.dyndns.org) [62.57.140.216] 
	by spohr.debian.org with esmtp (Exim 3.36 1 (Debian))
	id 1EGDht-0007z2-00; Fri, 16 Sep 2005 03:44:38 -0700
Received: from rmh by khazad.dyndns.org with local (Exim 4.52)
	id 1EGFZ4-0001Nx-0L; Fri, 16 Sep 2005 14:43:38 +0200
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Robert Millan <rmh@aybabtu.com>
To: Debian Bug Tracking System <submit@bugs.debian.org>
Subject: make sets MACHINE_ARCH=i486 (should be i386)
X-Mailer: reportbug 3.17
Date: Fri, 16 Sep 2005 14:43:37 +0200
Message-Id: <[🔎] E1EGFZ4-0001Nx-0L@khazad.dyndns.org>
Delivered-To: submit@bugs.debian.org
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: freebsd5-buildutils
Version: 5.4-2
Severity: important

freebsd-make sets MACHINE_ARCH variable to i486, but FreeBSD sources expect it
to be usable to the sys/${cpu} directories in kernel source.

This is set via dpkg-architecture in debian/rules (in CFLAGS).  I suggest
obtaining the cpu name in the same way that the kfreebsd package does.

-- System Information:
Debian Release: testing/unstable
Architecture: kfreebsd-i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: GNU/kFreeBSD 5.3-1
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set to C)

Versions of packages freebsd5-buildutils depends on:
ii  bsdmainutils               6.1.2         collection of more utilities from 
ii  dash                       0.5.2-7       The Debian Almquist Shell
ii  libc0.1                    2.3-1+kbsd.11 GNU C Library: Shared libraries an
ii  patchutils                 0.2.31-1      Utilities to work with patches
ii  unzip                      5.52-3        De-archiver for .zip files

freebsd5-buildutils recommends no packages.

-- no debconf information

---------------------------------------
Received: (at 328604-close) by bugs.debian.org; 17 Sep 2005 02:50:36 +0000
>From katie@spohr.debian.org Fri Sep 16 19:50:36 2005
Return-path: <katie@spohr.debian.org>
Received: from katie by spohr.debian.org with local (Exim 3.36 1 (Debian))
	id 1EGSjV-0000Dd-00; Fri, 16 Sep 2005 19:47:17 -0700
From: Aurelien Jarno <aurel32@debian.org>
To: 328604-close@bugs.debian.org
X-Katie: $Revision: 1.56 $
Subject: Bug#328604: fixed in freebsd5-buildutils 5.4-3
Message-Id: <E1EGSjV-0000Dd-00@spohr.debian.org>
Sender: Archive Administrator <katie@spohr.debian.org>
Date: Fri, 16 Sep 2005 19:47:17 -0700
Delivered-To: 328604-close@bugs.debian.org
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=-4.8 required=4.0 tests=BAYES_00,FROM_ENDS_IN_NUMS,
	HAS_BUG_NUMBER autolearn=no version=2.60-bugs.debian.org_2005_01_02

Source: freebsd5-buildutils
Source-Version: 5.4-3

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

freebsd5-buildutils_5.4-3.diff.gz
  to pool/main/f/freebsd5-buildutils/freebsd5-buildutils_5.4-3.diff.gz
freebsd5-buildutils_5.4-3.dsc
  to pool/main/f/freebsd5-buildutils/freebsd5-buildutils_5.4-3.dsc
freebsd5-buildutils_5.4-3_i386.deb
  to pool/main/f/freebsd5-buildutils/freebsd5-buildutils_5.4-3_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 328604@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Aurelien Jarno <aurel32@debian.org> (supplier of updated freebsd5-buildutils 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 ftpmaster@debian.org)


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

Format: 1.7
Date: Sat, 17 Sep 2005 04:36:26 +0200
Source: freebsd5-buildutils
Binary: freebsd5-buildutils
Architecture: source i386
Version: 5.4-3
Distribution: unstable
Urgency: low
Maintainer: GNU/kFreeBSD Maintainers <debian-bsd@lists.debian.org>
Changed-By: Aurelien Jarno <aurel32@debian.org>
Description: 
 freebsd5-buildutils - Utilities for building FreeBSD 5.x sources
Closes: 328604
Changes: 
 freebsd5-buildutils (5.4-3) unstable; urgency=low
 .
   * Fixed the MACHINE_ARCH variable on i386 (closes: bug#328604).
Files: 
 3b990a0d98e0a187c1e72ad65c3cd8e4 752 devel extra freebsd5-buildutils_5.4-3.dsc
 68de33598c81f858db523a407640a4c4 35958 devel extra freebsd5-buildutils_5.4-3.diff.gz
 48750f4758df88183391a1ef409fe2d8 356436 devel extra freebsd5-buildutils_5.4-3_i386.deb

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

iD8DBQFDK4Few3ao2vG823MRAiStAJ9MzTa6SaH7vgBlFJFgWmz7NXhhMwCfXMGI
Jsg1dpv/7vbJ/bGRYkILIdc=
=y93h
-----END PGP SIGNATURE-----



Reply to: