From cygwin-return-60732-listarch-cygwin=sourceware dot cygnus dot com at cygwin dot com Thu Oct 31 19:39:25 2002 Return-Path: Delivered-To: listarch-cygwin at sourceware dot cygnus dot com Received: (qmail 23427 invoked by alias); 31 Oct 2002 19:39:24 -0000 Mailing-List: contact cygwin-help at cygwin dot com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner at cygwin dot com Mail-Followup-To: cygwin at cygwin dot com Delivered-To: mailing list cygwin at cygwin dot com Received: (qmail 23403 invoked from network); 31 Oct 2002 19:39:23 -0000 Received: from unknown (HELO relay1.softcomca.com) (168.144.1.67) by sources dot redhat dot com with SMTP; 31 Oct 2002 19:39:23 -0000 Received: from M2W089.mail2web.com ([168.144.108.89]) by relay1.softcomca.com with Microsoft SMTPSVC(5.0.2195.5329); Thu, 31 Oct 2002 14:39:23 -0500 Message-ID: <63340-2200210431193923346@M2W089.mail2web.com> X-Priority: 3 Reply-To: lhall at rfk dot com X-Originating-IP: 209.113.174.244 From: "lhall at pop dot ma dot ultranet dot com" To: scott dot prive at storigen dot com, cbfalconer at worldnet dot att dot net, cygwin at cygwin dot com Subject: RE: gdb hangs on a 486 Date: Thu, 31 Oct 2002 14:39:23 -0500 MIME-Version: 1.0 Content-type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-OriginalArrivalTime: 31 Oct 2002 19:39:23.0433 (UTC) FILETIME=[36D9B990:01C28115] OK, I guess I read too much into your suggestion=2E Having one test in setup=2Eexe is easier than gathering this information from the packages (which is really flawed anyway since no package=20 could say it was was built for an architecture that it's=20 dependencies didn't support - which pretty much nullifies the=20 whole thing)=2E A change to setup to check this is probably the=20 best and easiest way to protect the user (from himself? ;-) ) Documentation would also do the trick, although it's less fool- proof=2E OK, so there would be a relatively simple solution for this, at least as far as providing a warning goes=2E So, if anyone is concerned enough about this problem such that they want to=20 implement a solution, I think this qualifies=2E Thanks for the clarification Scott=2E Larry Original Message: ----------------- From: Scott Prive Scott=2EPrive@storigen=2Ecom Date: Thu, 31 Oct 2002 13:30:41 -0500 To: lhall@rfk=2Ecom, cbfalconer@worldnet=2Eatt=2Enet, cygwin@cygwin=2Ecom Subject: RE: gdb hangs on a 486 Agreed=2E CPU specific-packages for obsolete platforms are not needed, and= my remark was not intended to suggest something far less than this=2E=20 What I meant was, in SETUP=2EEXE provide some warning to the end user that= the packages they have selected will not run on their CPU=2E Allow them to= continue if they acknowledge the warning=2E=20 Imagine waiting for install to complete (probably on 56K), and then realiz= e it's i586+ only=2E Having a check in the installer means you only "wasted"= a ~250Kb download=2E -Scott > -----Original Message----- > From: lhall@pop=2Ema=2Eultranet=2Ecom [mailto:lhall@pop=2Ema=2Eultranet=2E= com] > Sent: Thursday, October 31, 2002 12:32 PM > To: Scott Prive; cbfalconer@worldnet=2Eatt=2Enet; cygwin@cygwin=2Ecom > Subject: RE: gdb hangs on a 486 >=20 >=20 > Hm, an interesting thought=2E This would require packages to=20 > provide some information, probably in their setup=2Ehint, to=20 > indicate their configuration target=2E Could work=2E But unless > there are packages that are configured specifically for other=20 > than the default "i686", I don't think it would be a feature=20 > that would get much use=2E But I'm willing to be proven wrong on=20 > this=2E :-) >=20 > Larry >=20 > Original Message: > ----------------- > From: Scott Prive Scott=2EPrive@storigen=2Ecom > Date: Thu, 31 Oct 2002 10:06:22 -0500 > To: lhall@rfk=2Ecom, cbfalconer@worldnet=2Eatt=2Enet, cygwin@cygwin=2Eco= m > Subject: RE: gdb hangs on a 486 >=20 >=20 >=20 > > At this point, I think most (all?) Cygwin packages are=20 > > configured like this=2E > > Whether or not that's true, it's not unwarranted=2E There's=20 > > good reason to=20 > > make use of the newer architectures' capabilities=2E >=20 > At the risk of asking for Yet Another Feature =2E=2E=2E and I'm=20 > thinking out loud > more than anything else=2E=2E=2E it would be friendly for the setup=20 > utility to do > a CPU check vs=2E the packages you selected=2E >=20 > I know=2E=2E "patches gratefully accepted"=20 > (You wouldn't want a patch in C from me=2E trust me :-) >=20 >=20 > >=20 > >=20 > >=20 > > >The whole system was downloaded through setup within the past 20 > > >days=2E Gdb came up in a windowed rather than command line > > >version=2E After the hang the mouse was dead and the system needed > > >rebooting=2E I normally can run for weeks without reboots=2E > >=20 > >=20 > > gdb -nw > >=20 > >=20 > >=20 > > >Under DJGPP I am running gdb 5=2E1=2E1, with no apparent > > >difficulties=2E There the configuration says "i386-pc-msdosdjgpp" > >=20 > >=20 > >=20 > > Sounds like you may want to get the source, reconfigure, and=20 > > build your > > own version targeting i386 or i486=2E > >=20 > >=20 > >=20 > >=20 > > Larry Hall lhall@rfk=2Ecom > > RFK Partners, Inc=2E http://www=2Erfk=2Ecom > > 838 Washington Street (508) 893-9779 - RFK Office > > Holliston, MA 01746 (508) 893-9889 - FAX > >=20 > >=20 > > -- > > Unsubscribe info: http://cygwin=2Ecom/ml/#unsubscribe-simple > > Bug reporting: http://cygwin=2Ecom/bugs=2Ehtml > > Documentation: http://cygwin=2Ecom/docs=2Ehtml > > FAQ: http://cygwin=2Ecom/faq/ > >=20 > >=20 > >=20 >=20 > -------------------------------------------------------------------- > mail2web - Check your email from the web at > http://mail2web=2Ecom/ =2E >=20 >=20 >=20 >=20 -------------------------------------------------------------------- mail2web - Check your email from the web at http://mail2web=2Ecom/ =2E -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/