I have all the compiles running.

Now I am working on linking the images.

Then the real FUN begins - debugging the code to get a working version.

Nice to see progress.

Yes, I know there is A LOT to do yet, but at least it is such that there is progress and I am not staring at a blank wall.

Bill.

Ok, moving this forward.

I should have all compiles done, with a few exceptions. The limiting issues are being caused by our pushing the envelope a bit further than other folks using the GNV Unix portability environment build facility further than others. We found some issues in a key component of the porting facility - the wrapper around the C and C++ compiler and LINKER.

We have gotten about 95%+ of the modules to compile. And are now looking at the final few and seeing how we can get past the obstacles due to the issue with the tools.

We have not made any progress on the Perl modifications necessary to properly support GNV and the build environment other than to do some evaluation and also then do some preliminary modifications to isolated modules in the Samba 4.3.1 build to allow the bypassing of the updates so the builds will complete.

The Samba build depends upon Python, WAF, Perl PIDL, C, C++, Heimdal(Kerberos) and other tools and facilities.

We will update this was we move forward.

Bill.

After getting Python running nicely with GNV and OpenVMS with our new subprocess.py module we progressed on in the Samba 4.3.1 port to OpenVMS.

That proceeded nicely until I came to a point where it became obvious that the Perl implementation on OpenVMS was not supporting GNV properly. I was in the middle of trying to build the Heimdal Kerberos implementation (a builtin of Samba) rather than use the system installed Kerberos. That path was being taken as the current release of Kerberos on OpenVMS is TOO OLD!!!

SO, I then started to look at the build for Kerberos - started to work on that. ./configure went smoothly. The build started and then Perl popped up again - a bit later than in Heimdal - CUTE! NOT!

So I am not evaluating how to implement GNV support in Perl. I have a Perl build installed on one of my development RX2600s and so should be able to get some initial work done on it this week. I would like to have the fixes in place by the end of the month. That may not happen - too much going on with the South Carolina FIRST Tech Challenge State Robotics Championship.

Anyway, making progress - and for more than just myself.

Bill.

Ok, the initial release has been posted to http://sourceforge.net/projects/vms-por ... S_Python/.

This release is a total new implementation from the prior version. Testing has been done against the Samba 4.3.1 WAF build environment. ONLY ONE edit was necessary to allow execution of the configure process - to force the file type of the result of a LINK to not have the ".EXE" file type.

Yes there are other issues I have fighting with getting as many of the errors out of the configure process but they have nothing to do with the execution of the Python subprocess module.

For instance, there is a test of the mmap() function. It used fork() in the classically thought of way of duplicating the process (and executable) - which OpenVMS does not support, currently. It was a minor edit to create a mechanism to use vfork()/execl() to create a child process and then additional minor modifications to have the execution "detect" whether it is running as a parent or as a child.

So, now I am attacking the issue of using the Kerberos already installed on my OpenVMS systems as part of the build of Samba - more investigation and tweaking of the configure environment.

Bill.

Have gotten the configure script to run to the point of attempting to compile the summary.c code at the end of the configure process - it fails but that is not unexpected.

It gets there! That is what is important. Farther than at any time in the past on this project so that makes me feel good. A lot to do still. Boy, a whole heck of a lot to do.

Also some improvements on the subprocess.py module. Need to do some final testing and clean up and implement a could other features that I have bypassed for this project.

Bill.