On 11/11/10 7:31 PM, David Billinghurst wrote:
> David Billinghurst wrote:
>> Another data point. My normal build process on windows is a
>> cygwin/msys hybrid. This worked for me a long time ago and I have
>> never changed
>>
>> On cygwin:
>> cvs update -dp
>> copy the maxima tree to a build location
>> "sh bootstrap' in the build tree
>>
>> On msys, in the build tree:
>> ./configure
>> make
>> make check
>>
>> This still works. However, if run "sh bootstrap" under MSYS then I
>> get sed errors when I run configure, suggesting that one of the files
>> generated by the MSYS bootstrap process is broken. I will
>> investigate further.
>>
> There is a problem with the MSYS generated configure script. i can
> reproduce the sed errors by copying this one file into a directory
> tree with a cygwin bootstrap.
Thanks for testing. This seems to indicate that autoconf on MSYS is
not working the same as autoconf on cygwin. Are they the same version?
What is the difference between the generated configure script between
MSYS and cygwin?
Finally, can you try replacing the obvious line in configure.in with the
following line:
default_sharedirs=`find share -type d | sort | egrep -v 'share$|CVS|/fortran' | sed 's;share/\(.*\);"\1";' | tr '\n' ' '`
(That should all be on one line.) Try to bootstrap again and see if
that works.
This would be very good too if the person(s) who actually does the
Windows binaries could test this.
Ray