From: "Andrew Zabolotny" <bit@freya.etu.ru>
To: "egcs@cygnus.com" <egcs@cygnus.com>
Subject: __eprintf problem in f77
Date: Tue, 09 Dec 1997 02:57:00 -0000 [thread overview]
Message-ID: <199712091057.NAA29050@freya> (raw)
There was a problem with __eprintf before in cc1/cc1plus, then it disappeared somewhere in last patches before
egcs-1.0 release. But it is still present in the f771 compiler.
problem:
when building the entire bulk of compilers, make stops at gcc/f/fini.c with the ld diagnostics
"undefined symbol __eprintf in fini.o"
cause:
gcc/assert.h defines assert() to call __eprintf when assertion fails.
fini.c includes some .h file which in turn includes assert.h.
__eprintf is not present in default libraries when using cc
solution:
define assert() in fini.c same way as in, for example, f/com.c, i.e:
/* This is used by the `assert' macro. It is provided in libgcc.a,
which `cc' doesn't know how to link. Note that the C++ front-end
no longer actually uses the `assert' macro (instead, it calls
my_friendly_assert). But all of the back-end files still need this. */
void
__eprintf (string, expression, line, filename)
#ifdef __STDC__
const char *string;
const char *expression;
unsigned line;
const char *filename;
#else
char *string;
char *expression;
unsigned line;
char *filename;
#endif
{
fprintf (stderr, string, expression, line, filename);
fflush (stderr);
abort ();
}
Greetings,
_\ndy@teamOS/2
next reply other threads:[~1997-12-09 2:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-12-09 2:57 Andrew Zabolotny [this message]
1997-12-10 12:23 ` Dave Love
1997-12-11 5:11 Andrew Zabolotny
1997-12-12 10:18 ` Dave Love
1997-12-16 1:41 Andrew Zabolotny
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=199712091057.NAA29050@freya \
--to=bit@freya.etu.ru \
--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).