On 01/09/2019 10:53, Pierre Labastie via blfs-dev wrote: > On 01/09/2019 10:13, spiky0011 via blfs-dev wrote: >> Building sane backends, the command "chgrp -v scanner /var/lock/sane" >> fails. >> >> chgrp: cannot access '/var/lock/sane': No such file or directory >> >> The user needs adding to "scanner group" and >> >> su $(whoami) run. This was in the older sane commands >> > > Ah, I'm really sorry, I thought there was not error, because for some reason, > even if my scripts have "set -e", this one did not error out for this command. > > Actually, I can't even understand how it is possible that it make a difference > for commands run as root, that the user be added to "sane" group. Will look at > that... > > Ah, upstream test the exit status of the following command in "configure": > chgrp scanner sanetest.file 2>/dev/null > > So the command only succeeds if the user is in the "scanner" group, and fails > silently if not. So my checks of errors did not detect it at this place > either. > But if the command fails, upstream assume the group does not exits! This > roughly means they assume configure should be run as root... > There are other ways to check the existence of a group. > > Anyway, I'll put back the instructions in both trunk and the 9.0 tag. Bad move > from my part, but it's development after all... >
Tentative fix at revisions 22078 (trunk), and 22079 (tags/9.0). I've tested that with those instructions, the /var/lock/sane directory is created, and locking is enabled. Pierre -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
