public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Toon Moene <toon@moene.indiv.nluug.nl>
To: law@cygnus.com
Cc: egcs@cygnus.com
Subject: egcs-971127 on m68k-next-nextstep3; Status Report
Date: Sun, 30 Nov 1997 08:38:00 -0000	[thread overview]
Message-ID: <9711301456.AA14740@moene.indiv.nluug.nl> (raw)

Hi,

I managed to build all of egcs-971127 by using a trick to get the  
fixinclude'd include files in the right directory for gcc to find  
them.

I copied all of .../gcc/include/ansi/*.h and  
.../gcc/include/bsd/*.h to .../gcc/include, with the exception of  
ansi/stdio.h, because otherwise I get the following failure during  
the build of the Objective C compiler:

./xgcc -B./  -DIN_GCC    -O2 -g -O2 -I./include  -I. -I. -I./config \
-c ./objc/misc.c -o objc/misc.o
In file included from objc/runtime.h:31,
                 from ./objc/misc.c:30:
include/stdio.h:302: conflicting types for `_flsbuf'
include/stdio.h:153: previous declaration of `_flsbuf'
make[2]: *** [objc/misc.o] Error 1

which is interesting, because there only are 300 lines in stdio.h :-(

This is line 153:

   153                          extern int _flsbuf(unsigned char c,  
FILE *iop);

Anyway, because dejagnu doesn't build on my system, the only  
checking I did was to run c-torture-1.45 (same results as for  
egcs-971105 and much better than gcc-2.7.2.3).

I also ran my own batch of Fortran programs on it (around 200,000  
lines in 1,300 routines spread over half a dozen executables), which  
completed without problems.

I hope the release is progressing on schedule.

Regards,
Toon.

             reply	other threads:[~1997-11-30  8:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-11-30  8:38 Toon Moene [this message]
1997-11-30 14:29 ` Jeffrey A Law
1997-12-02 16:29   ` egcs-971201 " Toon Moene
1997-12-02 18:18     ` 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=9711301456.AA14740@moene.indiv.nluug.nl \
    --to=toon@moene.indiv.nluug.nl \
    --cc=egcs@cygnus.com \
    --cc=law@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).