From: "John Huddleston" <jhudd@itc.nrcs.usda.gov>
To: Bobák Csaba <bobak@ekf.deltav.hu>
Cc: <cygwin@sourceware.cygnus.com>
Subject: Re: Imakefile problem
Date: Fri, 10 Mar 2000 05:58:00 -0000 [thread overview]
Message-ID: <008d01bf8a98$778d3c30$6d298dc7@itc.nrcs.usda.gov> (raw)
In-Reply-To: <38C89808.AAA29CA8@ekf.deltav.hu>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 975 bytes --]
Make sure that there are no CR (carriage returns) in the file.
Also, make sure you have MAKE_MODE=unix set in your
environment. That should take care of it.
John Huddleston
----- Original Message -----
From: Bobák Csaba <bobak@ekf.deltav.hu>
To: <cygwin@sourceware.cygnus.com>
Sent: Thursday, March 09, 2000 11:36 PM
Subject: Imakefile problem
> Hello all,
>
> (It's a bit off-topic, I just don't know where to ask, sorry)
> I'm building a large-scaled UNIX application on cygwin-b20, no
> snapshots. I have problems with Imakefiles that contain a line like
> #define DEF2=\"$(DEF1)\"
> Imake complains about unterminated character strings (and some errors
> caused by that, like unfinished #ifdef).
> Would anyone give me a hand? Thank you.
>
> Csaba
>
>
> --
> Want to unsubscribe from this list?
> Send a message to cygwin-unsubscribe@sourceware.cygnus.com
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
next prev parent reply other threads:[~2000-03-10 5:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-09 22:37 Bobák Csaba
2000-03-10 5:58 ` John Huddleston [this message]
2000-03-10 6:49 Earnie Boyd
2000-03-10 6:59 ` John Huddleston
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='008d01bf8a98$778d3c30$6d298dc7@itc.nrcs.usda.gov' \
--to=jhudd@itc.nrcs.usda.gov \
--cc=bobak@ekf.deltav.hu \
--cc=cygwin@sourceware.cygnus.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).