Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Robert Schuster <thebohemian@gmx.net>
To: openembedded-devel@lists.openembedded.org
Subject: [RFC] GCC 4.3.1 unbuildable due to unapplyable patches - remove it then?
Date: Wed, 07 Jul 2010 10:16:23 +0200	[thread overview]
Message-ID: <4C3437D7.8050505@gmx.net> (raw)

[-- Attachment #1: Type: text/plain, Size: 307 bytes --]

Hi,
GCC 4.3.1 does not build for an ARM target because a patch does not fit.
So I assume that no one is really interested in that version of GCC
anymore and would remove it then if nobody fixes the patch situation:

http://tinderbox.openembedded.net/public/logs/task/6443736.txt

Regards,
Robert


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 270 bytes --]

             reply	other threads:[~2010-07-07  8:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-07  8:16 Robert Schuster [this message]
2010-07-07  8:35 ` [RFC] GCC 4.3.1 unbuildable due to unapplyable patches - remove it then? Graham Gower
2010-07-07  8:37 ` Frans Meulenbroeks
2010-07-08  8:10 ` Robert Schuster

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=4C3437D7.8050505@gmx.net \
    --to=thebohemian@gmx.net \
    --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