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

[Joerg Schilling]

In article <Lr5Gm.111824$la3.43298 at attbi_s22>,
John E. Malmberg <wb8tyw at qsl.network> wrote:

>eisner.decus.org is the same as eisner.encompasserve.org and the can be 
>reached as encompasserve.org.  The maintainers of eisner own the 
>encompasserve.org domain, the decus.org domain is owned by the 
>organization formerly know as Decus.
>
>If you will look at my original post, it shows where the ODS5 volume is: 
>usr_ods5:
>
>$ @gnv$gnu:[lib]gnv_setup.com

Thank you, this command worked!

Could you please explain what this does?
The last time I did work occasionally on VMS was 25 years ago and 
as this was not for a long time, I no longer know how to set up search path
and other things that are different from UNIX.

>Note that it is gnv$gnu, not gnu.  The gnu name violates VMS logical 
>name standards for an installed product.  (That fix has been submitted 
>to HP, but I do not know when it will be incorporated)
>

>One of the main features of eisner.encompasserve.org is a moderated 
>notes conferences that is invoked by the command NOTES.
>
>The "PORTING_TO_VMS" conference is not there by default.  It is added 
>with the command "ADD ENTRY PORTING_TO_VMS", or you can use web access 
>that I posted the URL for earlier.

OK

> >>   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.
>
>As I understand it the translation is to replace non-ods2 characters 
>with underscores.

> > Why? This is something that was created to test the features.
>
>Configure makes incorrect assumptions about the build environment on any 
>platform that maintains backwards binary compatibility with older releases.

I am using an own extremely enhanced fork from autoconf-2.13 which is the latest
version that does not depend on bash.


> > What I
> > did see on the VMS account I aquired a week ago looks like something
> > that is very close to a working solution and HP did even claim that
> > on a newer system configure should work now.
>
>I am the one that put the changes into GNV bash that eliminates most of 
>the problems with running configure.  That requires VMS 8.2 at a minimum 
>and the latest GNV kit, or one that has my patches applied.
>
>I am very much aware of what limitations remain.

OK, so I know whom to ask after I did run my first test run.

> >>> -	OpenVMS 7.0 should support a POSIX compliant struct stat.st_ino
> >>> 	but I cannot make this work.
>
>Nope, you need VMS 8.2 as I posted earlier.

OK, eisner seems to have 8.3

>It usually takes me several passes to get the configure script to 
>produce the correct output for VMS.
>
>I had to put back doors in the GNV CC wrapper program that allow me to 
>trick the configure script into coming up with the correct answer for VMS.
>
>Most of these hacks could be eliminated if configure was made to test 
>the functions with the header files in place instead of testing 
>functions with out header files.  It would also shorten the runtime of 
>the configure program, since many of the configure scripts eventually 
>run that tests.  See my previous reply.
>
>GNV is not a perfect UNIX emulation on VMS, it is a work in progress.
>
>I really recommend that you look over the porting_to_vms conference that 
>I posted earlier.  While you may be able to get configure scripts to run 
>with out doing so, it will be harder.

OK, with eisner it looks now very prommising.

-- 
EMail:joerg at schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin
      js at cs.tu-berlin.de		(uni)  
      joerg.schilling at fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/
URL:  http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily