On Thu, 23 Jun 2005, Robert P. J. Day wrote:
>On Thu, 23 Jun 2005, Christian Smith wrote:
>
>> On Thu, 23 Jun 2005, Robert P. J. Day wrote:
>>
>> > um ... what appears to be the problem here? certainly, i have the
>> >entire gnu development suite installed, and i've used this incantation
>> >to cross-compile other packages, like expat.
>>
>> SQLite requires a parser generator called lemon, which is bundled
>> with the sources. This has to be compiled and run on the build
>> machine, and cannot be cross compiled. Try setting BUILD_CC to the
>> host native compiler.
>
>as in, just add "BUILD_CC=/usr/bin/gcc"? same error. or did i
>misunderstand what you were suggesting?
Well, I got it wrong anyway. TARGET_CC is the cross compiler. Have a read
of configure.ac, which lists the expected environment variables that can
be used. Upon further examination, you need to prefix config_ to the
variable name:
$ export config_TARGET_CC=cross-gcc
$ ./configure ...
However, I tried using an arbitrary cross compiler (gcc-h8300-hms) and
libtool crapped out anyway.
>
>> Alternatively, use the Makefile.linux-gcc template used by DRH, and
>> change the variables in there.
>
>ok, i'll give that a shot, too, but i'd still like to know what the
>problem is with the configure phase.
One of the known problems is that the autoconf part is basically
unmaintained, and noone has stepped up to take the reigns. I always use
either the Makefile.linux-gcc as a template, or use my own imake based
Imakefile. I'd suggest the former unless you're integrating with another
build system and particularly require an autoconf or imake based build.
>
>rday
>
Christian
--
/"\
\ / ASCII RIBBON CAMPAIGN - AGAINST HTML MAIL
X - AGAINST MS ATTACHMENTS
/ \
