David Woodhouse wrote: >>... fixing >> them in the upstream packages (or in the autoconf system itself). >> >> Once someone fixes the cross-compilation issues for a package, they usually >> stay fixed, if the fixes are mainlined. > > I don't think that's true, unfortunately. Autoconf makes it _easy_ to do > the wrong thing, and people will often introduce new problems.
If autoconf is the problem (and I think it is), then that's what should be fixed (see my original post). At a minimum, it would be nice if it had more built-in detection and warning of techniques that were dangerous for cross-compilation. While I was writing the above, Paul Mundt wrote: > You can > either try to fix the packages in question, convince the package > developers to rip out the parts that cause trouble for your environment, > fix your own build environment to meet the needs of the packages, or > whine about it on a mailing list. Empirically we already know which one > of those options is going to win out. ;-) LOL. Well, at least Rob has put his money where his mouth is (so to speak) with Firmware Linux. The chance that I'll do anything but whine about autoconf is slim indeed... I'll shut up now! -- Tim ============================= Tim Bird Architecture Group Chair, CE Linux Forum Senior Staff Engineer, Sony Corporation of America ============================= -- To unsubscribe from this list: send the line "unsubscribe linux-embedded" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
