public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Rashi Singhal <singhal.rashi@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Cygwin 1.7-58 with windows 2008
Date: Mon, 28 Mar 2016 11:06:00 -0000	[thread overview]
Message-ID: <CAPCR6Q0gCwVJ0HvK_R_9QkbNac0i5eEngKd5Sdw4fc8G2DKi0w@mail.gmail.com> (raw)
In-Reply-To: <1698009033.20160328134228@yandex.ru>

Hi,

I am not getting what is wrong in my mail.

I replayed in the last conversation of the message.


On Mon, Mar 28, 2016 at 4:12 PM, Andrey Repin <anrdaemon@yandex.ru> wrote:
> Greetings, Rashi Singhal!
>
>> Thanks a lot for help.
>> Now my compilation went down but again stopped at some point.Its
>> halting in awk command after warning
>
>> config.status: WARNING:  '/oss/src/winsup/Makefile.in' seems to ignore
>> the --datarootdir setting
>
>> awk: ./confXqR7rV/subs.awk:1: BEGIN {\r
>> awk: ./confXqR7rV/subs.awk:1:        ^ backslash not last character on line
>> config.status: error: could not create Makefile
>
>> I have set SHELLOPTS= igncr ,still its give error .
>
>> Even I tried command dos2unix on configure files and awk.
>
>> Please give some clue what is going wrong here.
>
> d2u
> Also, please don't top-post.
>
>
> --
> With best regards,
> Andrey Repin
> Monday, March 28, 2016 13:42:10
>
> Sorry for my terrible english...
>

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

  reply	other threads:[~2016-03-28 11:06 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-17  8:44 Rashi Singhal
2016-02-17  9:09 ` Marco Atzeri
2016-02-22  9:50 ` Rashi Singhal
2016-02-22 11:21   ` Marco Atzeri
2016-02-23  3:34   ` Rashi Singhal
2016-02-23 14:01     ` Marco Atzeri
2016-03-04 16:40     ` Rashi Singhal
2016-03-09  8:00       ` Rashi Singhal
2016-03-09  8:16         ` Marco Atzeri
     [not found]         ` <CAPCR6Q2GdXd=EF7iAdP+xYT7UomLefLKgDm=be0oD=Wh64T_-g@mail.gmail.com>
2016-03-11  2:40           ` Rashi Singhal
2016-03-11  6:38             ` Mark Geisert
2016-03-17 11:19             ` Rashi Singhal
2016-03-17 11:47               ` Marco Atzeri
2016-03-18 16:15               ` Peter A. Castro
     [not found]                 ` <CAPCR6Q32VQeQLLjOC6t5UNs-AVtHYC_Er1ETdZHtYifbD6j3rA@mail.gmail.com>
     [not found]                   ` <alpine.LNX.2.00.1603231447150.6583@ming.fruitbat.org>
2016-03-24  4:20                     ` Fwd: " Rashi Singhal
2016-03-24 19:29                       ` Warren Young
2016-03-24 19:36                         ` Warren Young
2016-03-25  5:38                       ` Fwd: " Mark Geisert
2016-03-28  9:08                       ` Rashi Singhal
2016-03-28 10:50                         ` Andrey Repin
2016-03-28 11:06                           ` Rashi Singhal [this message]
2016-03-28 14:30                             ` Erik Soderquist
2016-03-29  2:47                       ` Rashi Singhal
  -- strict thread matches above, loose matches on Subject: below --
2016-02-17  5:53 Rashi Singhal
2016-02-17  6:50 ` Larry Hall (Cygwin)

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAPCR6Q0gCwVJ0HvK_R_9QkbNac0i5eEngKd5Sdw4fc8G2DKi0w@mail.gmail.com \
    --to=singhal.rashi@gmail.com \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).