X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f X-Received: by 10.236.220.39 with SMTP id n37mr15009097yhp.15.1384916396243; Tue, 19 Nov 2013 18:59:56 -0800 (PST) X-Received: by 10.49.71.111 with SMTP id t15mr915114qeu.6.1384916396213; Tue, 19 Nov 2013 18:59:56 -0800 (PST) Newsgroups: comp.os.msdos.djgpp Date: Tue, 19 Nov 2013 18:59:55 -0800 (PST) In-Reply-To: <52894CF0.6030201@gmx.de> Complaints-To: groups-abuse AT google DOT com Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=65.13.115.246; posting-account=p5rsXQoAAAB8KPnVlgg9E_vlm2dvVhfO NNTP-Posting-Host: 65.13.115.246 References: <921a79c9-9c3a-4823-9d68-bc644d63b96f AT googlegroups DOT com><834n7wczcq DOT fsf AT gnu DOT org> <84031e02-6a84-4359-b3e5-e71d005bef7d AT googlegroups DOT com> <52894CF0 DOT 6030201 AT gmx DOT de> User-Agent: G2/1.0 MIME-Version: 1.0 Message-ID: Subject: Re: missing files at start of ./configure From: rugxulo AT gmail DOT com Injection-Date: Wed, 20 Nov 2013 02:59:56 +0000 Content-Type: text/plain; charset=ISO-8859-1 X-Received-Bytes: 2993 X-Received-Body-CRC: 1049752880 Bytes: 3158 Lines: 39 To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: djgpp AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk Hi, On Sunday, November 17, 2013 5:10:40 PM UTC-6, Juan Manuel Guerrero wrote: > Am 16.11.2013 03:43, schrieb rugxulo AT nospam: > > > BTW, just FYI, as reported by iw2evk (Sep. 2) on BTTR, > > basically quoting Mikulas: > > > "* I fixed some bugs in WATTCP (a bug in CPU detection > > code that causes crash on 486 and a bug in getaddrinfo). > > I placed the patched WATTCP and recompiled OpenSSL to the > > directory with Links, use them instead of official DJGPP > > packages in case you want to recompile Links." > > > You (or someone) may wish to take a look at the changes. > > They have configured and compiled the port (wat3222s.zip) > using DJGPP-204. > > I have inspected the changes. They are documented in the > patch below. > > If they are useful and if they should be committed to the > watt code must be decided by Gisle Vanem. I have no > knowledge about how to detect 486 cpus. I'm not sure most people even care about 586s anymore, much less 486s. So I'm not sure it's even worth mentioning, sadly. Even my old machines aren't really working anymore, so I don't use them. It feels a bit sloppy to only use (or target) new machines, but what can you do? I'm not really that knowledgeable about old cpu detection, it's only something I've very very lightly looked into over the years. Just for tips, here are two links that may shed some light: 1). http://www.mail-archive.com/freedos-devel AT lists DOT sourceforge DOT net/msg00063.html 2). http://ftp.ibiblio.org/pub/micro/pc-stuff/freedos/files/util/system/cpulevel2007.zip