Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit:	trunk/buildroot/toolchain/external-toolchain
Date: Tue, 17 Jun 2008 09:16:43 +0200	[thread overview]
Message-ID: <87ej6wwmxw.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <20080617042319.GA17083@cloud.net.au> (Hamish Moffatt's message of "Tue\, 17 Jun 2008 14\:23\:19 +1000")

>>>>> "Hamish" == Hamish Moffatt <hamish@cloud.net.au> writes:

Hi,

 Hamish> On Mon, Jun 16, 2008 at 05:22:46AM -0700, jacmet at uclibc.org wrote:
 >> config BR2_TOOLCHAIN_EXTERNAL_PATH
 >> string "External toolchain path"
 >> -	default ""
 >> +	default "/path/to/staging_dir/usr"
 >> help
 >> Path to where the external toolchain is installed.

 Hamish> I've set this to "$(BR2_STAGING_DIR)/usr" here, which might
 Hamish> be a good default?

You think so? I wouldn't expect having buildroot install package stuff
together with the (potentially read only) external toolchain would be
a common setup.

 >> config BR2_TOOLCHAIN_EXTERNAL_PREFIX
 >> string "External toolchain prefix"
 >> -	default ""
 >> +	default "$(ARCH)-linux"
 >> help
 >> This the the external toolchain prefix. For example:
 >> armeb-unknown-linux-gnu, mipsel-unknown-linux-gnu, etc.

 Hamish> Probably not a useful default, given that all the examples
 Hamish> have -gnu etc after them? Mine is armeb-linux-uclibcgnu here;
 Hamish> again you can probably construct something like
 Hamish> "$(ARCH)-$(BR2_GNU_TARGET_SUFFIX)".

Don't you have an armeb-linux symlink? For the stuff I compile (arm,
i386, ppc) there's symlinks from the arm-linux-uclibc-<whatever> to
arm-linux-<whatever>.

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2008-06-17  7:16 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-16 12:22 [Buildroot] svn commit: trunk/buildroot/toolchain/external-toolchain jacmet at uclibc.org
2008-06-16 13:54 ` Bernhard Fischer
2008-06-16 14:07   ` Peter Korsgaard
2008-06-16 15:35     ` Bernhard Fischer
2008-06-17  4:23 ` Hamish Moffatt
2008-06-17  7:16   ` Peter Korsgaard [this message]
2008-06-17 10:47     ` Hamish Moffatt
2008-06-17 13:45       ` Peter Korsgaard
2008-06-17 14:29         ` Bernhard Fischer
2008-06-17 14:55           ` Peter Korsgaard
2008-06-17 15:45             ` Bernhard Fischer
2008-06-18  1:18         ` Hamish Moffatt
2008-06-18  5:03           ` [Buildroot] svncommit: trunk/buildroot/toolchain/external-toolchain Ulf Samuelsson
2008-06-18  7:36           ` [Buildroot] svn commit: trunk/buildroot/toolchain/external-toolchain Peter Korsgaard
2008-06-18  1:05       ` Hamish Moffatt
  -- strict thread matches above, loose matches on Subject: below --
2009-01-12 12:54 laird at uclibc.org
2008-11-03 10:37 jacmet at uclibc.org
2008-11-03 10:32 jacmet at uclibc.org
2008-10-17 10:19 jacmet at uclibc.org
2007-07-17  0:18 sjhill at uclibc.org
2007-04-28 17:10 sjhill at uclibc.org
2007-04-19  2:04 sjhill at uclibc.org

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