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

Re: Bug#72349: apt: compile fails



Jason Gunthorpe <jgg@ualberta.ca> writes:

> On Sun, 24 Sep 2000, Goswin Brederlow wrote:
> 
> > Might be a problem with configure on alpha.
> 
> It is.. what does config.guess/config.sub report for your alpha? You need
> to patch them and submit a bug upstream or replace them with newer
> upstream versions.
> 
> Jason

apt seems to be the only one having problems.
The problem seems to be in the configure.in ine 80:

dnl Converts the ARCH to be the same as dpkg
AC_MSG_CHECKING(system architecture)
archset="`awk \"{ if(\\\$1 == \\\"$host_cpu\\\") print \\\$2 }\" $srcdir/buildli
b/archtable`"
if test "x$archset" = "x"; then
  AC_MSG_ERROR(failed: use --host=)
fi
AC_MSG_RESULT($archset)
AC_DEFINE_UNQUOTED(ARCHITECTURE,"$archset")

But buildlib/archtable only contains "alpha   alpha   alpha" and no
subtypes.


So heres some more output:

% ./configure
loading cache ./config.cache
checking host system type... alphaev56-unknown-linux-gnu
checking build system type... alphaev56-unknown-linux-gnu
checking for gcc... gcc
checking whether the C compiler (gcc  ) works... yes
checking whether the C compiler (gcc  ) is a cross-compiler... no
checking whether we are using GNU C... yes
checking whether gcc accepts -g... yes
checking for POSIXized ISC... no
checking host system type... alphaev56-unknown-linux-gnu
checking for c++... c++
checking whether the C++ compiler (c++  ) works... yes
checking whether the C++ compiler (c++  ) is a cross-compiler... no
checking whether we are using GNU C++... yes
checking whether c++ accepts -g... yes
checking how to run the C preprocessor... gcc -E
checking for ranlib... ranlib
checking for ar... ar
checking for library containing gethostbyname... none required
checking for library containing connect... none required
checking system architecture... configure: error: failed: use --host=

% buildlib/config.guess
alphaev56-unknown-linux-gnu

Hope that helps.
                Goswin



Reply to: