From: Ivan Kuten <ivan.kuten@promwad.com>
To: buildroot@busybox.net
Subject: [Buildroot] Libtool error with AVR32
Date: Fri, 28 Sep 2007 22:42:48 +0300 [thread overview]
Message-ID: <46FD5938.303@promwad.com> (raw)
In-Reply-To: <20070928165114.GM20951@aon.at>
>
> Well, I'm thinking about doing this, yes. The problem with a project
> like buildroot (or any distribution) is that it's a moving target per
> definition. Software receives bug-fixes (upstream) or fancy features
> that you may want to use, so you have to update packages sometimes.
>
> We don't add much new "features", really. Except for huge experimental
> bundles like xorg only a small number of packages are added (which is a
> good thing since they cost time to keep uptodate).
>
I think it would be good to create a -testing branch and to push in this
branch fixes and additions. And main branch keep stable as possible.
Also it would be useful to create something like this "http://kegel.com/crosstool/crosstool-0.43/buildlogs/"
but for package/target status.
I can help if we decide to do something in that direction.
Best regards,
Ivan
--------------------------------
Embedded Linux engineer,
Promwad Company: http://www.promwad.com/
Homepage : http://www.ivankuten.com/
--------------------------------
next prev parent reply other threads:[~2007-09-28 19:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-27 18:17 [Buildroot] Libtool error with AVR32 don
2007-09-27 20:53 ` Ulf Samuelsson
2007-09-27 22:19 ` don
2007-09-27 22:34 ` Bernhard Fischer
2007-09-27 23:42 ` Ulf Samuelsson
2007-09-28 16:09 ` don
2007-09-28 16:38 ` Ulf Samuelsson
2007-09-28 18:34 ` don
2007-09-28 16:51 ` Bernhard Fischer
2007-09-28 19:06 ` Ulf Samuelsson
2007-09-28 19:42 ` Ivan Kuten [this message]
2007-09-28 19:17 ` Thiago A. Corrêa
2007-09-28 19:29 ` Bernhard Fischer
-- strict thread matches above, loose matches on Subject: below --
2007-10-14 20:09 don
2007-10-14 23:34 ` Ivan Kuten
2007-10-15 3:47 ` don
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=46FD5938.303@promwad.com \
--to=ivan.kuten@promwad.com \
--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