X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f From: Rugxulo Newsgroups: comp.os.msdos.djgpp Subject: Re: building libc (was "Re: ANNOUNCE: DJGPP port of Lua 5.2.0 uploaded.") Date: Tue, 27 Dec 2011 20:08:41 -0800 (PST) Organization: http://groups.google.com Lines: 54 Message-ID: <2ee81079-b1b5-422f-909b-fca74ad9cd52@x19g2000yqf.googlegroups.com> References: <201112220014 DOT pBM0ENQt004616 AT delorie DOT com> <74ee1ae2-8a21-4104-95d9-492073150519 AT l29g2000yqf DOT googlegroups DOT com> <3e0771bb-ed2b-4dfc-a654-75b59a3c65a7 AT p9g2000vbb DOT googlegroups DOT com> <5f4b3313-6ce8-4c7d-97a3-b9d313db1035 AT f11g2000yql DOT googlegroups DOT com> <7dd36ab5-c992-42b1-abae-0a75c7c7ee24 AT l19g2000yqc DOT googlegroups DOT com> <692c2768-e527-4fc3-95bf-4b44ba0d9cd5 AT p9g2000vbb DOT googlegroups DOT com> NNTP-Posting-Host: 65.13.115.246 Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 X-Trace: posting.google.com 1325045687 31405 127.0.0.1 (28 Dec 2011 04:14:47 GMT) X-Complaints-To: groups-abuse AT google DOT com NNTP-Posting-Date: Wed, 28 Dec 2011 04:14:47 +0000 (UTC) Complaints-To: groups-abuse AT google DOT com Injection-Info: x19g2000yqf.googlegroups.com; posting-host=65.13.115.246; posting-account=p5rsXQoAAAB8KPnVlgg9E_vlm2dvVhfO User-Agent: G2/1.0 X-Google-Web-Client: true X-Google-Header-Order: HNKRAUELSC X-HTTP-UserAgent: Mozilla/5.0 (X11; U; Linux i686; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.630.0 Safari/534.16,gzip(gfe) Bytes: 3836 To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id pBS4U2bu012838 Reply-To: djgpp AT delorie DOT com Hi, On Dec 23, 3:33 pm, Juan Manuel Guerrero wrote: > > You have corrupted your djgpp installation.  I would suggest to delete > into and make a fresh installation. Okay. Luckily I always keep .ZIP backups just for this reason. ;-) > AFAIK the cvs sources are never extracted into the djgpp installation > directory.  I usualy extract into tmp. Sounds reasonable, I just wasn't sure if it was allowed these days or not. > Before you start compiling you > must copy djgpp.djl and dxe.ld from the cvs /lib directory into your > djgpp installation /lib directory.  If this is not done the > compilation will abort when compiling symify. Wouldn't this be a good use for UPDATE.EXE (to automate it) when building? > > 2). DJTZN204.ZIP needs to be installed / unpacked? I guess you could > > No certainly no.  Everything you need to compile is checked out by CVS > or contained in djgpp.cvs.tar.gz. Okay, good. Yeah, I tested after you posted this, it (almost) works fine like you said (not counting /dev/null "quirk" in FreeDOS). > I do not understand all this.  Probably DOSEMU is not the best > emulator to compile the sources.  But I do not know.  I do not > remember if it was DOSEMU or DOSBOX but my experience with those > emulators was disapointing so I returned to VMware.  I am not > lobbying for it.  It is the one I use in my day-time job, so > I am most familiar with it than with the other ones. Well, to keep things simple, I (barely) try not to fiddle with ten bazillion different versions of the same thing. So hence I've never fiddled with VMware. I know DOSBox is completely unsuitable for compilation, though. > OFYI, I compiled today's libc sources on my thinkpad t60 with > MSDOS 6.22 (only SFN support).  FILES=250,  command.com environment > space = 16384,  smartdvr cache 10MB,  XMS = 64 MB.  With gcc 4.4.X > it compiled flawlessly in 8 min.  (No emulation but real hardware). > > BTW, you do not need LFN support to compile the CVS sources. Good to know. And it does work, not counting the /dev/null quirk (which I don't fully understand and don't anticipate a fix for).