Mail Archives: cygwin/2002/10/31/14:47:58
> Thanks for the clarification Scott.
>
> Larry
NP. When someone contributes a patch, I'll be sure to transfer those thanks since I don't deserve them (suggestions are *always* free..) ;-)
>
> 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/
- Raw text -