[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Bug-gnulib] sysexits.h

From: Simon Josefsson
Subject: Re: [Bug-gnulib] sysexits.h
Date: Wed, 11 Jun 2003 13:30:30 +0200
User-agent: Gnus/5.1003 (Gnus v5.10.3) Emacs/21.3.50 (gnu/linux)

Bruno Haible <address@hidden> writes:

> Simon Josefsson wrote:
>> This thread now contain many good suggestions for things to think
>> about when adding new modules.  Since I'm starting to have trouble
>> remembering them all by now, I think it would be useful to add a
>> simple README-dev or similar.  What do you think?
> A good idea. I've added the points you made to the main README.
> Feel free to add more of this when you think it's worth it.

Your clarification to one of the points

* Try to prevent that the files are built if they aren't needed on a
  platform.  Valid excuses to this rule include ELIDE constructs that
  lead to an empty .o file (see getopt module).

made me recall a system that couldn't handle empty .o files.  All *.c
files must declare at least one symbol, or the resulting *.o file was
regarded as corrupt when you tried to link it.  I saw this only a few
months ago, and I don't normally use historic machines (although
sometimes non-mainstream ones) so it may be relevant.  I'll see if I
can find out what machine this was.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]