On Fri, Oct 25, 2002 at 10:15:29AM +1000, Drew Parsons wrote:
> On Thu, Oct 24, 2002 at 01:50:29PM -0400, Stephen Gran wrote:
> > Hello all,
> >
> > I am having a problem with one of my packages failing on s390. It
> > builds fine on other architectures (except where I messed up with a bad
> > build-depends on a build-essential). The problem with s390 is here:
> >
> > # Add here commands to configure the package.
> > ./configure --host=s390-linux --build=s390-linux \
> > --prefix=/usr --mandir=\${prefix}/share/man --exec-prefix=/usr\
> >
> > checking host system type... Invalid configuration `s390-linux': machine
> > `s390' not recognized
> >
>
> Why do you have to specify host like that? The whole point of using
> configure is so you don't have to do that, configure determines it
> automatically, not so?
Not when cross-compiling, no. And since it's harmless enough the rest
of the time, debian packages can (and generally should) let
dpkg-architecture decide what to use, not config.guess.
--
.''`. ** Debian GNU/Linux ** | Andrew Suffield
: :' : http://www.debian.org/ | Dept. of Computing,
`. `' | Imperial College,
`- -><- | London, UK
