All -
the make rpm command is broken in the trunk. It appears that not all the
source files are being zipped up before being copied to the rpm subdir.
This also means that there will be missing files in a zip to tar
archive. I am tracing this down but if you have recently added files to
the
It looks like the include statement for the message number header file
has been somehow removed from the mix. I am getting undefined error
messages all over the place like this.
In file included from ./interpreter/runtime/RexxCore.h:273,
from
Was the include file somehow generated as an empty file?
Rick
On Tue, Apr 27, 2010 at 2:47 PM, David Ashley david.ashley@gmail.comwrote:
It looks like the include statement for the message number header file has
been somehow removed from the mix. I am getting undefined error messages all
On Tue, Apr 27, 2010 at 11:47 AM, David Ashley
david.ashley@gmail.comwrote:
It looks like the include statement for the message number header file has
been somehow removed from the mix. I am getting undefined error messages all
over the place like this.
What happens is, if you do a make
On Tue, Apr 27, 2010 at 12:07 PM, Mark Miesfeld miesf...@gmail.com wrote:
On Tue, Apr 27, 2010 at 11:47 AM, David Ashley david.ashley@gmail.com
wrote:
It looks like the include statement for the message number header file has
been somehow removed from the mix. I am getting undefined error
On 26 April 2010 03:51, Mike Cowlishaw m...@speleotrove.com wrote:
Parsing (oo)Rexx is hard. The reason for this is that a
symbol can be a symbol or a keyword, depending on the
context. Have a look at the following example: [snip]
Yes, that's correct (NetRexx makes it a bit more regular, in
