> At 03:14 PM 4/20/00 -0600, William Atkinson wrote:
> >Yes, it is definitely a conflict in header files. I talked with the vms guy
> >here and it turns out that we are comitted to keeping them so that we can
> >generate product versions that look like they came from older vms releases.
>
> Then he's doing things the wrong way, as you've found, as it crocks the
> current version's build. There are better ways to do it. (Keeping an old
> Alpha or VAX in the cluster's the best one... :) But it sounds like you're
> stuck with things the way they are.
So's the VMS guy... that'd be me. I complained long and hard about it
and was overrulled. Anyway, enough politics...
I hadn't seen this sort of conflict before -- for our "problem" we usually
list SYS$LIBRARY as an /INCLUDE directive. If I want to write "real" code
I've not had this problem.
I admit to being ignorant on the Perl build procedure -- does it list
SYS$LIBRARY and/or POSIX$INCLUDE as /INCLUDE directories?
--
Eric F. Richards
[EMAIL PROTECTED]
"The weird part is that I can feel productive even when I'm doomed."
- Dilbert
