Re: problem with GNU make configure
> Date: Fri, 3 Aug 2007 14:52:53 -0700 (PDT) > From: [EMAIL PROTECTED] > > I am trying to configure GNU make from cygwin and ./configure doesn't run. > I have attached the cygwin console capture with the error. I see no attachments. ___ Bug-make mailing list Bug-make@gnu.org http://lists.gnu.org/mailman/listinfo/bug-make
Re: problem with GNU make configure
> Date: Fri, 3 Aug 2007 14:55:15 -0700 (PDT) > From: [EMAIL PROTECTED] > > oops, here is the attached console capture It's much better to send this as plain text (you can capture it with `tee' or even by copying and pasting the contents into your mailer). My crystal ball says that somehow the configure script god DOS-style CR-LF line endings, which make Cygwin Bash barf. ___ Bug-make mailing list Bug-make@gnu.org http://lists.gnu.org/mailman/listinfo/bug-make
Re: problem with GNU make configure
On Sat, Aug 04, 2007 at 01:08:54AM +0300, Eli Zaretskii wrote: >> Date: Fri, 3 Aug 2007 14:55:15 -0700 (PDT) >> From: [EMAIL PROTECTED] >> >> oops, here is the attached console capture > >It's much better to send this as plain text (you can capture it with >`tee' or even by copying and pasting the contents into your mailer). > >My crystal ball says that somehow the configure script god DOS-style >CR-LF line endings, which make Cygwin Bash barf. That's right. That is exactly the problem. Use u2d to fix it. This is not a GNU make problem. ___ Bug-make mailing list Bug-make@gnu.org http://lists.gnu.org/mailman/listinfo/bug-make
RE: problem with GNU make configure
On 04 August 2007 00:08, Christopher Faylor wrote: > On Sat, Aug 04, 2007 at 01:08:54AM +0300, Eli Zaretskii wrote: >>> Date: Fri, 3 Aug 2007 14:55:15 -0700 (PDT) >>> From: [EMAIL PROTECTED] >>> >>> oops, here is the attached console capture >> >> It's much better to send this as plain text (you can capture it with >> `tee' or even by copying and pasting the contents into your mailer). >> >> My crystal ball says that somehow the configure script god DOS-style >> CR-LF line endings, which make Cygwin Bash barf. > > That's right. That is exactly the problem. Use u2d to fix it. You mean 'd2u'. > This is not a GNU make problem. Nik, did you use winzip or some similar windows gui to unpack the make sources? If you did, don't, they often 'helpfully' convert lineendings; use the cygwin command-line "tar". The other possibility is that you've installed cygwin with dos-mode line endings when you used setup.exe. That can be switched back by rerunning setup.exe. If you need more help, come and post over on the cygwin mailing list and we'll sort it out there. See the list page for archive, (un)subscribe and posting details. http://cygwin.com/cygwin/lists.html#cygwin cheers, DaveK -- Can't think of a witty .sigline today ___ Bug-make mailing list Bug-make@gnu.org http://lists.gnu.org/mailman/listinfo/bug-make
