Bug#40356: dpkg: prints architecture "alphapca56" on "alpha"
On Tue, Jun 29, 1999 at 11:19:52AM +0200, Falk Hueffner wrote:
> > > % dpkg --print-architecture
> > > dpkg: warning, architecture `alphapca56' not in remapping table
> > > alphapca56
> > >
> > > As root, it normally prints correctly "alpha"; but while building a
> > > package, it outputs the wrong architecture, making the built package
> > > unusable.
> > The problem really doesn't lie in dpkg (it IS, after all, reporting the
> > correct class of alpha), but rather in most configure scripts that are
> > included in the packages.
> The problem IS in dpkg. I know many configure scripts recognize alpha
> as alphaevsomething, but that's another thing. But in my case, dpkg
> itself prints alphapca56. And there is no alphapca56 in the set of
> architectures for debian. If I tried to upload a package, it would be
> rejected. And I would *really* like to upload it.
> It would be probably useful if it did give consistently alphapca56,
> but it sometimes gives plain alpha.
This string is generated from "gcc --print-libgcc-file-name". What does this
return on an alpha? Do you use different compiler?
In general, dpkg's architecture support is evil. Sideremark: Don't use
it for package rules files. Instead, use "dpkg --print-installation-architecture"
and derive the information from there. For cross compilation, we have better
support with dpkg-architecture, which is already policy but not incorporated
in dpkg yet. I will send mylatest patches to the open bug report about it
and hope it is in the next NMU.
dpkg-gencontrol and other tools unfortunately use dpkg --print-architecture.
This is fixed in my dpkg-architecture patch as well.
`Rhubarb is no Egyptian god.' Debian http://www.debian.org finger brinkmd@
Marcus Brinkmann GNU http://www.gnu.org master.debian.org
Marcus.Brinkmann@ruhr-uni-bochum.de for public PGP Key
http://homepage.ruhr-uni-bochum.de/Marcus.Brinkmann/ PGP Key ID 36E7CD09