On Sat, 6 Aug 2005, Thiemo Seufer wrote:
Bastian Blank wrote:
On Sat, Aug 06, 2005 at 09:32:33AM +0200, Thiemo Seufer wrote:
And the headers package is available for both the debian mips and mipsel
architecture.
It needs different .configs since endianness is a config option on mips.
Ok, so what's the problem then? Different configs mean different flavours.
Flavour name is encoded in the output of uname -r, so the flavour-specific
header file will just have to depend on the correct common subarch header
file. That's the reason for a requirement that flavour names would be
unique. Then we can name the flavour-specific header package
linux-headers-$(version)-$(abiname)-$(flavour)
and uname -r will return $(version)-$(abiname)-$(flavour). This header
package will depend on
linux-headers-$(subarch)-$(version)-$(abiname),
which is the common headers package for this subarch. Is there any case
that is not taken into account by this scheme?
Best regards,
Jurij Smakov [EMAIL PROTECTED]
Key: http://www.wooyd.org/pgpkey/ KeyID: C99E03CC
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
