On Wed, Aug 13, 2014 at 01:23:40PM -0500, Bruce Dubbs wrote:
>
> Following the book (jhalfs) I get no errors in the test suite. The 2 tests
> have a lot of sub-tests that are not reported individually, hence the one
> sed:
>
> sed -r -i 's|/usr(/bin/test)|\1|' test/udev-test.pl
>
> because it hard codes the test commnand (not bash builtin) in /usr/bin in
> just one of the sub-tests.
>
I probably won't start another build before 7.6 (if I can get hold
of the replacement drives I want : one of my RAID-1 pair keeps
reporting pending sectors, and I hope to replace both and then
grow the array). So for the moment, I'll just note that I am hopeful
of not getting any errors when I next run the tests in chroot.
For repeating these tests after gudev has been built on my desktop
builds, I'm unsure - they're only tests, I might just drop them like
most of the other testsuites in BLFS ;-)
> As for the 60-keyboard.rules, it says:
>
> SUBSYSTEMS=="usb", IMPORT{builtin}="hwdb --subsystem=usb
> --lookup-prefix=keyboard:", \
> RUN{builtin}+="keyboard", GOTO="keyboard_end"
>
> I believe that the {builtin} construct means that it shouldn't need an
> external program, but it's built into the current code.
>
Agreed - if keymap was NOT disabled. But I did disable it in most
of my builds.
> I have a US standard pc105 keyboard and do not see the error message you but
> that may be specific to certain keyboards and what the
>
> "hwdb --subsystem=usb --lookup-prefix=keyboard:"
>
> portion of the rule does.
>
> -- Bruce
I think you are misreading what I wrote: you compiled eudev
including the keymap, I had not been doing that (standard UK
keyboard - didn't see any need for keymap in earlier versions of
eudev). Now that I am doing that, the error disappears. So, I am
resigned to always building intltool and gperf and following the
book for those.
ĸen
--
Nanny Ogg usually went to bed early. After all, she was an old lady.
Sometimes she went to bed as early as 6 a.m.
--
http://lists.linuxfromscratch.org/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
