| |
G4DJB > JNOS 03.01.05 17:57l 41 Lines 1629 Bytes #999 (0) @ WW
BID : BE0070G4DJB
Read: GUEST
Subj: Re: ERR: compiling JNOS 2.0
Path: DB0FHN<DB0MRW<DB0RGB<OK0PPL<DB0RES<DK0WUE<7M3TJZ<ZL2TZE<GB7PZT<GB7MAX<
GB7FLY<GB7NLY
Sent: 041231/1406z 26608@GB7NLY.#42.GBR.EU $:BE0070G4DJB [Camberley] NNA314
Hi Frank,
Yes, this is a known problem. For the latest info check the TAPR NOS-BBS
mail archives at http://lists.tapr.org/pipermail/nos-bbs/
However, for Frank's particular problem of "unable to open include file"
the following message I submitted to the TAPR mailing list may be of help.
It would appear that on early releases of JNOS 2.0 the Borland compiler
had to be at a specific location. I understand that Maiko has made
changes, so please check with the TAPR archive or Maiko's web pages for
the latest info. PC problems have prevented me from doing any further work
on compiling JNOS 2.0.
===========================
Hello All,
I have been able to acquire a copy of Borland C++ 3.1 and have finally
been able to compile JNOS 2.0 using Maiko's original files. However, this
has only been possible when the Borland C++ 3.1 has been placed into the
folder c:\borlandc (as per Maiko's recent instructions).
In previous version of JNOS, I have been able to put the compiler into any
location with any folder name, as long as that folder is in the DOS path,
and the path is also specified in the makefile at the relevant place. With
JNOS 2.0 it only seems to work if the compiler is at c:\borlandc and
nowhere else.
I can only assume that something has been changed in the 2.0 version and
is pointing to c:\borlandc instead of using the path defined in the
makefile.
============================
73 - Peter, G4DJB @ GB7NLY
Please do not reply to my packet address as the GB7NLY BBS will close on 2
Jan 2005. I have no other reachable BBS so I will no longer have packet
access.
Message timed: 13:55 on 2004-Dec-31
Read previous mail | Read next mail
| |
