From: Jim Wilson <wilson@cygnus.com>
To: mrs@wrs.com (Mike Stump)
Cc: egcs@cygnus.com
Subject: Re: problem
Date: Fri, 31 Oct 1997 11:20:00 -0000 [thread overview]
Message-ID: <199710311920.LAA05386@cygnus.com> (raw)
In-Reply-To: <199710310304.TAA20396@kankakee.wrs.com>
$(srcdir)/f/intdoc.texi: f/intdoc.c f/intdoc.in f/ansify.c f/intrin.def f/intrin.h
$(HOST_CC) $(HOST_CFLAGS) $(HOST_LDFLAGS) \
`echo $(srcdir)/f/ansify.c | sed 's,^\./,,'` -o f/ansify
requires that CC be an ANSI compiler, this didn't happen to be the
case with my /bin/cc.
The snapshots intentionally include intdoc.texi so as to avoid this problem.
You should never need to rebuild it, and hence you should not be running into
this problem. Perhaps there is a problem with timestamps your source tree?
Jim
next prev parent reply other threads:[~1997-10-31 11:20 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-10-30 19:04 problem Mike Stump
1997-10-30 19:16 ` problem Joe Buck
1997-10-31 11:20 ` Jim Wilson [this message]
1997-10-31 12:08 problem Mike Stump
1999-09-01 16:22 Problem Mcfall, Troy D
1999-09-01 22:04 ` Problem Jeffrey A Law
1999-09-30 18:02 ` Problem Jeffrey A Law
1999-09-30 18:02 ` Problem Mcfall, Troy D
1999-10-09 13:49 problem Nathan A. Feger
1999-10-31 23:35 ` problem Nathan A. Feger
1999-10-10 9:47 problem Florin Iucha
1999-10-31 23:35 ` problem Florin Iucha
2001-10-19 8:14 problem Nurse, Brian
2001-10-19 8:37 ` problem Phil Edwards
2001-12-18 23:40 problem GTFSTBK
[not found] <616BE6A276E3714788D2AC35C40CD18D29DBCF@whale.softwire.co.uk>
2001-12-18 23:54 ` problem Rupert Wood
2001-12-19 0:04 ` problem Russ Allbery
2001-12-19 8:47 ` problem Tim Prince
[not found] <616BE6A276E3714788D2AC35C40CD18D29DBF7@whale.softwire.co.uk>
2001-12-19 1:42 ` problem Rupert Wood
2001-12-19 3:14 problem dewar
2001-12-19 9:48 problem GTFSTBK
2005-02-14 22:19 problem Virender Kashyap
2005-02-15 21:27 ` problem James E Wilson
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=199710311920.LAA05386@cygnus.com \
--to=wilson@cygnus.com \
--cc=egcs@cygnus.com \
--cc=mrs@wrs.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).