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 15:15:08 +0100 (BST)
- cc: Michael Meissner <meissner at cygnus dot com>, gcc-bugs at gcc dot gnu dot org
# > 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?)
#
# It could be a platform thing. What happens if you try feeding gcc a
# 0-byte foo.c on your platform?
Exactly the same thing as if I hand it a file wrapped in #if 0..#endif
(yes, I checked :) - it links without problems, provided I wasn't relying
on the resultant object files containing any symbols, of course ;)
--
Mo McKinlay Chief Software Architect inter/open Labs
mmckinlay (at) gnu.org http://www.gnu.org