Note: I think I only get mail on the vmsperl@perl.org list. Nicholas Clark wrote: > On Mon, Nov 29, 2004 at 01:58:52PM -0600, Craig Berry wrote: > > I'm not sure. I was trying to keep Config's AUTOLOAD as simple as possible. > Then again, using %INC shouldn't be that hard. > > For the Unix Makefile I hit the same problem (with the POD scripts) and > the solution I found was to change the -I on the command line from a > relative to an absolute path. Is that viable with the VMS MMS file? Or have > I missed some VMS specific subtilty? A VMS specific method would be to have a logical name that equated to a search list. $define foobar foo:[dir1],bar:[dir2] You can have quite a few directories on the list, and they would show up in UNIX syntax as all being in the same directory: foobar/xxxxx.h My preference in doing VMS builds of application is to use the search list feature of logical names to isolate the source from the resulting binaries and intermediate files. For example: Dist_root:[*...] is a source directory tree that the build procedure does not have privilege to modify. local_root:[*...] is the directory with locally modified source files for testing patches, etc. DEFINE BUILD_ROOT local_root:,dist_root: Set default BUILD_ROOT:[000000] ! Or other base directory. Now VMS will automatically look in the local_root: directory tree first for a file, and if it is not found, will look in dist_root: directory tree. New files being created will be put in the LOCAL_ROOT: tree. This does not work if the build procedure is expecting to actually modify files from the original distribution in place. Perl at the last time I attempted a build on VMS could not use such a search list. FYI: It looks like building SAMBA Version 4 on VMS will require using PERL to do the configuration phase. -John wb8tyw@qsl.net Personal Opinion OnlyThread Previous | Thread Next