public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Toon Moene <toon@moene.indiv.nluug.nl>
To: egcs@cygnus.com
Subject: egcs-971207 on m68k-next-nextstep3
Date: Tue, 09 Dec 1997 12:15:00 -0000	[thread overview]
Message-ID: <9712092012.AA19241@moene.indiv.nluug.nl> (raw)

1. I had to remove a second #include <tree.h> from
   .../config/m68k/m68k.c

2. My suggestion to add /NextDeveloper/Headers to the
   list of directories to be fixinclude'd is bogus:

% ls -l /usr/include
lrwxrwxrwx  1 root          24 Aug 29  1996 /usr/include ->  
../NextDeveloper/Headers@

   So fixinclude is now doing the same work twice ;-)

More results tomorrow ...

Cheers,
Toon.

                 reply	other threads:[~1997-12-09 12:15 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=9712092012.AA19241@moene.indiv.nluug.nl \
    --to=toon@moene.indiv.nluug.nl \
    --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).