Re: Consistent handling of the DEB_BUILD_OPTIONS
On Tue, Nov 06, 2007 at 05:49:11PM +0200, Riku Voipio wrote:
> As I see what Neil wrote, nocheck (I prefer this over notest) affects
> only testsuite. As for *handling* packages that run compiled code during
> build.. well that's the reason why scratchbox was invented :)
I'm confused about how this all works.
As I see it, there are a few ways to do cross compiling:
- The old way were you set up cross toolchain, and you tell
configure you want to cross build by adding --host to it's
arguments. This will change a few things in what configure does,
like setting CC differently, not running AC_RUN_IFELSE but use
some default instead.
- Emulate the cpu and pretend everything really is the host cpu.
There is no need to call configure with --host. We can't detect
that we're doing a cross build.
In the first case it makes sense not to run the testsuite for things
that need to run on the host cpu. In the second case we can run it,
and I think we should.
>From what I get from the description of scratchbox, it's doing the
second thing without actually emulating everything. From what I get
it uses a cross toolchain on the real cpu and the rest is emulated.
I think I've been told that we can't detect that we're cross building
by looking at dpkg-architecture. So I have to wonder why you don't want
to run the testsuite in that case.