On Tuesday 20 December 2011 02:38:29 David Cleaver wrote:
> 
> On 12/19/2011 2:46 AM, Cactus wrote:
> >
> > THe CRLF vs LF issue is a nuisance but I don't really know what can be done
> > about it.
> >
> 
> I found a way to update the configure file so that if it encounters CRLF line 
> endings in the config.in file, it will strip out the CR and then proceed 
> normally.  Would this be an acceptable solution so that it doesn't matter 
> what 
> svn client was used for the download?
> 
> I am including the diff between the original 'configure' and the new 
> 'configure'.  This diff is based off of svn 3759.
> 
> $ diff configure configure.new
> 29942c29942,29943
> < /^[\t ]*#[\t ]*(define|undef)[\t ]+$ac_word_re([\t (]|\$)/ {
> ---
>  > /^[\t ]*#[\t ]*(define|undef)[\t ]+$ac_word_re([\t (]|\r\$|\$)/ {
>  >   sub(/\r\$/,"")
> 32965c32966,32967
> < /^[\t ]*#[\t ]*(define|undef)[\t ]+$ac_word_re([\t (]|\$)/ {
> ---
>  > /^[\t ]*#[\t ]*(define|undef)[\t ]+$ac_word_re([\t (]|\r\$|\$)/ {
>  >   sub(/\r\$/,"")
> 35994c35996,35997
> < /^[\t ]*#[\t ]*(define|undef)[\t ]+$ac_word_re([\t (]|\$)/ {
> ---
>  > /^[\t ]*#[\t ]*(define|undef)[\t ]+$ac_word_re([\t (]|\r\$|\$)/ {
>  >   sub(/\r\$/,"")
> 
> I would be interested to know if this works for others in their environments.
> 
> -David C.
> 
> 

thanks , but configure is a machine generated file from configure.in and 
autotools , so this would 
not be very useful , I think autotools will fix it soon , in the next mpir we 
will be upgrading to the latest 
autotools anyway. the script regen in the develop directory will do this sort 
sort of correction and also fill
in missing files etc

Thanks
Jason

-- 
You received this message because you are subscribed to the Google Groups 
"mpir-devel" group.
To post to this group, send email to mpir-devel@googlegroups.com.
To unsubscribe from this group, send email to 
mpir-devel+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/mpir-devel?hl=en.

Reply via email to