Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Hinko Kočevar" <hinko.kocevar@cetrtapot.si>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot 2009.02 released
Date: Thu, 19 Feb 2009 18:41:22 +0100 (CET)	[thread overview]
Message-ID: <1983108078.3421235065282329.JavaMail.root@zimbra-store.cetrtapot.si> (raw)
In-Reply-To: <53818555.3401235065156991.JavaMail.root@zimbra-store.cetrtapot.si>


----- Original Message -----
From: "Ulf Samuelsson" <ulf.samuelsson@atmel.com>
To: "Hinko Kocevar" <hinko.kocevar@cetrtapot.si>, "Peter Korsgaard" <jacmet@uclibc.org>
Cc: buildroot at uclibc.org
Sent: Thursday, February 12, 2009 7:11:24 PM GMT +01:00 Amsterdam / Berlin / Bern / Rome / Stockholm / Vienna
Subject: Re: [Buildroot] Buildroot 2009.02 released


>>>>>> "Hinko" == Hinko Kocevar <hinko.kocevar@cetrtapot.si> writes:
>
> Hi,
>
> Hinko> Building gdb for cris-v10 architecture fails with:
>
> Ahh, seems like you should have tested the release candidates better
> ;)
>

As far as I have seen, there has been very little testing activitiy going on 
before the release.
There are several packages that does not build, at least for ARM.
Several packages build but crash when you start the target.

Zero documentation on what builds and what does not build.

Zero documentation on what builds but does not run.

True.

Maybe we could put some focus on these points.

I'll try to steal some time to try out basic packages (for starters) that build & run on cris-v10 arch. That's the only embedded arch I can test.

What about he packages that can not be built for some specific arch, for some reason or another (too few resources CPU, mem, flash, ..)? Should they be marked or noted somehow to inform us about its status on selected arch?

Regards,
Hinko


-- 
?ETRTA POT, d.o.o., Kranj
Planina 3
4000 Kranj
Slovenia, Europe
Tel. +386 (0) 4 280 66 03
E-mail: hinko.kocevar at cetrtapot.si
Http: www.cetrtapot.si

       reply	other threads:[~2009-02-19 17:41 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <53818555.3401235065156991.JavaMail.root@zimbra-store.cetrtapot.si>
2009-02-19 17:41 ` Hinko Kočevar [this message]
2009-02-19 19:10   ` [Buildroot] Buildroot 2009.02 released Peter Korsgaard
2009-02-22  7:22 Frank Hoeflich
2009-02-24 18:15 ` Ulf Samuelsson
  -- strict thread matches above, loose matches on Subject: below --
2009-02-12  9:22 Peter Korsgaard
2009-02-12 12:30 ` Hinko Kocevar
2009-02-12 12:42   ` Peter Korsgaard
2009-02-12 14:45     ` Hinko Kocevar
2009-02-12 18:11     ` Ulf Samuelsson
2009-02-19 19:15       ` Peter Korsgaard
2009-02-19 22:38         ` Ulf Samuelsson
2009-02-20  8:23           ` Peter Korsgaard
2009-02-21  9:29             ` Ulf Samuelsson
2009-02-22  9:47               ` Peter Korsgaard
2009-02-23 11:02                 ` Ulf Samuelsson
2009-02-14  2:42 ` Hamish Moffatt
2009-02-15 15:34 ` Thomas Petazzoni
2009-04-29  9:38 ` Peter Korsgaard
2009-04-29 10:17   ` Sven Neumann
2009-04-29 10:25     ` Peter Korsgaard

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=1983108078.3421235065282329.JavaMail.root@zimbra-store.cetrtapot.si \
    --to=hinko.kocevar@cetrtapot.si \
    --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