public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "John Huddleston" <jhudd@itc.nrcs.usda.gov>
To: <earnie_boyd@yahoo.com>
Cc: <cygwin@sourceware.cygnus.com>
Subject: Re: Imakefile problem
Date: Fri, 10 Mar 2000 06:59:00 -0000	[thread overview]
Message-ID: <013001bf8aa1$0399ebd0$6d298dc7@itc.nrcs.usda.gov> (raw)
In-Reply-To: <20000310144926.2242.qmail@web108.yahoomail.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 2212 bytes --]

Pretty much.  I built the GRASS5 system which had hundreds of
Imakefiles.   When there were cases of long lines that had the
backslash '\' in them to continue on the next line, the Carriage
Returns always caused the problem.   I wrote a simple C program
(yes I could have used tr) to remove CR's from the end of lines.
It always fixed the problem.

John

----- Original Message -----
From: Earnie Boyd <earnie_boyd@yahoo.com>
To: John Huddleston <jhudd@itc.nrcs.usda.gov>; Bobák_Csaba
<bobak@ekf.deltav.hu>
Cc: <cygwin@sourceware.cygnus.com>
Sent: Friday, March 10, 2000 7:49 AM
Subject: Re: Imakefile problem


--- John Huddleston <jhudd@itc.nrcs.usda.gov> wrote:
> 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.
>

Are you sure?  It appears to be a quoting problem to me.  Is the version of
imake that Bobák is using a Cygwin or Non-Cygwin program.  If it Non-Cygwin
then it is definately a quoting problem and the fix would be to add two more
\"\" to the Makefile.

Earnie.

> 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
>
>
__________________________________________________
Do You Yahoo!?
Talk to your friends online with Yahoo! Messenger.
http://im.yahoo.com


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

  reply	other threads:[~2000-03-10  6:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-03-10  6:49 Earnie Boyd
2000-03-10  6:59 ` John Huddleston [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-03-09 22:37 Bobák Csaba
2000-03-10  5:58 ` 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='013001bf8aa1$0399ebd0$6d298dc7@itc.nrcs.usda.gov' \
    --to=jhudd@itc.nrcs.usda.gov \
    --cc=cygwin@sourceware.cygnus.com \
    --cc=earnie_boyd@yahoo.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).