[Buildroot] Hiding non-buildable packages

Ulf Samuelsson ulf at atmel.com
Wed Aug 22 20:24:56 UTC 2007

ons 2007-08-22 klockan 21:13 +0200 skrev Bernhard Fischer:
> On Tue, Aug 21, 2007 at 10:28:57PM +0200, Ulf Samuelsson wrote:
> >A lot of the packages does not build.
> Fixing them is the right thing to do.

Yes, the goal is to have all packages working for all architectures.
We are not there by far.

> >Some only build for some targets.
> Certain packages (think specific HW support) should depend on a specific
> arch. Which are these?

I do not have this list.

> >I think it would be nice to have the possibility
> >to set a config item, which resulted in that only
> >packages which seems to build are really visible.
> I object to this if you just want to avoid helping to provide patches to
> upstream that do fix the respective packages that are ment to work fine.

Do you think I have been too passive submitting patches during the last
2 months :-)

I see this as a help to quickly determine what I can do and cannot do 
at a certain point of time. The goal is to remove the restrictions.

I am mostly interested in ARM and AVR32.
There are a lot of packages, which needs an active porting effort to 
build on the AVR32, since those packages explicitly state which 
architectures are supported, and the AVR32 might not be listed.
It would be very good if people would know up front what can be done at
the moment.

On the ARM, the problem is different. 
Packages, not involving direct access to architecure specific H/W
(mostly PC stuff) should build, but for various reasons they do not.
If people starting using buildroot had this help, then they could
spend their time first building a working filesystem, and then select
a specific, non-working package, to debug.
Today endless hours can be spent on trying to build stuff which ends in
a failure.
If it is known not to build, it is good to communicate this to others.

With this fix, it will be easy to grep package/*/Config.in 
for a list of non-working packages, and then prioritize
what to work on.

Best Regards,
Ulf Samuelsson

More information about the buildroot mailing list