Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@sunsite.dk>
To: buildroot@busybox.net
Subject: [Buildroot] [git commit master] defconfigs: use new default location for STAGING_DIR
Date: Wed, 16 Dec 2009 20:47:46 +0100	[thread overview]
Message-ID: <87vdg666ql.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <a038bef50912161135g96cd695m27e23a7811e37fe7@mail.gmail.com> (Chris Packham's message of "Wed, 16 Dec 2009 14:35:16 -0500")

>>>>> "Chris" == Chris Packham <judge.packham@gmail.com> writes:

 >> -BR2_STAGING_DIR="/usr/local/$(ARCH)/gcc-$(BR2_GCC_VERSION)-uclibc"
 >> +BR2_STAGING_DIR="$(BASE_DIR)/staging"
 >> ?# BR2_FPU_SUFFIX is not set
 >> ?BR2_TOPDIR_PREFIX=""
 >> ?BR2_TOPDIR_SUFFIX=""

 Chris> Not that I know anything about arm_toolchain_defconfig but from its
 Chris> name and the old BR2_STAGING_DIR value I'm guessing it attempts to
 Chris> generate a standalone toolchain and install it in /usr/local. You
 Chris> might want to change this one back.

Yes I noticed.
I actually think we should probably just delete that defconfig - Having
a generic arm defconfig (which tries to write files under /usr/local/
where most normal users don't have permissions), uses OABI and has the
AT91 stuff enabled is probably not that useful after all.

-- 
Bye, Peter Korsgaard

      reply	other threads:[~2009-12-16 19:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-16 19:02 [Buildroot] [git commit master] defconfigs: use new default location for STAGING_DIR Peter Korsgaard
2009-12-16 19:35 ` Chris Packham
2009-12-16 19:47   ` Peter Korsgaard [this message]

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=87vdg666ql.fsf@macbook.be.48ers.dk \
    --to=jacmet@sunsite.dk \
    --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