Thanks Adam, I'll try this.
I just can't try it right now, since the machine I'm planning to run
sword on is a stand alone machine with no network, and right now I'm at
work.
Daniel,
If this doesn't fix the problem, I'll send you the makefile.
Thanks for all the help,
Kind regards,
Martijn Ru
On 10 Nov, 2003, at 04:37, M. Ruff wrote:
#ifdef unix# include #else# include//
This one is missing# include // This one is also
missing#endif
Seems pretty basic, but now I read this, it's probably the that 'unix'
isn't defined. I wonder why...
If you change #ifdef unix
On Mon, 2003-11-10 at 10:37, M. Ruff wrote:
> Thanks for your quick reaction Daniel,
>
> The reason I thought I needed Makefile.cfg and Makefile.post was that
> the moment I did a 'make' (after a ./configure), make complained it
> missed these two files.
Hmmm, I'm still curious about why it is
Thanks for your quick reaction Daniel,
The reason I thought I needed Makefile.cfg and Makefile.post was that
the moment I did a 'make' (after a ./configure), make complained it
missed these two files.
But okay, I'll try doing it with gmake or automake. Only the version of
automake distributed w
On Fri, 2003-11-07 at 15:23, M. Ruff wrote:
> Hi everyone,
>
> I've been trying to compile the sword API 1.5.6. on an OpenBSD 3.4
> (i386) system, but when I do a './configure' followed by a 'make' , no
> 'Makefile.cfg' and no 'Makefile.post' are created. This will cause
> 'make' to stop. When I
Hi everyone,
I've been trying to compile the sword API 1.5.6. on an OpenBSD 3.4
(i386) system, but when I do a './configure' followed by a 'make' , no
'Makefile.cfg' and no 'Makefile.post' are created. This will cause
'make' to stop. When I use gmake, the compilation starts, but after a
while, tw
