From: Dan Harkless <cygwin-list21@harkless.org>
To: cygwin@cygwin.com
Subject: Re: Another confusing error from someone else's Cygwin setup
Date: Mon, 26 Jun 2023 17:01:28 -0700 [thread overview]
Message-ID: <6df1585d-1215-2052-c728-a5367ceff5b2@harkless.org> (raw)
In-Reply-To: <0e66e09e-f921-2bf0-7c6f-126dfb73a4e4@harkless.org>
On 6/26/2023 4:58 PM, Dan Harkless via Cygwin wrote:
> On 6/26/2023 4:35 PM, David Karr via Cygwin wrote:
>
> > > He was getting a weird error on line 3, just saying this:
> > > ---------------------
> > > ...: line 3: syntax error near unexpected token `$'{\r''
> > > ...: line 3: `main() {
> > > ---------------
>
> Apologies, I don't remember your other report, but this one kind of
> sounds like an end-of-line characters problem. Try installing
> (Cygwin's) dos2unix, if you don't already have it, then try running
> dos2unix on the script. If it still doesn't work, try then running
> unix2dos. If you have binutils installed, you can also use the 'file'
> command for a quick report on whether files have lines terminated with
> CR (macOS), CRLF (Windows), or LF (UNIX/Linux). 'file' might not
> realize when you have files with inconsistent line-terminators, though.
And I forgot dos2unix also includes a 'mac2unix' command these days
(though not a mac2dos), so maybe try that first.
--
Dan Harkless
http://harkless.org/dan/
next prev parent reply other threads:[~2023-06-27 0:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-26 23:35 David Karr
2023-06-26 23:58 ` Dan Harkless
2023-06-27 0:01 ` Dan Harkless [this message]
2023-06-27 2:08 ` Mike Gran
2023-06-27 17:52 ` David Karr
2023-07-05 19:25 ` Andrey Repin
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=6df1585d-1215-2052-c728-a5367ceff5b2@harkless.org \
--to=cygwin-list21@harkless.org \
--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).