On Tue, Mar 4, 2008 at 1:56 AM, John E. Malmberg <[EMAIL PROTECTED]> wrote:
> First I would need to find out what a VPATH build is.
A VPATH build is one where the sources and object files live in
different directories. For example:
mkdir compile
tar zxf /tmp/blah.-1.0.tar.gz
cd compile
../blah
Ralf Wildenhues wrote:
Hello John,
* John E. Malmberg wrote on Mon, Mar 03, 2008 at 07:01:46AM CET:
In tests/testsuite :
VMS can not deal with having a file/directory named testname and
testname.dir in the same directory.
This is because all directories are named .dir, and to be more POSI
Hello John,
* John E. Malmberg wrote on Mon, Mar 03, 2008 at 07:01:46AM CET:
> In tests/testsuite :
>
> VMS can not deal with having a file/directory named testname and
> testname.dir in the same directory.
>
> This is because all directories are named .dir, and to be more POSIX
> friendly, VM
I have TAR passing the pipe test, so I though it would be a good point
to pass the source changes I needed so far.
TODO: I still have to add the vfork/exec/pipe code from the VMS bash
port so that the compression options work.
In lib/alloca.in.h :
VMS needs a definition for the built-in __AL
