From: Eli Zaretskii Newsgroups: comp.os.msdos.djgpp Subject: Re: `void main' in Gnu packages---?! Date: Sat, 15 Jan 2000 10:16:36 +0200 Organization: NetVision Israel Lines: 16 Message-ID: <38802CE4.1C67F4E2@is.elta.co.il> References: <200001141504 DOT JAA08686 AT darwin DOT sfbr DOT org> NNTP-Posting-Host: ras1-p8.rvt.netvision.net.il Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Trace: news.netvision.net.il 947924296 25611 62.0.172.10 (15 Jan 2000 08:18:16 GMT) X-Complaints-To: abuse AT netvision DOT net DOT il NNTP-Posting-Date: 15 Jan 2000 08:18:16 GMT X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,ru,hebrew To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com Jeff Williams wrote: > > [time-1.7.tar.gz] compiled right out of the box (well, almost), but when > I ran the executable I got a brutal reminder that DOS can't fork(). One should never trust the compiler to make sure a Unix-born program will work when compiled with DJGPP. You should at least grep the sources for telltale Unix-isms like fork, pipe, etc. I generally find that, to have a good reliable port, there's no other way than to read the entire source of the program and look for code that won't work on DOS/Windows. (As a bonus, you get to understand how the program works.) Note that libc.info which comes with v2.03 includes a special chapter that describes those library functions which either always fail or do nothing (or almost nothing) in the DJGPP implementation. This chapter is specifically meant to be read by people who port packages from Unix.