Article View: gnu.g++.bug
Article #1519problem with __eprintf.
From: "Karl Berry."
Date: Fri, 28 Oct 1988 23:26
Date: Fri, 28 Oct 1988 23:26
13 lines
1061 bytes
1061 bytes
The name of the eprintf facility changed in gcc 1.30 to have
an extra underscore. This is reflected in the new assert.h
that comes in the gcc distribution, and, of course, in gnulib,
where it is defined.
The bug comes from the fact that when tree.c (etc) are compiled,
the assert.h in the gcc-include directory is not seen. (At least
the last-used-time didn't get updated.) What is even more puzzling
is that a file that consists of nothing but a `#include "assert.h"'
and `main(){}' does find that new assert.h, while even moving
the include of assert.h to the top of the include list in, say,
tree.c does not produce the same effect. I was, as far as I know,
compiling with the same flags.
Technical Details
Message-ID:
<8810291214.AA13405@prep.ai.mit.edu>Path:
arc1-ca.pugleaf.net!utzoo!telly!ddsw1!lll-winken!uunet!tut.cis.ohio-state.edu!umb.edu!karlShow Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!telly!ddsw1!lll-winken!uunet!tut.cis.ohio-state.edu!umb.edu!karl
From: karl@umb.edu ("Karl Berry.")
Newsgroups: gnu.g++.bug
Subject: problem with __eprintf.
Message-ID: <8810291214.AA13405@prep.ai.mit.edu>
Date: 28 Oct 88 23:26:45 GMT
Sender: daemon@tut.cis.ohio-state.edu
Distribution: gnu
Organization: GNUs Not Usenet
Lines: 12