All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom <fivemiletom@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] BR2_STAGING_DIR config?
Date: Thu, 31 May 2007 12:16:10 -0700	[thread overview]
Message-ID: <465F1EFA.3090403@gmail.com> (raw)
In-Reply-To: <20070531164543.GA22322@aon.at>

Thanks.

 From the systems I use, 3.4 could be dropped: Fedora Core 6 comes with 
4.1.1 and Cygwin is (soon?) to upgrade from 3.4.4 to 4.2.0.

Bernhard Fischer wrote:
> On Thu, May 31, 2007 at 09:33:25AM -0700, Tom wrote:
>> Hello,
>>
>> I want to use the cross development toolchain also for other projects 
>> and thus defined:
>> BR2_STAGING_DIR="/tw/tools/gnu/cygwin/arm-linux"
>>
>> However, I am getting this error in libutils, what am I missing please?
> 
> I was looking into toolchains that can be moved around to other machines
> without problems.
> See the archives, thread
> Subject: Re: [Buildroot] [patch] sysroot support in toolchain,
>         use correct pathes in staging_dir
> 
> for details.
> The last patch is here:
> http://uclibc.org/~aldot/buildroot.mine.cow.20070515-1321.diff.bz2
> 
> But i am hesitating to fix this, since the outdated, deprecated gcc-3.4
> series will break with these changes (and i didn't see yet how to fix
> that without touching this ancient gcc, which i refuse to do).
> 
>>From my POV, it would be fine to discontinue gcc-3.4, not sure what
> people think about this, though.
> 
> HTH,
> 

  reply	other threads:[~2007-05-31 19:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-31 16:33 [Buildroot] BR2_STAGING_DIR config? Tom
2007-05-31 16:45 ` Bernhard Fischer
2007-05-31 19:16   ` Tom [this message]
     [not found]   ` <46607980.9060606@atmel.com>
     [not found]     ` <20070601213849.GG12010@aon.at>
2007-06-04 19:43       ` Ulf Samuelsson

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=465F1EFA.3090403@gmail.com \
    --to=fivemiletom@gmail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.