Re: Cross compiling texinfo-4.7

[Stepan Kasal]

Hello,

On Wed, Oct 06, 2004 at 05:11:38PM -0400, Karl Berry wrote:
>     1) I think that the configure script could be switched to a ``tools only
>     mode'' by an external variable, say TEXINFO_CONFIGURE_TOOLS.
> 
> Sorry, I'm lost at step one.  What does "tools only" mean?

when you run

  ./configure --build=i686-pc-linux-gnu --host=hppa2.0-unknown-linux-gnu

you are building on your PC and want to get binaries for HPPA.

In order to build the docs, you need a few binaries (makeinfo, ...) which
run on your PC.

So the trick is to create a ``tool build,'' where both --build and --host
are i686-pc-linux-gnu .

During that ``tool build'' you don't have to make all in subdir ``doc,''
you only need the binaries.

If this explanation is confusing, never mind.

When Mark (or I) create the patch, I'll try to advocate it.  It'll be much
easier when it arrives.
1) You'll se the code.
2) You would be able to check that it doesn't interfere with the good old
native build too much.

> By the way, I'm not clear why it is ever useful to cross compile Texinfo.

Well, most of GNU usually cross-compiles.  Autoconf manual takes care to
teach you to use compile-tests whenever possible, not run-tests.
(I mean that ./configure should not try to _run_ the compiled test
programs, if not absolutely necessary.)

Texinfo is unusual in the respect that it needs to run the programs
which has just been built.  Most projects don't need that and thus 
cross compile smoothly.

(But Mark's explanation why cross compile is useful is much better,
of course.)

OK, I like this issue.  So you can rest, redirecting all cross compile
discussion to me.
Until I'll come and ask you to accept an actual patch.  Then you'll have
a problem. ;-)

Have a nice day,
        Stepan