Message-Id: <200006271630.TAA26325@mailgw1.netvision.net.il> Date: Tue, 27 Jun 2000 19:31:35 +0200 To: Laurynas Biveinis X-Mailer: Emacs 20.6 (via feedmail 8.2.emacs20_6 I) and Blat ver 1.8.5b From: "Eli Zaretskii" CC: djgpp-workers AT delorie DOT com In-reply-to: <39586C3C.6F58707A@softhome.net> (message from Laurynas Biveinis on Tue, 27 Jun 2000 10:56:28 +0200) Subject: Re: libc/stubs business References: <39586C3C DOT 6F58707A AT softhome DOT net> Reply-To: djgpp-workers AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: djgpp-workers AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk > Date: Tue, 27 Jun 2000 10:56:28 +0200 > From: Laurynas Biveinis > > Also, check output showed me: > Impure stub fsext.o(close) -> stub0002.o > Impure stub tempnam.o(access) -> stub0000.o > [...] > > I'm not sure if they need fixing too, because neither > fsext() nor tempnam() is ANSI/POSIX. I think that's because fsext is called from _open, _read, etc. which are called from ANSI functions, and so fsext cannot call close, which is non-ANSI. I think the solution is simply to call _close instead, because that's what close does anyway. As for tempnam, it is called by tmpfile, which is ANSI, and so the fact that tempnam calls access (a non-ANSI function) is a problem. 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. Would you like to add this? > And the third, how to interpret other check output? No clue. Doesn't the source tell? ;-)