[Info-vax] Looking into C-include files on VMS

[Steven Schweda]

Joerg Schilling wrote:

> I am currently trying to make compiling cdrtools a bit more automated.

   More automated how?  More than what's available here?:

      http://antinode.info/dec/sw/cdrtools.html

> There are several problems:

   How many haven't been solved already?

> -	The filesystem only supports one dot "." in filenames which would
> 	require modifications in "configure"

   Trying to force-fit a UNIX-like "configure" script onto a
VMS system seems to me to be the wrong way to do this job.
Which is why I did it differently.  UnZip and VMSTAR both
adjust file names as needed for an ODS2 file system.  My VMS
builders seem to cope, so far as I know.

> -	OpenVMS 7.0 should support a POSIX compliant struct stat.st_ino
> 	but I cannot make this work.

   What doesn't work?  What did you try?  Look for
__USING_STD_STAT in my code changes.

> 	**********************
> -	I cannot see the ful content of the system include files.
> 	Could someone help me with hints on how to do this?

   They can be extracted from the text library, if that hasn't
been done already.  I think that it's not done automatically
now, though it once was.  I should have a procedure somewhere
to do it.

> I am currntly trying to compile "smake" and use a static hand made
> configuration that was created by Mr. Heuser but I need to find a way to
> run commands via bash. What is the best way to do this? THere seems to be no
> fork() but vfork(). Will vfork()/exec() work?

   Don't those static, hand-made configuration files handle
this?

   I haven't published a kit since a59, and I still need (and
intend) to get the "find" code to work on VMS, but otherwise,
I'm not aware of significant problems with what I've done.
But I'm always open to a good complaint.

   Does this wheel really need re-invention?