From: Alexey Neyman <stilor@att.net>
To: Josh Branning <lovell.joshyyy@gmail.com>, crossgcc@sourceware.org
Subject: Re: Building rpi armv6 toolchain on macOS
Date: Sun, 12 Mar 2017 01:04:00 -0000 [thread overview]
Message-ID: <46e45cf1-06b7-cf1a-0613-82013de1a289@att.net> (raw)
In-Reply-To: <58C49061.6030807@gmail.com>
On 03/11/2017 04:03 PM, Josh Branning wrote:
> On 11/03/17 21:06, Etan Kissling wrote:
>> Thanks for the quick reply!
>>
>> With the master build, I run into an error quite quickly (following
>> instructions from crosstool-ng.org).
>> [DEBUG] ==> Executing: 'mkdir' '-p' '/build'
>> [ALL ] mkdir: /build: Permission denied
>> - Full log: https://scriptreactor.com/rpi1-master-build.log
>>
>> Any idea what's going on here?
>
> Are you running crosstool-ng as root? And do you have permission to
> write to the / directory? I'm guessing not. (If not, then I suggest
> changing the build directory instead of running as root.)
As the error states, he *is not* running it as root. Moreover, running
as root IS NOT RECOMMENDED - crosstool-ng is quite explicit about it.
The problem is that he took a config from 1.22 and tried to run it on
master without upgrading it through the regular procedure for
kconfig-based system ("oldconfig"). In master, build directory is set
using a value of an auxiliary variable, CT_BUILD_TOP_DIR, that isn't set
in the config unless it is upgraded.
Regards,
Alexey.
next prev parent reply other threads:[~2017-03-12 1:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-09 12:15 Etan Kissling
2017-03-09 18:21 ` Alexey Neyman
2017-03-11 21:06 ` Etan Kissling
2017-03-11 22:40 ` Alexey Neyman
2017-03-12 0:03 ` Josh Branning
2017-03-12 1:04 ` Alexey Neyman [this message]
2017-03-12 12:14 ` Etan Kissling
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=46e45cf1-06b7-cf1a-0613-82013de1a289@att.net \
--to=stilor@att.net \
--cc=crossgcc@sourceware.org \
--cc=lovell.joshyyy@gmail.com \
/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).