From: Bob Dunlop <bob.dunlop@xyzzy.org.uk>
To: crossgcc@sourceware.org
Subject: Re: cross-ng building trys to copy files to '/' ?
Date: Fri, 10 Jan 2014 08:32:00 -0000 [thread overview]
Message-ID: <20140110083221.GA30691@xyzzy.org.uk> (raw)
In-Reply-To: <20140109192428.94015be2c64aa5cbb06af3a9@t-online.de>
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:
I'm coming into the conversation late but has anyone tried the obvious.
What is CT_PREFIX_DIR set to ?
This is the target directory for CT and it's parent needs to be writeable
by the building user.
--
Bob Dunlop
--
For unsubscribe information see http://sourceware.org/lists.html#faq
next prev parent reply other threads:[~2014-01-10 8:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-08 14:33 narkewoody
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 [this message]
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=20140110083221.GA30691@xyzzy.org.uk \
--to=bob.dunlop@xyzzy.org.uk \
--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).