Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Khem Raj <raj.khem@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH 0/5][v4] Make multi-machine toolchains to co-exist (Alternate approach)
Date: Tue, 3 Aug 2010 12:58:47 -0700	[thread overview]
Message-ID: <20100803195847.GB5264@gmail.com> (raw)
In-Reply-To: <i39d10$d2f$1@dough.gmane.org>

On (03/08/10 17:36), Koen Kooi wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> On 03-08-10 15:35, Martin Jansa wrote:
> > On Tue, Aug 03, 2010 at 12:13:58PM +0200, Koen Kooi wrote:
> >> -----BEGIN PGP SIGNED MESSAGE-----
> >> Hash: SHA1
> >>
> >> Acked-by: Koen Kooi <k-kooi@ti.com>
> >>
> >> If noone objects, can we get this in ASAP?
> > 
> > Building from scratch armv4t then armv6 was ok, building few more
> > packages for armv4t again still worked, but now I've upgraded gcc/eglibc
> > and building eglibc-initial for armv4t first fails:
> > 
> > http://tinderbox.openembedded.org/packages/665289/
> > http://build.shr-project.org/tests/jama/config.log
> > 
> > see 
> > configure: error: compiler support for __thread is require
> > and
> > Fatal error: Invalid -march= option: `armv4t'
> 
> I had that with a previous incarnation of that patchset, but it seems to
> have gone away.
> Do we want to solve this problem first or apply the patches and solve it
> later?

All right the beast is in. Please rebuild from scratch as the location of
toolchain has once again changed.

Thanks a bunch to everyone who helped in testing these patches and thereby
making them worthy

Thanks

-Khem



  parent reply	other threads:[~2010-08-03 19:59 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-31  5:34 [PATCH 0/5][v4] Make multi-machine toolchains to co-exist (Alternate approach) Khem Raj
2010-07-31  5:34 ` [PATCH 1/5] bitbake.conf, cmake.bbclass, cross.bbclass, icecc.bbclass: Point the toolchain paths to new multi-machine friendly toolchain install location Khem Raj
2010-07-31  5:34 ` [PATCH 2/5] binutils-cross.inc: Dont install duplicate copies of tools create relative symlinks instead Khem Raj
2010-07-31  5:34 ` [PATCH 3/5] gcc, eglibc: Use the paths for mutli-machine safe toolchain install Khem Raj
2010-07-31  5:34 ` [PATCH 4/5] recipes: Fix the PATHs for toolchains Khem Raj
2010-07-31  5:34 ` [PATCH 5/5] mpfr_3.0.0.bb: Override needs to be thumb instead of armv4t Khem Raj
2010-07-31  9:48 ` [PATCH 0/5][v4] Make multi-machine toolchains to co-exist (Alternate approach) Koen Kooi
2010-07-31 13:34   ` Koen Kooi
2010-07-31 18:54     ` Koen Kooi
2010-08-02  9:33       ` Koen Kooi
2010-08-02 16:27         ` Khem Raj
2010-08-03 10:13           ` Koen Kooi
2010-08-03 10:21             ` Martin Jansa
2010-08-03 10:29               ` Andrea Adami
2010-08-03 10:31             ` Frans Meulenbroeks
2010-08-03 13:35             ` Martin Jansa
2010-08-03 15:36               ` Koen Kooi
2010-08-03 17:20                 ` Khem Raj
2010-08-04  9:04                   ` Martin Jansa
2010-08-03 19:58                 ` Khem Raj [this message]
2010-08-03 19:56               ` Khem Raj
2010-08-01 15:48 ` Eric Bénard

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=20100803195847.GB5264@gmail.com \
    --to=raj.khem@gmail.com \
    --cc=openembedded-devel@lists.openembedded.org \
    /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