Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Message-ID: <63340-2200210431193923346@M2W089.mail2web.com>
Reply-To: lhall AT rfk DOT com
From: "lhall AT pop DOT ma DOT ultranet DOT com" <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: 8bit

OK, I guess I read too much into your suggestion.  Having one
test in setup.exe is easier than gathering this information from
the packages (which is really flawed anyway since no package 
could say it was was built for an architecture that it's 
dependencies didn't support - which pretty much nullifies the 
whole thing).  A change to setup to check this is probably the 
best and easiest way to protect the user (from himself? ;-) )
Documentation would also do the trick, although it's less fool-
proof.  OK, so there would be a relatively simple solution for
this, at least as far as providing a warning goes.  So, if anyone
is concerned enough about this problem such that they want to 
implement a solution, I think this qualifies.

Thanks for the clarification Scott.

Larry

Original Message:
-----------------
From: Scott Prive Scott DOT Prive AT storigen DOT com
Date: Thu, 31 Oct 2002 13:30:41 -0500
To: lhall AT rfk DOT com, cbfalconer AT worldnet DOT att DOT net, cygwin AT cygwin DOT com
Subject: RE: gdb hangs on a 486


Agreed. CPU specific-packages for obsolete platforms are not needed, and my
remark was not intended to suggest something far less than this. 

What I meant was, in SETUP.EXE provide some warning to the end user that
the packages they have selected will not run on their CPU. Allow them to
continue if they acknowledge the warning. 

Imagine waiting for install to complete (probably on 56K), and then realize
it's i586+ only. Having a check in the installer means you only "wasted" a
~250Kb download.

-Scott


> -----Original Message-----
> From: lhall AT pop DOT ma DOT ultranet DOT com [mailto:lhall AT pop DOT ma DOT ultranet DOT com]
> Sent: Thursday, October 31, 2002 12:32 PM
> To: Scott Prive; cbfalconer AT worldnet DOT att DOT net; cygwin AT cygwin DOT com
> Subject: RE: gdb hangs on a 486
> 
> 
> Hm, an interesting thought.  This would require packages to 
> provide some information, probably in their setup.hint, to 
> indicate their configuration target.  Could work.  But unless
> there are packages that are configured specifically for other 
> than the default "i686", I don't think it would be a feature 
> that would get much use.  But I'm willing to be proven wrong on 
> this. :-)
> 
> Larry
> 
> Original Message:
> -----------------
> From: Scott Prive Scott DOT Prive AT storigen DOT com
> Date: Thu, 31 Oct 2002 10:06:22 -0500
> To: lhall AT rfk DOT com, cbfalconer AT worldnet DOT att DOT net, cygwin AT cygwin DOT com
> Subject: RE: gdb hangs on a 486
> 
> 
> 
> > At this point, I think most (all?) Cygwin packages are 
> > configured like this.
> > Whether or not that's true, it's not unwarranted.  There's 
> > good reason to 
> > make use of the newer architectures' capabilities.
> 
> At the risk of asking for Yet Another Feature ... and I'm 
> thinking out loud
> more than anything else... it would be friendly for the setup 
> utility to do
> a CPU check vs. the packages you selected.
> 
> I know.. "patches gratefully accepted" 
> (You wouldn't want a patch in C from me. trust me :-)
> 
> 
> > 
> > 
> > 
> > >The whole system was downloaded through setup within the past 20
> > >days.  Gdb came up in a windowed rather than command line
> > >version.  After the hang the mouse was dead and the system needed
> > >rebooting.  I normally can run for weeks without reboots.
> > 
> > 
> > gdb -nw
> > 
> > 
> > 
> > >Under DJGPP I am running gdb 5.1.1, with no apparent
> > >difficulties.  There the configuration says "i386-pc-msdosdjgpp"
> > 
> > 
> > 
> > Sounds like you may want to get the source, reconfigure, and 
> > build your
> > own version targeting i386 or i486.
> > 
> > 
> > 
> > 
> > Larry Hall                              lhall AT rfk DOT com
> > RFK Partners, Inc.                      http://www.rfk.com
> > 838 Washington Street                   (508) 893-9779 - RFK Office
> > Holliston, MA 01746                     (508) 893-9889 - FAX
> > 
> > 
> > --
> > 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/
> > 
> > 
> > 
> 
> --------------------------------------------------------------------
> mail2web - Check your email from the web at
> http://mail2web.com/ .
> 
> 
> 
> 

--------------------------------------------------------------------
mail2web - Check your email from the web at
http://mail2web.com/ .


--
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/