From: Jeffrey A Law <law@cygnus.com>
To: andrewc@rosemail.rose.hp.com
Cc: egcs@cygnus.com
Subject: Re: fixincludes problem
Date: Sat, 10 Jan 1998 22:02:00 -0000 [thread overview]
Message-ID: <4592.884498505@hurl.cygnus.com> (raw)
In-Reply-To: <199801100040.AA025882840@typhoon.rose.hp.com>
In message < 199801100040.AA025882840@typhoon.rose.hp.com >you write:
> Could somebody tell me how to disable fixincludes from running
> in certain situations. Here's the scenarion where I have problems
Set FIXINCLUDES to "Makefile.in" in the Makefile.
However, I don't recommend it -- we should instaed figure out why your
include files are trashed and fix that problem instead.
fixincludes is vital to the proper operation of gcc.
jeff
next prev parent reply other threads:[~1998-01-10 22:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-01-09 16:41 Andrew Crabtree
1998-01-10 22:02 ` Jeffrey A Law [this message]
1998-01-10 23:23 ` Andrew Crabtree
1998-01-12 11:39 ` Jeffrey A Law
1998-01-12 20:31 ` Andrew Crabtree
1998-01-12 22:13 ` Jeffrey A Law
1998-01-13 18:59 ` Andrew Crabtree
1998-01-14 4:17 ` Jeffrey A Law
1998-01-15 16:30 ` Andrew Crabtree
1998-01-14 23:17 ` Jeffrey A Law
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=4592.884498505@hurl.cygnus.com \
--to=law@cygnus.com \
--cc=andrewc@rosemail.rose.hp.com \
--cc=egcs@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).