[kbd] >=kbd-2.0.0 doesn't load keymaps on sparc

[Lars Wendler]

Hello dear list readers,

it seems like >=kbd-2.0.0 fails to load keymaps on my sparc machine
which is a SunFire V240 running Gentoo Linux. Same kbd versions on x86
Gentoo machines are working fine so does kbd-1.15.5 on sparc.

This is what I get with kbd-1.15.5:

# loadkeys -V ; loadkeys -v de-latin1-nodeadkeys | egrep
"^Load|^Changed" loadkeys from kbd 1.15.5
Loading /usr/share/keymaps/i386/qwertz/de-latin1-nodeadkeys.map.gz
Changed 975 keys and 26 strings.
Loaded 0 compose definitions.

As you can see, keys were changed and my keyboard (Sun Type 6 USB) with
german layout has the correct keys assigned.


This is what I get with >=sys-apps/kbd-2.0.0 instead:

# loadkeys -V ; loadkeys -v de-latin1-nodeadkeys | egrep
"^Load|^Changed" loadkeys from kbd 2.0.1
Loading /usr/share/keymaps/i386/qwertz/de-latin1-nodeadkeys.map.gz
switching to de-latin1.map
switching to qwertz-layout
switching to compose
switching to linux-with-alt-and-altgr
switching to linux-keys-bare
switching to euro2.map
switching to compose.latin1

Changed 0 keys and 26 strings
Loaded 158 compose definitions


And still wrong keyboard layout as indicated by the output "Changed 0
keys". (On a sidenote, it seems like loadkeys from >=kbd-2.0.0 prints
verbose messages to stderr and not stdout like kbd-1.15* did.)

I have no idea how to debug this especially since loadkeys doesn't
print any kind of warning or error.

More detailed information about the sparc machine's toolchain etc. can
be obtained from the Gentoo bug I opened at [1] in case that matters.

Please CC me on replies as I am not subscribes to this list.

[1] https://bugs.gentoo.org/508436

Kind regards
-- 
Lars Wendler
Gentoo package maintainer
GPG: 4DD8 C47C CDFA 5295 E1A6 3FC8 F696 74AB 981C A6FC
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: not available
URL: <http://lists.altlinux.org/pipermail/kbd/attachments/20140422/0b9bbba4/attachment.bin>