This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: GCC's <assert.h> and C99
- To: Martin Buchholz <martin at xemacs dot org>
- Subject: Re: GCC's <assert.h> and C99
- From: Kamil Iskra <kamil at wins dot uva dot nl>
- Date: Thu, 21 Sep 2000 22:03:51 +0200 (MET DST)
- cc: gcc at gcc dot gnu dot org
On Sat, 16 Sep 2000, Martin Buchholz wrote:
> To summarize the problem: You would like to be able to use .o and .a
> files compiled and or linked by different compilers (gcc and non-gcc,
> pre- and post-C99), and never get a link error due an unreferenced
> function (e.g. __eprintf) that you've never heard of.
Out of curiosity:
Could you explain, why you get these undefined references? IIRC, __eprintf
is defined in libgcc.a. You are always supposed to link with -lgcc when
linking .o objects generated with GCC. So why is __eprintf undefined?
--
/ Kamil Iskra kamil@wins.uva.nl \
| Section Computational Science, Faculty FNWI, Universiteit van Amsterdam |
| tel. +31 20 525 75 35 fax. +31 20 525 74 90 |
\ Kruislaan 403 room F.202 1098 SJ Amsterdam (NL) /