[Xitami] Building Xitami (OS/2)

Brian {Hamilton Kelly} xitami@lists.xitami.org
Tue, 4 May 2004 08:21:52 +0100 (BST)


In message <20040503142708.V85@warpix.org> John Poltorak writes:
> On Mon, May 03, 2004 at 02:23:50PM +0200, Pieter Hintjens wrote:

> As I said previously running 'c *.c' results in the system being unable to 
> find the file specified.
> 
> > I don't recall whether OS/2 
> > allows wildcards like 'c *.c'.
> 
> Yes, it does.

No it doesn't; OS/2 expands wildcards within each application, not within
the shell.  So the parameter "*.c" would be passed over intact to the
c.cmd (is this a batch file, or is it a proper REXX command procedure?)
and this in turn (presumably) will pass it on to gcc --- which doesn't
know how to expand "*.c".

[If c.cmd *is* written in REXX, rather than just a series of OS/2
commands, then it would be easy to rewrite so as to expand *.c]

> > > Do I need a c.conf? I don't have one, but it is mentioned in c.conf.
> > 
> > No, you don't need this.
> 
> Where would I find one anyway? It may be somewhere that I set a number of 
> variables.

I still can't get over the concept that a file might be required, is
mentioned in a particular file, but that file doesn't exist!  I presume
one of the instances of "c.conf" in that line quoted above is actually
something else?

-- 
   fix (vb.): 1. to paper over, obscure, hide from public view; 2. to
   work around, in a way that produces unintended consequences that are
   worse than the original problem.  Usage: "Windows ME fixes many of the
   shortcomings of Windows 98 SE".