Damnit I am still not getting anything in config.h. I must be doing something wrong. I'm going to let Jason fix this. Perhaps dos2unix isn't doing the job.
I have to go out for a few hours. Bill. 2009/3/5 Bill Hart <goodwillh...@googlemail.com>: > It's not clear to me why WinSCP didn't change the line endings. It > probably didn't identify the files as text files. > > Bill. > > 2009/3/5 Bill Hart <goodwillh...@googlemail.com>: > - Show quoted text - >> Should do the same for all files in /mpn/x86_64/core2, >> /mpn/x86_64/amd64 and /mpn/x86_64/amd64/k10 >> >> It's just a matter of running dos2unix *.as in each dir I think. >> >> Bill. >> >> 2009/3/5 <ja...@njkfrudils.plus.com>: >>> >>> On Thursday 05 March 2009 17:37:31 Cactus wrote: >>>> On Mar 5, 5:37 pm, ja...@njkfrudils.plus.com wrote: >>>> > must be Brian script , they are all full of "\r" >>>> > which of course means the matching name is mpn_name\r not mpn_name >>>> > removing the "\r" is easy on all files, but we will probably hit the >>>> > problem again , and/or I can put a >>>> > tr -d "\r" >>>> > to delete all "\r" in that specific piece of configure >>>> > We could hit the problem in other places!!! >>>> >>>> Only because you got me to run it on Windows. My guess is that it >>>> would produce the right line endings if the Python code was run on >>>> Linux >>>> >>> >>> Great , if it only those few that Bill asked you to convert , then I'll >>> delete >>> the \r and leave the configure script alone >>> - Show quoted text - >> - Show quoted text - >>> >>>> Brian >>>> >>>> >>> >>> >>> >>> >>> >> > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
