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

Bug#96436: marked as done (gcc 2.95 package build stomps on dpkg-dev script variables)



Your message dated Sun,  6 May 2001 21:34:46 +0200 (MEST)
with message-id <15093.42664.697421.574138@bolero>
and subject line fixed in gcc-2.95.4-0.010506
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.)

Darren Benham
(administrator, Debian Bugs database)

--------------------------------------
Received: (at submit) by bugs.debian.org; 5 May 2001 18:50:37 +0000
>From gcarper@xrhino.com Sat May 05 13:50:37 2001
Return-path: <gcarper@xrhino.com>
Received: from xrhino.com (eris.xrhino.com) [12.5.16.51] 
	by master.debian.org with esmtp (Exim 3.12 1 (Debian))
	id 14w78X-0002aA-00; Sat, 05 May 2001 13:50:37 -0500
Received: from xrhino.com (gcarper@fishnchips.xrhino.com [192.168.0.2])
	by eris.xrhino.com (8.11.0/8.8.7) with ESMTP id f45InkM06717
	for <submit@bugs.debian.org>; Sat, 5 May 2001 14:49:46 -0400
Message-ID: <3AF44B7B.7040100@xrhino.com>
Date: Sat, 05 May 2001 14:50:35 -0400
From: Gray Carper <gcarper@xrhino.com>
User-Agent: Mozilla/5.0 (X11; U; Linux 2.4.2 i686; en-US; 0.8) Gecko/20010215
X-Accept-Language: en
MIME-Version: 1.0
To: submit@bugs.debian.org
Subject: gcc 2.95 package build stomps on dpkg-dev script variables
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Delivered-To: submit@bugs.debian.org

Package: gcc-2.95
Version: 2.95.4.ds1-0.010424

In truth, this applies to all gcc-2.95 versions.

When building the gcc-2.95 package, four key dpkg-dev
variables are utilized like this (in "rules.defs")...

DEB_HOST_ARCH := $(shell ")
DEB_HOST_GNU_CPU := $(shell dpkg-architecture -qDEB_HOST_GNU_CPU)
DEB_HOST_GNU_SYSTEM := $(shell dpkg-architecture
                        -qDEB_HOST_GNU_SYSTEM)
DEB_HOST_GNU_TYPE := $(shell dpkg-architecture -qDEB_HOST_GNU_TYPE)

On the systems which we attempted the build (all working from the
*unstable* tree, granted), the build process failed first with
the dpkg-gencontrol script (and then later with the dpkg-genchanges
script). The scripts reported, for example, a lack of architecture
(saying that " " was the host architecture).

It turned out that, after the above varibles were set, queries
to those variables through dpkg-architecture returned absolutely
nothing. So, when the dpkg-dev scripts tried to do the queries,
the host architecture (among other variables) was seen as blank.
This caused a build failure every time.

The fix is a small one. We simply needed to change the names of
all instances of those above variables. So, DEB_HOST_ARCH became
DEB_HOST_ARCHI, etc. This fixed the build completely.

Perhaps it would be good to consider varible name changes so
freaky namespace collisions don't occur?

We are using dpkg-dev 1.9.4, debhelper 3.0.18, kernel 2.4.2,
dpkg 1.9.4, libc6 2.2.2-4, and Debian GNU/Linux 2.2r2 (now
working from the unstable tree, though).

C-ya,
Gray
-- 
Gray Carper
Technical Lead
xRhino, a division of ASTi
1700 Kraft Drive, Research Building VII, suite 2413
Blacksburg, Virginia, USA 24060
Telephone: (540) 961-4469
Email    : gcarper@xrhino.com
Web      : http://www.xrhino.com/



---------------------------------------
Received: (at 96436-done) by bugs.debian.org; 6 May 2001 19:38:43 +0000
>From doko@cs.tu-berlin.de Sun May 06 14:38:43 2001
Return-path: <doko@cs.tu-berlin.de>
Received: from mail.cs.tu-berlin.de [130.149.17.13] (root)
	by master.debian.org with esmtp (Exim 3.12 1 (Debian))
	id 14wUMd-0002wJ-00; Sun, 06 May 2001 14:38:43 -0500
Received: from bolero.cs.tu-berlin.de (doko@bolero.cs.tu-berlin.de [130.149.19.1])
	by mail.cs.tu-berlin.de (8.9.3/8.9.3) with ESMTP id VAA19773;
	Sun, 6 May 2001 21:34:46 +0200 (MET DST)
Received: (from doko@localhost)
	by bolero.cs.tu-berlin.de (8.9.3+Sun/8.9.3) id VAA16935;
	Sun, 6 May 2001 21:34:46 +0200 (MEST)
From: Matthias Klose <doko@cs.tu-berlin.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Date: Sun,  6 May 2001 21:34:46 +0200 (MEST)
To: 95955-done@bugs.debian.org, 95978-done@bugs.debian.org,
        95358-done@bugs.debian.org, 95969-done@bugs.debian.org,
        96436-done@bugs.debian.org
Subject: fixed in gcc-2.95.4-0.010506
X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs  Lucid
Message-ID: <15093.42664.697421.574138@bolero>
Delivered-To: 96436-done@bugs.debian.org

gcc-2.95 (2.95.4.ds1-0.010506) unstable; urgency=low

  * Fix build problem. That was a bug in the rules files, exposed
    by dpkg-1.9's changed dpkg-buildpackage script. Thanks to Roderich Schupp.
    Fixes #96436.

gcc-2.95 (2.95.4.ds1-0.010502) unstable; urgency=low

  * Update fsirl patch to 010501 (fixes #95955, #95969, #95978).
    Fixes building of glibc.
  * Apparently we do have a problem with dpkg-dev-1.9, which does
    create control files with missing 'Architecture:' lines. Fixes
    are welcome.
  * debian/gpc-2.95.prerm: Fix typo (#95358).
  * Disable fsirl patch for alpha again.
  * Update date in gcc version string to be able to identify the
    exact Debian version.
  * Now that gcj-3.0 is in the archives, disable building gcj-2.95.



Reply to: