Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Rolf Leggewie <no2spam@nospam.arcornews.de>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH 2/4] gcc: fix libstdc/libgcc packaging on x86_64
Date: Fri, 14 Aug 2009 15:06:31 +0200	[thread overview]
Message-ID: <h63ngq$s80$1@ger.gmane.org> (raw)
In-Reply-To: <4A84B3E7.4070602@tait.co.nz>

Douglas Royds wrote:
> FWIW, Ubuntu Hardy LTS 8.04 is on GCC 4.2.3:
> 
>     http://packages.ubuntu.com/search?keywords=gcc
> 
> Hardy LTS is the "Long-Term Support" version of Ubuntu, that they 
> support for 2 years. It will be replaced in April 2010, which isn't 
> tooooo far away.

Hardy is my main build machine.  I hope OE will continue to work with it.

Hardy will be EOL'd on the desktop in April 2011.  Support for the
console/server version will run another two years after that.

https://wiki.ubuntu.com/Releases




  reply	other threads:[~2009-08-14 13:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-13 15:00 [PATCH 1/4] site/x86_64-linux: Add some vars from ix86-common Michael Smith
2009-08-13 15:00 ` [PATCH 2/4] gcc: fix libstdc/libgcc packaging on x86_64 Michael Smith
2009-08-13 15:00   ` [PATCH 3/4] udev 141: fix " Michael Smith
2009-08-13 15:00     ` [PATCH 4/4] openssl.inc: fix packaging on x86_64; use INC_PR Michael Smith
2009-09-01 22:00     ` [PATCH 3/4] udev 141: fix packaging on x86_64 Michael Smith
2009-08-13 15:43   ` [PATCH 2/4] gcc: fix libstdc/libgcc " Khem Raj
2009-08-14 13:06     ` Michael Smith
2009-08-14  0:46   ` Douglas Royds
2009-08-14 13:06     ` Rolf Leggewie [this message]
2009-08-14 14:15       ` Michael Smith

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='h63ngq$s80$1@ger.gmane.org' \
    --to=no2spam@nospam.arcornews.de \
    --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