From: <dan...@ya...> - 2001-09-14 05:08:19
|
If no objections I will upload update of binutils (reflecting recent changes to auto-import), mingw 1.1 runtime and w32api to SF on Sunday or Monday. Also complete mingw 1.1 package containing above plus latest gcc-2.95.3-20010828. Oh yeah, I'll put make in again too. Anything missing. Danny http://travel.yahoo.com.au - Yahoo! Travel - Got Itchy feet? Get inspired! |
From: Earnie B. <ear...@ya...> - 2001-09-14 12:12:49
|
Danny Smith wrote: > > > If no objections I will upload update of binutils (reflecting recent > changes to auto-import), mingw 1.1 runtime and w32api to SF on Sunday > or Monday. Also complete mingw 1.1 package containing above plus latest > gcc-2.95.3-20010828. Oh yeah, I'll put make in again too. Anything > missing. > I'll take care of the mingw-runtime-1.1 and w32api-1.1. I hope to wrap those up today, if not it'll be Monday. I finally convinced Chris to let me upload these packages to Cygwin's package release system so I'll do the release in twin mode. The concern at the moment is that Cygwin's package name for mingw-runtime is mingw-[time stamp] and the autoscript for creating the setup.ini file isn't smart enough to have a name change. Any other changes to the source would be for configuration purposes only. Earnie. _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com |
From: Christopher F. <cg...@re...> - 2001-09-14 18:05:56
|
On Fri, Sep 14, 2001 at 08:12:21AM -0400, Earnie Boyd wrote: >Danny Smith wrote: >>If no objections I will upload update of binutils (reflecting recent >>changes to auto-import), mingw 1.1 runtime and w32api to SF on Sunday >>or Monday. Also complete mingw 1.1 package containing above plus >>latest gcc-2.95.3-20010828. Oh yeah, I'll put make in again too. >>Anything missing. > >I'll take care of the mingw-runtime-1.1 and w32api-1.1. I hope to wrap >those up today, if not it'll be Monday. I finally convinced Chris to >let me upload these packages to Cygwin's package release system so I'll >do the release in twin mode. Now if only I could finally convince you that your cygwin-specific changes to w32api/lib/Makefile.in are incorrect and should be reverted, everyone would be happy. cgf |
From: Earnie B. <ear...@ya...> - 2001-09-14 19:48:26
|
Christopher Faylor wrote: > > On Fri, Sep 14, 2001 at 08:12:21AM -0400, Earnie Boyd wrote: > >Danny Smith wrote: > >>If no objections I will upload update of binutils (reflecting recent > >>changes to auto-import), mingw 1.1 runtime and w32api to SF on Sunday > >>or Monday. Also complete mingw 1.1 package containing above plus > >>latest gcc-2.95.3-20010828. Oh yeah, I'll put make in again too. > >>Anything missing. > > > >I'll take care of the mingw-runtime-1.1 and w32api-1.1. I hope to wrap > >those up today, if not it'll be Monday. I finally convinced Chris to > >let me upload these packages to Cygwin's package release system so I'll > >do the release in twin mode. > > Now if only I could finally convince you that your cygwin-specific > changes to w32api/lib/Makefile.in are incorrect and should be reverted, > everyone would be happy. > I agree they should change. I agree that only the dist target needs to do the modification, I will eventually do that. In the mean time I've modified it so that it only affects the case where configure --prefix=/usr --build=cygwin --target=cygwin make install prefix=/install/into/foo creates /install/into/foo/usr/include/w32api /install/into/foo/usr/lib/w32api a make install creates /usr/include/w32api /usr/lib/w32api . If --build!=cygwin --target=cygwin then it should install where expected, i.e. a target specific directory such as i686-pc-cygwin/include/w32api. If --target!=cygwin then the install doesn't even suffix /w32api. If --prefix=/usr/local --build=cygwin --target=cygwin then make install creates /usr/local/include/w32api /usr/local/lib/w32api . Earnie. P.S.: If you're interested in the rest of this discussion, see the cygwin-developer archives. _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com |
From: Jose F. <jrf...@em...> - 2001-09-15 11:53:54
|
Ok. Now I've joined the MinGW team at SourceForge. I've take a look the project pages at sourceforge (Bugs, Support, Patches= , Tasks, ...) and also to the mailing lists archives, but I feel a little l= ost and don't know by where should I start. What should I do? Trying to resolve some of the bugs or in something new? Jos=E9 Fonseca ----- Original Message ----- From: "Earnie Boyd" <ear...@ya...> To: "Jose Fonseca" <jrf...@em...> Sent: Wednesday, September 12, 2001 1:56 PM Subject: Re: [Mingw-users] ANN: My gnu-win32 webpage update > jrfonseca has been added to a MinGW developer. I've classified you as = a > Porter, you can change it if you want. > > Earnie. > |
From: <dan...@ya...> - 2001-09-15 21:05:18
|
--- Jose Fonseca <jrf...@em...> wrote: > Ok. Now I've joined the MinGW team at SourceForge. > > I've take a look the project pages at sourceforge (Bugs, Support, > Patches, > Tasks, ...) and also to the mailing lists archives, but I feel a > little lost > and don't know by where should I start. > > What should I do? Trying to resolve some of the bugs or in something > new? > > José Fonseca > Hello José and welcome. Don't worry about were you *should* start, something will grab you soon enough. I notice that you use bzip2 compression for all your distro's, and have a lightweight extracter available for download. I would like to see mingw go that way too. What do you think? BTW, thanks for your Dr Mingw. It has been very useful to me. Danny > > ----- Original Message ----- > From: "Earnie Boyd" <ear...@ya...> > To: "Jose Fonseca" <jrf...@em...> > Sent: Wednesday, September 12, 2001 1:56 PM > Subject: Re: [Mingw-users] ANN: My gnu-win32 webpage update > > > > jrfonseca has been added to a MinGW developer. I've classified you > as a > > Porter, you can change it if you want. > > > > Earnie. > > > > > > > _______________________________________________ > MinGW-dvlpr mailing list > Min...@li... > https://lists.sourceforge.net/lists/listinfo/mingw-dvlpr http://travel.yahoo.com.au - Yahoo! Travel - Got Itchy feet? Get inspired! |
From: Jose F. <jrf...@em...> - 2001-09-16 20:05:27
|
----- Original Message ----- From: "Danny Smith" <dan...@ya...> To: <min...@li...> Sent: Saturday, September 15, 2001 10:05 PM Subject: Re: [MinGW-dvlpr] MinGW developer > --- Jose Fonseca <jrf...@em...> wrote: > Ok. Now I've joined > the MinGW team at SourceForge. > > > > I've take a look the project pages at sourceforge (Bugs, Support, > > Patches, > > Tasks, ...) and also to the mailing lists archives, but I feel a > > little lost > > and don't know by where should I start. > > > > What should I do? Trying to resolve some of the bugs or in something > > new? > > > > Jos=E9 Fonseca > > > > Hello Jos=E9 and welcome. Don't worry about were you *should* start, > something will grab you soon enough. > > I notice that you use bzip2 compression for all your distro's, and have > a lightweight extracter available for download. I would like to see > mingw go that way too. What do you think? > I think that if there is a compression method that is much better than gz= ip (not to mention zip), that is free, and even has very nice GUI unpackers = (in Linux/unix and now Windows too), I can see no reason to pay for the extra bandwith... For those who may fell unconfortable with it, we can always provide a sim= ple extractor or even a small installer. I use it because it's very hard to find space (in the web, on my disk, etc..). So by using bzip2 I can put more in there and the upload/download times are smaller. > BTW, thanks for your Dr Mingw. It has been very useful to me. > You're welcome. It's very handy to me too. I really should get some time = to improve it further... (e.g., trace through system dlls and get more info from C++ classes). What do you think? > Danny > > > > > ----- Original Message ----- > > From: "Earnie Boyd" <ear...@ya...> > > To: "Jose Fonseca" <jrf...@em...> > > Sent: Wednesday, September 12, 2001 1:56 PM > > Subject: Re: [Mingw-users] ANN: My gnu-win32 webpage update > > > > > > > jrfonseca has been added to a MinGW developer. I've classified you > > as a > > > Porter, you can change it if you want. > > > > > > Earnie. > > > Jos=E9 Fonseca |
From: Jose F. <jrf...@em...> - 2001-09-16 20:29:09
|
In the sequence of my previous e-mails I remembered that one thing that i= s quite important and has been some what overlooked is the debugger. What is your opinion that Mingw should follow. 1. Use the cygwin version of gdb/insight? 2. Port these above to native win32? 3. Use a debugger other than gdb. I'm inclined towards the second because: 1. Even if not all like it, gdb is a widely established debugger in many platforms. 2. The cygwin versions can have problems with the paths and are slow. 3. Very few debuggers on windows support the .stabs format Jos=E9 Fonseca |
From: <dan...@ya...> - 2001-09-16 21:06:35
|
--- Jose Fonseca <jrf...@em...> wrote: > In the sequence of my previous e-mails I remembered that one thing > that is > quite important and has been some what overlooked is the debugger. > > What is your opinion that Mingw should follow. > > 1. Use the cygwin version of gdb/insight? > 2. Port these above to native win32? > 3. Use a debugger other than gdb. > > I'm inclined towards the second because: > 1. Even if not all like it, gdb is a widely established debugger in > many > platforms. > 2. The cygwin versions can have problems with the paths and are slow. > 3. Very few debuggers on windows support the .stabs format > > José Fonseca > > I agree with your inclination. I started working on gdb-5.x port about 3 months ago but soon realized that it required a very substantial time commitment and let it slip. Also, getting w32-specific patches into mainline can be frustrating. If you want to lead that project I will be happy to assist. Danny > > _______________________________________________ > MinGW-dvlpr mailing list > Min...@li... > https://lists.sourceforge.net/lists/listinfo/mingw-dvlpr http://travel.yahoo.com.au - Yahoo! Travel - Got Itchy feet? Get inspired! |
From: Christopher F. <cg...@re...> - 2001-09-16 21:58:36
|
On Mon, Sep 17, 2001 at 07:06:30AM +1000, Danny Smith wrote: > --- Jose Fonseca <jrf...@em...> wrote: > In the sequence of my >previous e-mails I remembered that one thing >> that is >> quite important and has been some what overlooked is the debugger. >> >> What is your opinion that Mingw should follow. >> >> 1. Use the cygwin version of gdb/insight? >> 2. Port these above to native win32? >> 3. Use a debugger other than gdb. >> >> I'm inclined towards the second because: >> 1. Even if not all like it, gdb is a widely established debugger in >> many >> platforms. >> 2. The cygwin versions can have problems with the paths and are slow. >> 3. Very few debuggers on windows support the .stabs format >> >> Jos? Fonseca >> >> >I agree with your inclination. I started working on gdb-5.x port about >3 months ago but soon realized that it required a very substantial time >commitment and let it slip. Also, getting w32-specific patches into >mainline can be frustrating. If you want to lead that project I will be >happy to assist. Since I'm the maintainer for the win32 target, it shouldn't be too difficult to get patches in, as long as you are not affecting too much of the core. If I've missed one, then please ping me. The biggest obstacle is getting the FSF assignment needed for major work. I have one patch sitting around now that I'd love to have in the core but is languishing due to a lack of assignment. Anyway, since gdb already supports DJGPP, I don't think that there should be too much extra effort required for path support of native windows. There really isn't *that* much cygwin specific stuff in the win32-nat.c file. There may be some functions that aren't available in mingw but I don't think that it should be too hard to get things working. Didn't Mumit Khan actually do this some time ago? FWIW, I'd love to have native PE-COFF debugging capabilities in gdb. I tried to push this through as a background project for one of the gdb engineers who reported to me but real work (tm) kept intruding on the project... Btw, as far as the "slowness" issue is concerned, I'm hard pressed to come up with what in cygwin would cause gdb to be slow. The only thing I can think of is path handling and there should not be that much path handling in a normal 'set a breakpoint'/'single step' session, should there? cgf |
From: <dan...@ya...> - 2001-09-17 00:08:46
|
--- Christopher Faylor <cg...@re...> wrote: > On Mon, Sep 17, 2001 at 07:06:30AM +1000, Danny Smith wrote: > > --- Jose Fonseca <jrf...@em...> wrote: > In the sequence of > my > >previous e-mails I remembered that one thing > >> that is > >> quite important and has been some what overlooked is the debugger. <snip> > Since I'm the maintainer for the win32 target, it shouldn't be too > difficult to get patches in, as long as you are not affecting too > much > of the core. If I've missed one, then please ping me. > > The biggest obstacle is getting the FSF assignment needed for major > work. I have one patch sitting around now that I'd love to have in > the > core but is languishing due to a lack of assignment. > > Anyway, since gdb already supports DJGPP, I don't think that there > should be too much extra effort required for path support of native > windows. > > There really isn't *that* much cygwin specific stuff in the > win32-nat.c > file. There may be some functions that aren't available in mingw but > I > don't think that it should be too hard to get things working. Didn't > Mumit Khan actually do this some time ago? > <snip> > > cgf > Thanks for that Christopher. I guess I've been using the "too hard" excuse because I wanted to do other things first. Anyway, you've encouraged me to have another go. José, are you still keen? Danny > _______________________________________________ > MinGW-dvlpr mailing list > Min...@li... > https://lists.sourceforge.net/lists/listinfo/mingw-dvlpr http://travel.yahoo.com.au - Yahoo! Travel - Got Itchy feet? Get inspired! |
From: Jose F. <jrf...@em...> - 2001-09-17 07:19:51
|
----- Original Message ----- From: "Danny Smith" <dan...@ya...> To: <min...@li...> Sent: Monday, September 17, 2001 1:08 AM Subject: Re: [MinGW-dvlpr] GDB > > --- Christopher Faylor <cg...@re...> wrote: > On Mon, Sep 17, 2001 > at 07:06:30AM +1000, Danny Smith wrote: > > > --- Jose Fonseca <jrf...@em...> wrote: > In the sequence of > > my > > >previous e-mails I remembered that one thing > > >> that is > > >> quite important and has been some what overlooked is the debugger. > > <snip> > > > Since I'm the maintainer for the win32 target, it shouldn't be too > > difficult to get patches in, as long as you are not affecting too > > much > > of the core. If I've missed one, then please ping me. > > > > The biggest obstacle is getting the FSF assignment needed for major > > work. I have one patch sitting around now that I'd love to have in > > the > > core but is languishing due to a lack of assignment. > > > > Anyway, since gdb already supports DJGPP, I don't think that there > > should be too much extra effort required for path support of native > > windows. > > > > There really isn't *that* much cygwin specific stuff in the > > win32-nat.c > > file. There may be some functions that aren't available in mingw but > > I > > don't think that it should be too hard to get things working. Didn't > > Mumit Khan actually do this some time ago? > > > > <snip> > > > > > cgf > > > Thanks for that Christopher. I guess I've been using the "too hard" > excuse because I wanted to do other things first. Anyway, you've > encouraged me to have another go. Jos=E9, are you still keen? > > Danny > Yes, I do. I know that Mumit made a quick port of gdb-4.18. Michael Rickman also por= ted gdb-4.18 with support for libreadline. Danny, have you another patches or any other thing to start with? Jos=E9 Fonseca |
From: Christopher F. <cg...@re...> - 2001-09-17 18:19:08
|
On Mon, Sep 17, 2001 at 08:18:19AM +0100, Jose Fonseca wrote: > >----- Original Message ----- >From: "Danny Smith" <dan...@ya...> >To: <min...@li...> >Sent: Monday, September 17, 2001 1:08 AM >Subject: Re: [MinGW-dvlpr] GDB > > >> >> --- Christopher Faylor <cg...@re...> wrote: > On Mon, Sep 17, 2001 >> at 07:06:30AM +1000, Danny Smith wrote: >> > > --- Jose Fonseca <jrf...@em...> wrote: > In the sequence of >> > my >> > >previous e-mails I remembered that one thing >> > >> that is >> > >> quite important and has been some what overlooked is the debugger. >> >> <snip> >> >> > Since I'm the maintainer for the win32 target, it shouldn't be too >> > difficult to get patches in, as long as you are not affecting too >> > much >> > of the core. If I've missed one, then please ping me. >> > >> > The biggest obstacle is getting the FSF assignment needed for major >> > work. I have one patch sitting around now that I'd love to have in >> > the >> > core but is languishing due to a lack of assignment. >> > >> > Anyway, since gdb already supports DJGPP, I don't think that there >> > should be too much extra effort required for path support of native >> > windows. >> > >> > There really isn't *that* much cygwin specific stuff in the >> > win32-nat.c >> > file. There may be some functions that aren't available in mingw but >> > I >> > don't think that it should be too hard to get things working. Didn't >> > Mumit Khan actually do this some time ago? >> > >> >> <snip> >> >> Thanks for that Christopher. I guess I've been using the "too hard" >> excuse because I wanted to do other things first. Anyway, you've >> encouraged me to have another go. Jos?, are you still keen? >> >> Danny >> > >Yes, I do. > >I know that Mumit made a quick port of gdb-4.18. Michael Rickman also ported >gdb-4.18 with support for libreadline. Danny, have you another patches or >any other thing to start with? For the record, I can't approve readline patches. Your best bet for those is to contact the FSF maintainer since we try to keep the readline on sources.redhat.com up-to-date with the FSF version. cgf |
From: Jose F. <jrf...@em...> - 2001-09-17 07:32:57
|
----- Original Message ----- From: "Christopher Faylor" <cg...@re...> To: <min...@li...> Sent: Sunday, September 16, 2001 10:58 PM Subject: Re: [MinGW-dvlpr] GDB ... > FWIW, I'd love to have native PE-COFF debugging capabilities in gdb. I > tried to push this through as a background project for one of the gdb > engineers who reported to me but real work (tm) kept intruding on the > project... > Do you mean be able to read MSVC debugging info? If yes I also had it in my mind for Dr. Mingw which uses binutils code for reading the debugging info. But nowadays the debugging info is no longer in COFF but in PDB. There is very few information about this format, but is surely possible (at least for the windows platform) to read it using the relevent MS DLLs. > Btw, as far as the "slowness" issue is concerned, I'm hard pressed to > come up with what in cygwin would cause gdb to be slow. The only thing > I can think of is path handling and there should not be that much path > handling in a normal 'set a breakpoint'/'single step' session, should > there? > Not only path handling will be slow. All file input/output can create lags AFAIK. Although I agree that in the command line version probably there is not much lag, once gdb is handled I really wanted to move forward Insight, and since it handles all the source files that are involved with the executable is somewhat slow. > cgf > > _______________________________________________ > MinGW-dvlpr mailing list > Min...@li... > https://lists.sourceforge.net/lists/listinfo/mingw-dvlpr > |
From: Christopher F. <cg...@re...> - 2001-09-17 18:25:30
|
On Mon, Sep 17, 2001 at 08:31:24AM +0100, Jose Fonseca wrote: > >----- Original Message ----- >From: "Christopher Faylor" <cg...@re...> >To: <min...@li...> >Sent: Sunday, September 16, 2001 10:58 PM >Subject: Re: [MinGW-dvlpr] GDB > > >... > >> FWIW, I'd love to have native PE-COFF debugging capabilities in gdb. I >> tried to push this through as a background project for one of the gdb >> engineers who reported to me but real work (tm) kept intruding on the >> project... >> > >Do you mean be able to read MSVC debugging info? If yes I also had it in my >mind for Dr. Mingw which uses binutils code for reading the debugging info. >But nowadays the debugging info is no longer in COFF but in PDB. There is >very few information about this format, but is surely possible (at least for >the windows platform) to read it using the relevent MS DLLs. It is in PDB by default but you can also cause MSVC to use COFF format. I think that COFF would be the easiest thing to tackle first. However, if someone wants to tackle PDB, too, I wouldn't complain. :-) It's possible that this is all very easy if you use Microsoft's published API for dealing with debugging, actually. cgf |
From: <dan...@ya...> - 2001-09-14 21:51:39
|
--- Earnie Boyd <ear...@ya...> wrote: > Danny Smith wrote: > > > > > > If no objections I will upload update of binutils (reflecting > recent > > changes to auto-import), mingw 1.1 runtime and w32api to SF on > Sunday > > or Monday. Also complete mingw 1.1 package containing above plus > latest > > gcc-2.95.3-20010828. Oh yeah, I'll put make in again too. > Anything > > missing. > > > > I'll take care of the mingw-runtime-1.1 and w32api-1.1. I hope to > wrap > those up today, if not it'll be Monday. Earnie, I see the announcements. Following your example, should I use a short "release" name (MinGW-1.1-tar.gz) rather than MinGW-1.1-"snapdate" long name for full package? Danny http://travel.yahoo.com.au - Yahoo! Travel - Got Itchy feet? Get inspired! |
From: Earnie B. <ear...@ya...> - 2001-09-17 12:44:27
|
Danny Smith wrote: > > --- Earnie Boyd <ear...@ya...> wrote: > Danny Smith wrote: > > > > > > > > > If no objections I will upload update of binutils (reflecting > > recent > > > changes to auto-import), mingw 1.1 runtime and w32api to SF on > > Sunday > > > or Monday. Also complete mingw 1.1 package containing above plus > > latest > > > gcc-2.95.3-20010828. Oh yeah, I'll put make in again too. > > Anything > > > missing. > > > > > > > I'll take care of the mingw-runtime-1.1 and w32api-1.1. I hope to > > wrap > > those up today, if not it'll be Monday. > > Earnie, I see the announcements. Following your example, should I use > a short "release" name (MinGW-1.1-tar.gz) rather than > MinGW-1.1-"snapdate" long name for full package? > MinGW-1.1-tar.gz should be the release. We should then bump the version number in anticipation of the next release and release snapshots toward the next release in the interim. We failed that on 1.0 but we should follow it for 1.1. Earnie. _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com |