From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: OpenEmbedded Development mailing list
<openembedded-devel@lists.openembedded.org>
Subject: failed build, permission denied for glibc_2.9 packaging
Date: Wed, 14 Oct 2009 08:35:26 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.00.0910140835180.28726@localhost> (raw)
as a followup to an earlier post of mine, i'm trying to build a
"base-iamge" of angstrom for my beagleboard from the dev branch, and
the build was making nice progress until:
... snip ...
NOTE: Running task 1719 of 3361 (ID: 210,
/home/rpjday/oe/openembedded/recipes/glibc/glibc_2.9.bb, do_install)
NOTE: Running task 1720 of 3361 (ID: 211,
/home/rpjday/oe/openembedded/recipes/glibc/glibc_2.9.bb,
do_populate_staging)
NOTE: Running task 1721 of 3361 (ID: 214,
/home/rpjday/oe/openembedded/recipes/glibc/glibc_2.9.bb, do_package)
mmap: Permission denied
NOTE: preparing tree for binary locale generation
NOTE: generating locale es_NI (UTF-8)
NOTE: Task failed: localedef returned an error (command was
PATH="/home/rpjday/oe/angstrom-dev/staging/x86_64-linux/usr/bin/armv7a-angstrom-linux-gnueabi:/home/rpjday/oe/angstrom-dev/staging/x86_64-linux/usr/bin/armv7a-angstrom-linux-gnueabi:/home/rpjday/oe/angstrom-dev/staging/x86_64-linux/usr/sbin:/home/rpjday/oe/angstrom-dev/staging/x86_64-linux/usr/bin:/home/rpjday/oe/angstrom-dev/cross/armv7a/bin:/home/rpjday/oe/angstrom-dev/staging/x86_64-linux/sbin:/home/rpjday/oe/angstrom-dev/staging/x86_64-linux/bin:/home/rpjday/oe/openembedded/bitbake/bin:/home/rpjday/nuxeo/dl/nuxeo-dm-5.2.0/bin:/usr/lib64/qt-3.3/bin:/usr/kerberos/bin:/usr/lib64/ccache:/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/sbin:/home/rpjday/bin:/home/rpjday/bitbake-1.8.12/bin:/home/rpjday/eldk/usr/bin"
I18NPATH="/home/rpjday/oe/angstrom-dev/work/armv7a-angstrom-linux-gnueabi/glibc-2.9-r35.2/locale-tree//usr/share/i18n"
qemu-arm -s 1048576 -r 2.6.24 -L
/home/rpjday/oe/angstrom-dev/work/armv7a-angstrom-linux-gnueabi/glibc-2.9-r35.2/locale-tree
-E
LD_LIBRARY_PATH=/home/rpjday/oe/angstrom-dev/work/armv7a-angstrom-linux-gnueabi/glibc-2.9-r35.2/locale-tree/lib
-cpu cortex-a8
/home/rpjday/oe/angstrom-dev/work/armv7a-angstrom-linux-gnueabi/glibc-2.9-r35.2/locale-tree/bin/localedef
--force --old-style --no-archive
--prefix=/home/rpjday/oe/angstrom-dev/work/armv7a-angstrom-linux-gnueabi/glibc-2.9-r35.2/locale-tree
--inputfile=/usr/share/i18n/locales/es_NI --charmap=UTF-8 es_NI).
ERROR: TaskFailed event exception, aborting
ERROR: Build of
/home/rpjday/oe/openembedded/recipes/glibc/glibc_2.9.bb do_package
failed
i'm open to suggestions. did i do something obviously silly?
rday
--
========================================================================
Robert P. J. Day Waterloo, Ontario, CANADA
Linux Consulting, Training and Annoying Kernel Pedantry.
Web page: http://crashcourse.ca
Twitter: http://twitter.com/rpjday
========================================================================
next reply other threads:[~2009-10-14 12:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-14 12:35 Robert P. J. Day [this message]
2009-10-14 12:38 ` failed build, permission denied for glibc_2.9 packaging Robert P. J. Day
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=alpine.LFD.2.00.0910140835180.28726@localhost \
--to=rpjday@crashcourse.ca \
--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