From: Mike Westerhof <mike@mwester.net>
To: openembedded-devel@lists.openembedded.org
Subject: sane-backends-1.0.20 failing to build
Date: Wed, 25 Nov 2009 11:12:48 -0600 [thread overview]
Message-ID: <4B0D6590.2040009@mwester.net> (raw)
Something is rather fishy with the sane-backends that was just committed
-- anyone else see failures similar to this? (Looks like the
mkinstalldirs script doesn't take the -g option?)
-Mike (mwester)
Here's the pertinent part of
armv5teb-linux-gnueabi/sane-backends-1.0.20-r0/temp/log.do_install.nnnn:
---------------------------------------------------
for dir in artec_eplus48u gt68xx snapscan epjitsu ; do \
/bin/sh ../mkinstalldirs
/u/slug/slugos/tmp/work/armv5teb-linux-gnueabi/sane-backends-1.0.20-r0/image/usr/sha\
re/sane/${dir} ; \
done
mkdir -p --
/u/slug/slugos/tmp/work/armv5teb-linux-gnueabi/sane-backends-1.0.20-r0/image/usr/share/sane/artec_eplus48u
mkdir -p --
/u/slug/slugos/tmp/work/armv5teb-linux-gnueabi/sane-backends-1.0.20-r0/image/usr/share/sane/gt68xx
mkdir -p --
/u/slug/slugos/tmp/work/armv5teb-linux-gnueabi/sane-backends-1.0.20-r0/image/usr/share/sane/snapscan
mkdir -p --
/u/slug/slugos/tmp/work/armv5teb-linux-gnueabi/sane-backends-1.0.20-r0/image/usr/share/sane/epjitsu
/bin/sh ../mkinstalldirs -m 775 -g uucp
/u/slug/slugos/tmp/work/armv5teb-linux-gnueabi/sane-backends-1.0.20-r0/image/va\
r/lock/sane
Usage: mkinstalldirs [-h] [--help] [--version] [-m MODE] DIR ...
Create each directory DIR (with mode MODE, if specified), including all
leading file name components.
Report bugs to <bug-automake@gnu.org>.
make[4]: *** [install-lockpath] Error 1
next reply other threads:[~2009-11-25 17:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-25 17:12 Mike Westerhof [this message]
2009-11-25 18:18 ` sane-backends-1.0.20 failing to build Koen Kooi
2009-12-06 21:37 ` Mike Westerhof
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4B0D6590.2040009@mwester.net \
--to=mike@mwester.net \
--cc=openembedded-devel@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox