Re: Bug#55274: svgalib: can't build from source

[Andy Mortimer <andy.mortimer@zetnet.co.uk>]

[ resend; sorry John if you get it twice! ;-]

Hi,

I think I've found the problem, or at least a possible cause.  The
following is the crucial paragraph:

Andy Mortimer <andy.mortimer@zetnet.co.uk> writes:
> For information, the note from the readme about the alpha.  Perhaps I
> should just set it to ARch:i386 for now ... comments, anyone?
[...]
>    If you compile it on a machine where __alpha__ is defined, you should
>    have configured your kernel correctly once. This is due to the fact
>    that he saw no other possibility to determine the type of ALPHA AXP
>    hardware you use. During kernel configuration your are asked which
>    architecture you want to compile it for.
> 
>    Also important: you must have the right libc compiled for your board
>    hardware. This is due to the I/O functions in libc. They need to be
>    compiled especially for your Alpha board. Have a look at
>    ftp.azstarnet.com for precompiled libc's (although this is not very
>    reliable, most of the libc-packages are sources).

It seems that the build machine doesn't have the headers from a
correctly configured kernel installed in /usr/include.  (I tested on
lully).  faure has even less than this, so far as I can see ...

svgalib expects one of the three
CONFIG_ALPHA_{JENSEN,NONAME,CABRIOLET} to be defined in
linux/autoconf.h in order to work properly.  This doesn't seem to be
the case.

In the light of the last paragraph, it seems that libc may need one of 
these as well; I therefore copy this to the glibc maintainer to ask
how glibc handles this sort of dependency.

Comments, anyone? ;-)

Andy

-- 
Andy Mortimer                                 andy.mortimer@zetnet.co.uk
-- 
Andy walking, Andy tired,
Andy take a little snooze
    -- "Andy Warhol," David Bowie