All of lore.kernel.org
 help / color / mirror / Atom feed
From: Khem Raj <raj.khem@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: calamari (ppc e500v2) failure
Date: Tue, 11 May 2010 08:33:08 -0700	[thread overview]
Message-ID: <20100511153308.GB15186@gmail.com> (raw)
In-Reply-To: <1273588323.22943.397.camel@trini-m4400>

On (11/05/10 07:32), Tom Rini wrote:
> On Sun, 2010-05-09 at 22:49 -0700, Khem Raj wrote:
> > On (09/05/10 11:24), Tom Rini wrote:
> > > On Sat, 2010-05-08 at 08:11 -0700, Tom Rini wrote:
> > > > On Sat, 2010-05-08 at 09:06 +0200, Frans Meulenbroeks wrote:
> > > > > 2010/5/7 Tom Rini <tom_rini@mentor.com>:
> > > > > > Hey all,
> > > > > >
> > > > > > With DISTRO=minimal and MACHINE=calamari, I see the following failure in
> > > > > > gnutls (using fe4ff6940b06c73d5b88224b99750bf65accf13d in oe.dev):
> > > > > > http://pastebin.com/cjAStcLb and I confirmed this prior to the RP merge,
> > > > > > so this is unrelated.
> > > > > 
> > > > > Which eglibc is that?
> > > > > The issues I had seemed due to some catch22 situation that I cured; I
> > > > > started a clean build yesterday before I left work & can tell the
> > > > > results on monday.
> > > > > My distro was angstrom, machine calamari, this uses eglibc 2.10. Is
> > > > > minimal also using 2.10 or is it at 2.11
> > > > > 
> > > > > I can also try to kick off a minimal build on monday
> > > > 
> > > > minimal is eglibc 2.10.  I'll try an Angstrom build.
> > > 
> > > With Angstrom, gcc-cross-initial fails building libgcc, config.log has:
> > > cc1: error: not configured for ABI: 'spe'
> > > configure:2591: $? = 1
> > > configure: failed program was:
> > > ... standard empty program ...
> > > configure:2605: error: cannot compute suffix of object files: cannot
> > > compile
> > > 
> > > Ubuntu 9.10 x86_64 host
> > 
> > Could you test with attached gcc patch please. This should fix the
> > undefined symbol error. You could use minimal distro for SPE targets
> > it should work. Please let me know if it works for you.
> 
> This fixes the e300c3 / ppc603e issue, but not the gnutls issue (which
> is now seen on those platforms).  So the general problem of -Os + ppc
> not being right with GNU.org toolchains is still there, on 4.4.3 at
> least.

out of order epilogue/prologue are added in gcc 4.4 so I expect 4.4+ to
show this issue. That said, when I tried for calamari from scratch 
bitbake gnutls it went through fine on Kubuntu 10.04/x86_64 build machine.
> 
> -- 
> Tom Rini <tom_rini@mentor.com>
> Mentor Graphics Corporation
> 
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel



  reply	other threads:[~2010-05-11 15:36 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-07 16:31 calamari (ppc e500v2) failure Tom Rini
2010-05-08  7:06 ` Frans Meulenbroeks
2010-05-08 15:11   ` Tom Rini
2010-05-09 18:24     ` Tom Rini
2010-05-10  5:49       ` Khem Raj
2010-05-11 14:32         ` Tom Rini
2010-05-11 15:33           ` Khem Raj [this message]
2010-05-10  8:40       ` Frans Meulenbroeks
2010-05-10 16:47         ` Tom Rini
2010-05-11  6:53           ` Frans Meulenbroeks
2010-05-11 14:20             ` Tom Rini
2010-05-10 16:47         ` Khem Raj

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=20100511153308.GB15186@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 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.