Hi Anton,
Just one more question, do you have a simple, yet explanatory example
of the multi tasking words in gforth ?
Thank
Andrew
On 15 Sep 2005, at 14:27, Anton Ertl wrote:
Andrew Holt wrote:
Hi,
On 15 Sep 2005, at 10:47, Nick Rout wrote:
On Thu, 2005-09-15 at 10:11 +0100, Andrew Holt wrote:
The example you give is for a 386 target. I presume that I have to
specify CC=<compiler> to configure,
Yes.
You also have to specify ac_cv_c_bigendian=yes (I see you did that).
checking for asm.fs... arch/386/asm.fs
checking for disasm.fs... arch/386/disasm.fs
Oops, I guess you also need to specify the machine as
powerpc-unkown-linux. I think you need to use the --host option for
this.
checking if and how we can waste code space... configure: error:
cannot run test program while cross compiling
Hmm, the easiest way to work around that ist to delete everything
between
for i in ".skip 16" ".block 16" ".org .+16" ".=.+16" ".space 16"
and the next
done
in configure (or in configure.in, and run autoconf afterwards), and
replace it with
skipcode=".skip 16"
or whatever works on that assembler (".skip 16" works on my PPC-Linux
box). Or, alternatively, with
skipcode=no
(which will disable dynamic native code generation (more speed and
more memory consumption).
machine='386'
Does this refer to the host or the target ?
In autoconf terminology, to the host (it's the host of the program you
are compiling).
- anton
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
