Message-ID:	<395A46EC.5171DC14@softhome.net>
Date:	Wed, 28 Jun 2000 20:41:48 +0200
From:	Laurynas Biveinis <lauras AT softhome DOT net>
X-Mailer:	Mozilla 4.73 [en] (Win98; U)
X-Accept-Language:	lt,en
MIME-Version:	1.0
To:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
CC:	djgpp-workers AT delorie DOT com
Subject:	Re: libc/stubs business
References:	<Pine DOT SUN DOT 3 DOT 91 DOT 1000628160436 DOT 526C-100000 AT is>
Reply-To:	djgpp-workers AT delorie DOT com

Eli Zaretskii wrote:
> Yes.  But this doesn't fix the tempnam problem, does it?

Hm? The following part of that patch doesn't?

Index: djgpp/src/libc/compat/stdio/tempnam.c
===================================================================
RCS file: /cvs/djgpp/djgpp/src/libc/compat/stdio/tempnam.c,v
retrieving revision 1.2
diff -u -r1.2 tempnam.c
--- tempnam.c   1997/10/28 19:22:12     1.2
+++ tempnam.c   2000/06/28 08:31:01
@@ -1,5 +1,7 @@
+/* Copyright (C) 2000 DJ Delorie, see COPYING.DJ for details */
 /* Copyright (C) 1997 DJ Delorie, see COPYING.DJ for details */
 /* Copyright (C) 1995 DJ Delorie, see COPYING.DJ for details */
+#include <libc/stubs.h>
 #include <stdio.h>
 #include <stdlib.h>
 #include <string.h>

> > > I think it could be a good idea to get libc build procedure to run
> > > libclink/check automatically when the library is built, and abort the
> > > build if something fails to check out.
> >
> > I see it more as a part of 'make test' or 'make check', not simple make.
> > IMHO it is better to separate building and testing process.
> 
> I don't think this is a test.  It is no more a test than the fact that we
> use a lot of -W* switches, to reveal possible bugs.  I think that
> polluting ANSI/Posix namespace is a grave problem, and if an automated
> tool finds quite a few problems, even after several cleanup efforts, it's
> a clear sign that manual procedures are inadequate.

I wonder if anyone has reported this grave problem in 2.03 ;-) But I take
your point; however this tool needs some work to be automated. 

Laurynas

- Raw text -