Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: S0L0 at gmx-topmail.de <S0L0@gmx-topmail.de>
To: buildroot@busybox.net
Subject: [Buildroot] {buildroot 0004384]: GCC 4.3.1 fails with cannot compute suffix of object files
Date: Wed, 04 Feb 2009 00:34:38 +0100	[thread overview]
Message-ID: <20090203233438.203590@gmx.net> (raw)
In-Reply-To: <4985F291.5010002@hq.tensilica.com>

I have the same problem. Build fails and I can not find the patchfile. :(

I would be very glad, too hear something regarding this issue.

S0l0
-------- Original-Nachricht --------
> Datum: Sun, 01 Feb 2009 11:05:53 -0800
> Von: Maxim Grigoriev <maxim@tensilica.com>
> An: Maxim Grigoriev <maxim@tensilica.com>
> CC: buildroot at uclibc.org
> Betreff: Re: [Buildroot] {buildroot 0004384]: GCC 4.3.1 fails with cannot compute suffix of object files

> Is this the right mailing list to ask questions about BUILDROOT ?
> 
> Should I ask some official maintainers directly instead ?
> 
> If there is a communication policy described somewhere, please, refer me 
> to it.
> 
> Thanks,
> -- Maxim
> 
> 
> Maxim Grigoriev wrote:
> > There is a buildroot issue 0004384:
> >
> >    
> http://lists.uclibc.org/pipermail/buildroot/2008-September/010792.html
> >
> > I understand it's a generic architecture-independent GCC 4.3.1+ compiler
> > problem
> > mentioned several times in different places ( e.g. bugzilla PRs 35577, 
> > 35693 ).
> >
> > On the buildroot mailing, list I found a reference to the patch
> >
> >   gcc-4.3.1-compile.patch 
> >
> > introduced by "antezedens" somewhere around 09-10-08.
> > But, I was not able to find this patch. Looks like it was withdrawn.
> >
> >                           * * * * *
> >
> > My question is: is this build failure supposed to be fixed on
> > the BUILDROOT makefiles/scripts level ? Or, setting 
> >
> > LD_LIBRARY_PATH=$PWD/toolchain_build_arm/mpfr/lib:$LD_LIBRARY_PATH
> >
> > from the top of buildroot tree is assumed to be a standard
> > setup for the buildroot build ? Is it documented anywhere ?
> >
> > Thanks,
> > -- Maxim
> >
> >
> >
> >
> > _______________________________________________
> > buildroot mailing list
> > buildroot at busybox.net
> > http://lists.busybox.net/mailman/listinfo/buildroot
> >   
> 
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot

-- 
Psssst! Schon vom neuen GMX MultiMessenger geh?rt? Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger01

  reply	other threads:[~2009-02-03 23:34 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-30 23:02 [Buildroot] {buildroot 0004384]: GCC 4.3.1 fails with cannot compute suffix of object files Maxim Grigoriev
2009-02-01 19:05 ` Maxim Grigoriev
2009-02-03 23:34   ` S0L0 at gmx-topmail.de [this message]
2009-02-03 23:51     ` Maxim Grigoriev
2009-02-04  4:02       ` Maxim Grigoriev
2009-02-15  2:20         ` Shinya Kuribayashi
  -- strict thread matches above, loose matches on Subject: below --
2008-09-27 10:15 [Buildroot] [buildroot " bugs at busybox.net
2008-09-10 11:27 bugs at busybox.net
2008-09-10  7:30 bugs at busybox.net
2008-07-31 11:57 bugs at busybox.net

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=20090203233438.203590@gmx.net \
    --to=s0l0@gmx-topmail.de \
    --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