From: narkewoody@gmail.com
To: crossgcc <crossgcc@sourceware.org>
Subject: cross-ng building trys to copy files to '/' ?
Date: Wed, 08 Jan 2014 14:33:00 -0000 [thread overview]
Message-ID: <20140108143238.GA24260@cp920> (raw)
Hi,
I am building ARM toolchain using cross-ng on my Slackware Linux PC.
I've tried 1.17 and 1.18 - the two most recent release, but met the same
error in building (ct-ng build). It seems, cross-ng was trying to
install some header files into my /usr/include and then failed because
it was not running as root.
Can anyone help me? Below is the output:
...
[ALL ] mv -f /home/woody/work/cross-ng.build/1.17.0/.build/arm-unknown-linux-gnueabi/build/build-libc-startfiles/tls.makeT /home/woody/work/cross-ng.build/1.17.0/.build/arm-unknown-linux-gnueabi/build/build-libc-startfiles/tls.make
[ALL ] make[2]: Leaving directory `/home/woody/work/cross-ng.build/1.17.0/.build/src/glibc-2.9'
[ALL ] make[2]: Entering directory `/home/woody/work/cross-ng.build/1.17.0/.build/src/glibc-2.9'
[ALL ] /home/woody/work/cross-ng.build/1.17.0/.build/tools/bin/install -c -m 644 include/limits.h /usr/include/limits.h
[ALL ] /usr/bin/ginstall: cannot remove '/usr/include/limits.h': Permission denied
[ERROR] make[2]: *** [/usr/include/limits.h] Error 1
[ALL ] make[2]: Leaving directory `/home/woody/work/cross-ng.build/1.17.0/.build/src/glibc-2.9'
[ERROR] make[1]: *** [install-headers] Error 2
[ALL ] make[1]: Leaving directory `/home/woody/work/cross-ng.build/1.17.0/.build/arm-unknown-linux-gnueabi/build/build-libc-startfiles'
[ERROR]
[ERROR] >>
[ERROR] >> Build failed in step 'Installing C library headers & start files'
[ERROR] >> called in step '(top-level)'
[ERROR] >>
[ERROR] >> Error happened in: CT_DoExecLog[scripts/functions@258]
[ERROR] >> called from: do_libc_backend_once[scripts/build/libc/glibc-eglibc.sh-common@384]
...
--
For unsubscribe information see http://sourceware.org/lists.html#faq
next reply other threads:[~2014-01-08 14:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-08 14:33 narkewoody [this message]
2014-01-08 19:01 ` thorsten.johannvorderbrueggen
[not found] ` <CAAsE_uepmdsn1YOux0U9W9D1PKJ6KpVmV4=mSh=+jjmBLY4BJA@mail.gmail.com>
2014-01-09 18:24 ` thorsten.johannvorderbrueggen
2014-01-10 2:42 ` Woody Wu
2014-01-10 8:32 ` Bob Dunlop
2014-01-10 12:41 ` Woody Wu
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=20140108143238.GA24260@cp920 \
--to=narkewoody@gmail.com \
--cc=crossgcc@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).