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-980129 on m68k-next-nextstep3: toplev.c:196: conflicting typesfor abort
Date: Fri, 30 Jan 1998 03:27:00 -0000	[thread overview]
Message-ID: <9801301125.AA16155@moene.indiv.nluug.nl> (raw)

On m68k-next-nextstep3, the newest snapshot of egcs doesn't build -  
it dies with

stage1/xgcc -Bstage1/  -DIN_GCC    -O2 -g  -DHAVE_CONFIG_H     -I.  
-I. -I./config  \
  -DTARGET_NAME=\"m68k-next-nextstep3\" \
  -c `echo ./toplev.c | sed 's,^\./,,'`
toplev.c:196: conflicting types for `abort'
/NextDeveloper/Headers/ansi/stdlib.h:65: previous declaration of `abort'
make[1]: *** [toplev.o] Error 1

during stage 2.

The declaration in /NextDeveloper/Headers/ansi/stdlib.h is:

#ifdef  __GNUC__
extern volatile void abort(void);	<-- line 65
#else   /* !__GNUC__ */
extern void abort(void);
#endif  /* !__GNUC__ */

Anyone who knows a way out ?

TIA,
Toon.

             reply	other threads:[~1998-01-30  3:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-01-30  3:27 Toon Moene [this message]
1998-01-30  8:10 ` egcs-980129 on m68k-next-nextstep3: toplev.c:196: conflicting types for abort 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=9801301125.AA16155@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).