This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: gcc merrily compiles empty files
- To: Henry Sobotka <sobotka at axess dot com>
- Subject: Re: gcc merrily compiles empty files
- From: Mo McKinlay <mmckinlay at gnu dot org>
- Date: Wed, 21 Jun 2000 01:14:09 +0100 (BST)
- cc: Michael Meissner <meissner at cygnus dot com>, gcc-bugs at gcc dot gnu dot org
# I don't mean technically empty in the sense of a file that ends up empty
# because conditions aren't met. I'm talking about a physically
# 0-byte-length source.
Surely these would amount to the same thing, in terms of object files,
though...and hence lead to the same problems?
If I didn't misread your original message, it points to a more serious
problem on your platform (i.e, why did those empty C sources compile to
produce object files which caused linkings problems?)
Just a thought :)
Mo.
--
Mo McKinlay Chief Software Architect inter/open Labs
mmckinlay (at) gnu.org http://www.gnu.org