Bug#96436: gcc 2.95 package build stomps on dpkg-dev script variables
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/
Reply to: