Re: Need build for xulrunner
On Sun, Jun 25, 2006 at 12:07:02PM -0700, Peter Naulls wrote:
> In message <[🔎] 20060625185634.GB15411@country.grep.be>
> Wouter Verhelst <firstname.lastname@example.org> wrote:
> > * To be able to cross-build packages, a cross-toolchain has to be
> > installed. There are no prebuilt packages for this, you need to build
> > them yourselves.
> > * Debian build-dependencies do not distinguish between stuff that's
> > needed because you need to run it, and stuff that's needed because you
> > need the .so or .a file, or some (possibly architecture-specific)
> > header files.
> > * Cross-building packages makes it rather troublesome to do test suites,
> > since you can't run target code on the compile host.
> Understandable but resolveable. These have been discussed in
> considerable detail in the past, and have good solutions for EmDebian,
The only suggestions I've seen thus far required far more manual work
than is the case for buildd. Of course, I could've missed some of
them; but then I've been following this rather closely for a while (or
trying to, at least).
> > Of course, that doesn't mean you shouldn't do cross-compiled packages at
> > all; and if you can somehow guarantee the quality of the compiled code,
> > then by all means, go for it.
> > It's just that you seemed to assume that the slower Debian architectures
> > would probably cross-compile their stuff, and I wanted to point out that
> > this is, in fact, wrong, for very good reasons. That's all.
> I've made nothing like this kind of assumption.
Right, my mistake then.
> But never mind, it doesn't seem like you have much interest in this,
Actually I do. However, I'm not interested in any cross-compile setup
which would require more work from the admin than the status quo, or
which would require thousands of packages to be changed before the setup
could effectively be used. Thus far, any suggestion I've seen would
require at least one of those.
Fun will now commence
-- Seven Of Nine, "Ashes to Ashes", stardate 53679.4