> What would help a lot with open source porting in general would be having
a sufficiently robust GNV package with all the utilities a Configure script
is likely to need and a cc command that is compatible with what unixy
packages expect (regardless of what compiler that cc command invokes).
Curiously this comment on configure brings me back to the original reason
that I subscribed to this mailing list, which is to complain that autoconf
now requires Perl and features/capabilities that are (at least were) not
available/not working on Perl for VMS (vfork/exec vice lib$spawn, separate
std{err,out}redirection, really long command lines, etc.) I solved this
problem by doing a sort of cross-autoconf from Linux using my VMS specific
autoconf macros. Until this gets fixed there's a bit of a roadblock in the
way.
|
