That seems reasonable, so it is now up to you to figure out why configure
is not finding install-sh. Another thing to consider - why not run
configure on your MVS machine for a native build, rather than trying to
run it on Windows for a cross-compile build? If MVS has a reasonably
portable sh im
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Paul Edwards on 2/4/2009 1:44 PM:
> MVS is on the list of recognized platforms:
>>
>> $ ./build-aux/config.sub mvs
>> i370-ibm-mvs
>
> Which particular MVS compiler is that though? One that supports
> Unix extensions or one that only sup
MVS is on the list of recognized platforms:
$ ./build-aux/config.sub mvs
i370-ibm-mvs
Which particular MVS compiler is that though? One that supports
Unix extensions or one that only supports C89? I'm using the latter.
What version of bash are you using, and from where did you get it? I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Paul Edwards on 2/1/2009 7:06 AM:
>>> I can't run configure. The target is the mainframe, not the
>>> compiler I have on my PC.
>>
>> The ./configure script works for cross-compilation cases, if you use the
>> right --build and --host fla
All of the @ characters are designed to be replaced by running the
Makefile produced by the ./configure script. Are you able to run that
script? If not, can you at least post the resulting config.log to show
how far it got?
I can't run configure. The target is the mainframe, not the
compiler
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[please keep the list in the loop; also, adding bug-gnulib, since the
files you are complaining about come from there]
According to Paul Edwards on 1/31/2009 11:01 PM:
>> All of the @ characters are designed to be replaced by running the
>> Makefile p
