On Sun, 6 Feb 2005, Craig A. Berry wrote: > At 7:30 PM -0500 2/4/05, John E. Malmberg wrote: > >Craig A. Berry wrote: > > > >>When GNV gets to the point where we can use Configure rather than > >>configure.com and stop maintaining a separate behemoth configuration > >>script, that's the point where we will need to update support for GNU > >>make.
I modified my local copy of the configure.com to accept a "-Dbuilder=make" so that on the command line I could set the default. The build failed because [.vms]Makefile.in was not found. So I am now falling back to MMK. > Perl has been able to use unix syntax file specification for 10 years > or so. If what you mean is the behavior that results from > DECC$FILENAME_UNIX_REPORT, that's a different matter. This is a > really a problem with other packages not handling file specs reported > in VMS syntax. Perl's tendency is that, when in doubt, convert to > native syntax. This was essential for older CRTL versions that often > did not handle unix syntax fully. But reporintg filenames in VMS > syntax will of course cause trouble for other packages that can't > handle that. So yes, there is work to be done in Perl to make it > only report unix syntax filenames. It apparently a case where the perl script output is expected to be used by an application that does not understand VMS file specifications. I am going by second hand knowledge here. When I actually try to build one of these products, I may find out more information. > On my 7.3-1 system: > > $ search sys$library:decc$crtl.exe lstat > %SEARCH-I-NOMATCHES, no strings matched Wrong image file, try: $ search sys$share:decc$shr lstat/format=nonull > I suppose it could be a macro that references decc$stat, though I see > no evidence of that in the header. > > >Until 8.2 + future RMS SYMLINKS ECO kit, it behaves the same as stat(), and > >if support for lstat() is not configured, Perl already knows to substitute > >stat(). And there is no plans to backport these changes to earlier VMS > >versions or to implement them on VAX. > > We'll have to explicitly test for lstat in configure.com, including > some sort of test that it not only is present in the CRTL but > actually works, i.e., has the underlying OS support. The 8.2 CRTL will do the right thing even if the actual SYMLINK support is missing, so just a test for 64 bit OpenVMS 8.2 should be all that is needed for Configure.com. The only thing that would be significant to test for is if a symbolic link can be created. I have not looked at what Perl does in that case that is different than if the symlink() routine is missing. No need to test for earlier versions, the routines will just return the same results as if they did not find a symlink for the argument that was called. -John [EMAIL PROTECTED] [EMAIL PROTECTED] Personal Opinion Only
