Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Microbit_Ubuntu <microbit@virginbroadband.com.au>
To: buildroot@busybox.net
Subject: [Buildroot] ct-NG proceed - 2009.11 can't write to /x-tools folder (R/O)
Date: Fri, 23 Apr 2010 23:12:13 +1000	[thread overview]
Message-ID: <1272028333.19524.9.camel@ubuntu> (raw)

Hi Grant/all,

I'm back on Ubuntu now, looked at crosstool-NG again, was quite simple
to install - must have had my wires crossed somewhere...
It built just fine in one take.

One simple question though :
I thought it prudent to leave the toolchain marked as "read only" in
ct-NG menuconfig.
However, when Buildroot-2009.11 has finished building gdb-6.8 (host,
target, server) it seems to want to make a copy of the executables to
the x-tools/arm-unknown-linux-uclibcgnueabi/bin folder (understandably
for path issues, I guess).
So BR2 make marks with dislike...

Is there a workaround, or do I temporarily allow writes to the x-tools
folder(s) ???

-- 
Best regards,
Kris

                 reply	other threads:[~2010-04-23 13:12 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1272028333.19524.9.camel@ubuntu \
    --to=microbit@virginbroadband.com.au \
    --cc=buildroot@busybox.net \
    /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