All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philip Balister <philip@balister.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Which distro for OE development?
Date: Thu, 19 Nov 2009 08:54:38 -0500	[thread overview]
Message-ID: <4B054E1E.80602@balister.org> (raw)
In-Reply-To: <alpine.LFD.2.00.0911190818300.16520@localhost>

On 11/19/2009 08:19 AM, Robert P. J. Day wrote:
> On Thu, 19 Nov 2009, Hodgson, Simon wrote:
>
>> I'm setting up a new machine with Linux specifically to use for
>> OpenEmbedded development. Which Linux distro should I go with?
>>
>> I'm looking to make it as easy as possible to get started, so
>> ideally all the packages I need will be available from that distro's
>> standard repositry.
>>
>> I've tried SuSE in the past and given up trying to get all of the
>> required tools installed, and more recently been using Debian, but
>> the Python version in Debian is a few versions behind and there was
>> talk of OE soon requiring a more up to date version.
>>
>> Ubuntu is a good candidate at the moment as I belive there won't be
>> any hardware issues with the laptop I want to use, but this wiki
>> page suggests there's some faffing to do
>> http://wiki.openembedded.net/index.php/Gcc_issues_in_Intrepid_and_later
>> which I'd like to avoid if possible - does anyone know if these
>> issues are present in the latest version 9.10?
>
>    despite my occasional(?) shrieks of outrage, fedora has generally
> served me well for OE builds.

You should be fine with the "mainstream" distros since it is likely 
someone on the list is using it and can help you with any issues that 
crop up. As you can see at the moment, the Fedora users are working out 
a potential issue with F12.

Philip



  reply	other threads:[~2009-11-19 13:56 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-19 13:06 Which distro for OE development? Hodgson, Simon
2009-11-19 13:19 ` Robert P. J. Day
2009-11-19 13:54   ` Philip Balister [this message]
2009-11-19 14:02     ` Robert P. J. Day
2009-11-19 13:22 ` Marcin Juszkiewicz
2009-11-19 13:25   ` Ahsan Khawaja
2009-11-19 13:37 ` Phil Blundell
2009-11-19 13:50   ` Ricardo Salveti de Araujo
2009-11-19 13:57     ` Robert P. J. Day
2009-11-19 15:34 ` Marco Cavallini
2009-11-19 15:55 ` Bjørn Forsman
  -- strict thread matches above, loose matches on Subject: below --
2008-09-02 11:42 Eliyahu Skoczylas
2008-09-02 12:35 ` Florian Boor
2008-09-02 12:43 ` Andrea Adami
2008-09-02 13:39   ` Philip Balister
2008-09-02 15:07     ` Stanislav Brabec
2008-09-02 15:19     ` Martyn Welch
2008-09-02 19:00       ` Khem Raj
2008-09-02 13:37 ` Michael 'Mickey' Lauer

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=4B054E1E.80602@balister.org \
    --to=philip@balister.org \
    --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.