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

Re: Bug#40356: dpkg: prints architecture "alphapca56" on "alpha"

On 28 Jun 1999, Falk Hueffner wrote:

> Package: dpkg
> Version:
> Severity: normal
> % 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.

This really should be corrected, BUT it could also be an advantage if
compiling things for a "roll yer own" system (if used properly, it can
allow the programme to take advantage of CPU-specific changes like the
byte load/store instructions on newer Alphas).

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.  I would say that about 75% of the configure
scripts haven't been regenerated from autoconf in a LONG time.  I've made
sure that newer autoconfs recognise many new Alpha types (alphapca56,
alphapca57, alphaev6 to name a few), but the maintainers usually never
regenerate using autoconf.

For a workaround, try adding '--host=alpha-unknown-linux-gnu' or
'--host=alpha-debian-linux-gnu' and it should force configure to use
something that it's aware of.


Reply to: