From: Paul G. <pga...@qw...> - 2001-03-22 00:53:37
|
On 21 Mar 2001, at 21:39, the Illustrious Gilles Depeyrot wrote: > Hello everyone, > > Are there any plans for a mingw packaged gcc-2.95.3? Afaik, it is in process...since we only have a few people who want to volunteer their time as developers...it may be a little while before we can get a Mingw version of gcc-2.95.3 stable enough to put on the file download site. > > I have been using the November 99 mingw gcc packaged by Mumit Khan for > over a year. Since it has been working rather well, I am wary to upgrade > using the newer components from www.mingw.org (especially since there > are several components that need to be manually combined...) Well, you can use the latest mingw gcc package if you wish. I understand why you might be concerned. At any rate, I have been testing and running with the latest release of Mingw for some time now (since it came out actually), and have not had any problems with it beyond what are considered to be "known bugs". You can create your own specialized version of Mingw by first downloading and installing all of the new distributons (binutils, bfd, ld, runtime, last complete gcc, latest release of win32api) and then adding any special tools or processes which you require after you've successfully installed the new distibutions. For the most part, and this is a requirement for Mingw, any old apps built with Mingw are still compatible with the latest releases of Mingw and visa-versa (latest versions of Mingw are downwardly compatible with older versions of Mingw -- the only exception might be found if you are using the crtdll version of Mingw. Even so, the latest releases of Mingw still maintain compatibility with the crtdll release. Keep in mind, however, that the Mingw-crtdll release is no longer being updated. If you wish to upgrade your gcc and/or fiddle with .dif files, you can have the very latest version of Mingw-gcc (stability is another question). Personal opinion: The last complete Mingw-gcc release (December of last year I think) is quite stable. Updates that have been made to the various distributions were simply not allowed unless they enhanced the Mingw Development Tool Set. Peace, Paul G. Nothing real can be threatened. Nothing unreal exists. |
From: Paul G. <pga...@qw...> - 2001-03-23 03:09:22
|
Hi folks, On 22 Mar 2001, at 22:09, the Illustrious Gilles Depeyrot wrote: > Hi Paul, > > > Afaik, it is in process...since we only have a few people who want to > > volunteer their time as developers... > > Thanks for your time. Mingw-gcc is a very useful port of gcc. > "Merci beaucoup", we like to think so, too :-) > > You can create your own specialized version of Mingw by first > > downloading and installing all of the new distributons (binutils, bfd, > > ld, runtime, last complete gcc, latest release of win32api) and then > > adding any special tools or processes which you require after you've > > successfully installed the new distibutions. > > OK. I may have a try at that. > > > Personal opinion: The last complete Mingw-gcc release (December of > > last year I think) is quite stable. Updates that have been made to > > the various distributions were simply not allowed unless they enhanced > > the Mingw Development Tool Set. > > Where could I download this from? The Mingw web site has two links on > the home page: > > - Latest release: gcc-2.95.2. (Nov 7, 1999) > - Latest development snapshot: gcc-2.95.2-1. (Jan 21, 2000) You are not the first one to talk about this confusion. As for the confusion we are working on clarifying things. As to which you should use, that is really up to you. Personally, I feel that the latest Mingw distributions (minus the diffs) available from the the project page (https://sourceforge.net/projects/mingw/) are the best choice, especially if you have any desire to become a developer for the Mingw Project. Granted, I could be in the minority here -- even so, it is the latest releases of all things mingw (minus the diffs) that I am using. > > Is there another complete Mingw-gcc release aside from the ones above? Outside what we have noted here, none that I am aware of. Peace, Paul G. > > Best regards, > Gilles > > -- > Gilles Depeyrot <mailto:Gil...@wa...> > <http://perso.wanadoo.fr/gilles.depeyrot> > > > _______________________________________________ > MinGW-users mailing list > Min...@li... > > You may change your MinGW Account Options at: > http://lists.sourceforge.net/lists/listinfo/mingw-users > Nothing real can be threatened. Nothing unreal exists. |
From: Nicholas Lewin-K. <koh...@co...> - 2001-03-23 04:11:14
|
Hi, I am going to whine a little bit, so let me preface this with the comment that I have been using the mingw tool chain for about 3years now, and truely appreciate never having had to buy M$VC++. Thank you, Now.. I have been following the discussion about mingw as a host, cygwin and the mno-cygwin switch etc. My set up is as follows: in C:/cygwin - all the usual stuff except perl, gcc, binutils (mostly there for bash, groff, sed etc) in c:/GNU I have mingw/ with all the latest distributions from the source forge site. No if I download a new package from the net and I want to compile it my dream would be to just type in my bash shell > ./configure --host=mingw32; make; make install and go get a cup of coffee while it compiles. Alas life is never so easy. I have spent a lot of time hand writing makefiles to port a lot of the tools I need for my real work. I understand that if a library uses a lot of posix stuff you have to roll up your sleeves, and put some defs in the headers, and change the code to work native or just use cygwin dll, no problem there. But, if a package is already set up to run on windows, say for example libjpeg, it would be really nice to have some clear documentation about how to set up my system so that I can use configure etc. and focus on my own programming. Can someone spell out for me how to do this. Once I figure it out I would be happy to write a faq for other non experts like myself who hang out at the fringes. Nicholas CH3 | N Nicholas Lewin-Koh / \ Dept of Statistics N----C C==O Program in Ecology and Evolutionary Biology || || | Iowa State University || || | Ames, IA 50011 CH C N--CH3 http://www.public.iastate.edu/~nlewin \ / \ / nl...@ia... N C | || Currently CH3 O Graphics Lab School of Computing National University of Singapore The Real Part of Coffee koh...@co... |
From: Earnie B. <ear...@ya...> - 2001-03-23 15:46:01
|
Nicholas Lewin-Koh wrote: > > Hi, > I am going to whine a little bit, so let me preface this with the comment > that I have been using the mingw tool chain for about 3years now, and > truely appreciate never having had to buy M$VC++. Thank you, Now.. > > I have been following the discussion about mingw as a host, cygwin and the > mno-cygwin switch etc. My set up is as follows: > in C:/cygwin - all the usual stuff except perl, gcc, binutils (mostly > there for bash, groff, sed etc) > in c:/GNU I have mingw/ > with all the latest distributions from the source forge site. > > No if I download a new package from the net and I want to compile it my > dream would be to just type in my bash shell > > ./configure --host=mingw32; make; make install > Unless you've actually built GCC as a MinGW cross under Cygwin this won't work. You should instead do CC='gcc -mno-cygwin' ../configure in order to have autoconfiguration find the correct resources. This of course won't get rid of all of your problems but you'll be closer than you were before. > and go get a cup of coffee while it compiles. > You'll still have to set the cup down but not as often, hopefully. Earnie. P.S.: As a matter of practice you should never configure in the source directory unless the package is badly configured so as to force you to. Some packages will not correctly make if you do configure in the source directory. This is a GNU standard. _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com |
From: berkus <be...@k4...> - 2001-03-24 21:06:26
|
Use The Source, Earnie! Replying to your mail dated Friday, March 23, 2001, 8:35:02 PM, about "[Mingw-users] configure, automake etc. using mingw native on windows.": EB> P.S.: As a matter of practice you should never configure in the source EB> directory unless the package is badly configured so as to force you to. EB> Some packages will not correctly make if you do configure in the source EB> directory. This is a GNU standard. Hummm...interesting... Didn't know that. Where should I configure from then? Is it some specific directory or just "not the source one"? (Opps...maybe my binutils build screws up because of this??) keep in touch. berkus. * mailto:be...@k4... * http://ber.k45.ru * ICQ UIN 49516372 * * The Go! operating system development: http://attend.to/go * |
From: Earnie B. <ear...@ya...> - 2001-03-26 13:28:17
|
berkus wrote: > > Use The Source, Earnie! > > Replying to your mail dated Friday, March 23, 2001, 8:35:02 PM, > about "[Mingw-users] configure, automake etc. using mingw native on windows.": > > EB> P.S.: As a matter of practice you should never configure in the source > EB> directory unless the package is badly configured so as to force you to. > EB> Some packages will not correctly make if you do configure in the source > EB> directory. This is a GNU standard. > > Hummm...interesting... Didn't know that. Where should I configure from > then? Is it some specific directory or just "not the source one"? > (Opps...maybe my binutils build screws up because of this??) > I typically choose one of two options: 1) Change to the src directory and mkdir bld; cd bld; ../configure ... 2) Change to the parent of the package containing the src and mkdir bld; cd bld; ../package/src/configure ... (My guess is yes. Binutils must not be configured in the source directory.) Earnie. _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com |
From: <rei...@go...> - 2001-03-25 22:54:04
|
On Thu, 22 Mar 2001, Paul Garceau wrote: > =09Afaik, it is in process...since we only have a few people who want t= o=20 > volunteer their time as developers...it may be a little while before we= =20 > can get a Mingw version of gcc-2.95.3 stable enough to put on the file=20 > download site. I work currently on a Linux to MinGW cross compiler. Maybe you can give m= e some answers to some questions: I have started with the binutils 2.10.1 version without any patches. Are this the right sources? Build done without problems. Then I have loaded the last gcc version (2.95.3) and patched it with Mumits patches. I have analysed them and I think they are still necessary. Is this correct? Are there other patches necessary? Build of the compiler done without problems (without libstdc++.a). Only a tricky part with the runtime includes is necessary. I got the runtime (mingw and w32api) from the cygnus package cygwin-1.1.8= -2. Earnie explained some weeks ago, that this is the right source. I have no= t tried to build the runtime until now, but I used the headers from this pa= ckage to build gcc (limits.h, ...). After building the runtime, I would like to continue with gcc libstdc++.a= =2E Doing this in this order is necessary, because the build process for libs= tdc++ needs the startup code (crt0.o ). Is this the corrent way in you opinion? Are there some hints, that you can give me? Thank you for your suggestions Reinhard --=20 Ing. Reinhard Jessich mailto: rei...@go... A-1190 Vienna, Goergengasse 2/2/1 phone: +43/1/3692600 http://go.to/jessich mobile: +43/664/1735439 |
From: <dan...@ya...> - 2001-03-26 02:12:22
|
--- rei...@go... wrote: > On Thu, 22 Mar 2001, Paul Garceau wrote: > > Afaik, it is in process...since we only have a few people who want to > > volunteer their time as developers...it may be a little while before we > > can get a Mingw version of gcc-2.95.3 stable enough to put on the file > > download site. > > I work currently on a Linux to MinGW cross compiler. Maybe you can give me > some > answers to some questions: > > I have started with the binutils 2.10.1 version without any patches. > Are this the right sources? > Build done without problems. > > Then I have loaded the last gcc version (2.95.3) and patched > it with Mumits patches. I have analysed them and I think they are still > necessary. Is this correct? Are there other patches necessary? I believe that even with Mumits patches, the configure script makes the crtdll version of mingw the default. In gcc/configure, I made the following change to make __MSVCRT__ version the default: @@ -3888,15 +3897,17 @@ for machine in $build $host $target; do fi exeext=.exe case $machine in - *mingw32msv*) - ;; - *minwg32crt* | *mingw32*) + *mingw32crt*) tm_file="${tm_file} i386/crtdll.h" ;; + *mingw32msv* | *mingw32*) + ;; Following patches are not necessary, but they fix some additional bugs: C++ parser bug with function attributes: http://gcc.gnu.org/ml/gcc-patches/2001-01/msg01751.html __gthread_getspecific : http://www.geocrawler.com/archives/3/6013/2000/10/0/4465027/ > Build of the compiler done without problems (without libstdc++.a). > Only a tricky part with the runtime includes is necessary. > > I got the runtime (mingw and w32api) from the cygnus package cygwin-1.1.8-2. > Earnie explained some weeks ago, that this is the right source. I have not > tried to build the runtime until now, but I used the headers from this > package > to build gcc (limits.h, ...). > > After building the runtime, I would like to continue with gcc libstdc++.a. > Doing this in this order is necessary, because the build process for > libstdc++ > needs the startup code (crt0.o ). > > Is this the corrent way in you opinion? > Are there some hints, that you can give me? > When building libstdc++ for __MSVCRT__ version of mingw, I ran into a type mismatch in libio. The problem and the fix are described here: libio _IO_pos_t/_IO_off_t type mismatch: http://gcc.gnu.org/ml/gcc-patches/2000-09/msg01139.html > Thank you for your suggestions > Reinhard > > -- > Ing. Reinhard Jessich mailto: rei...@go... > A-1190 Vienna, Goergengasse 2/2/1 phone: +43/1/3692600 > http://go.to/jessich mobile: +43/664/1735439 > > _______________________________________________ > MinGW-users mailing list > Min...@li... > > You may change your MinGW Account Options at: > http://lists.sourceforge.net/lists/listinfo/mingw-users _____________________________________________________________________________ http://calendar.yahoo.com.au - Yahoo! Calendar - Access your appointments and meetings online. |
From: Ruediger W. <rue...@la...> - 2001-03-26 19:11:34
|
----- Original Message ----- From: <rei...@go...> > > I work currently on a Linux to MinGW cross compiler. Maybe you can give= me some > answers to some questions: Well I will try it > I have started with the binutils 2.10.1 version without any patches. > Are this the right sources? > Build done without problems. In theory yes. I had terrible problems building a native gcc 2.95.3 for windows with these tools. Apearantly they do not work. Use Binutils 2.9.1 instead for crosscompilin= g > Then I have loaded the last gcc version (2.95.3) and patched > it with Mumits patches. I have analysed them and I think they are still > necessary. Is this correct? yes. Well I have built my crosscompiler with gcc-2.95.2, gcc-2.95.3_test3 and Mumits patches. >Are there other patches necessary? Not really. But you may try also this patch from http://gcc.gnu.org/ml/gcc-patches/2001-01/msg01751.html > Build of the compiler done without problems (without libstdc++.a). > Only a tricky part with the runtime includes is necessary. What trick?? > I got the runtime (mingw and w32api) from the cygnus package cygwin-1.1.8-2. > Earnie explained some weeks ago, that this is the right source. I have = not > tried to build the runtime until now, but I used the headers from this package > to build gcc (limits.h, ...). I am always playing with the latest development snapshots from sourceforg= e but this package should work. > After building the runtime, I would like to continue with gcc libstdc++= .a. > Doing this in this order is necessary, because the build process for libstdc++ > needs the startup code (crt0.o ). > Bye R=FCdiger |
From: Paul G. <pga...@qw...> - 2001-03-26 00:24:26
|
Hi folks, Generally speaking, this looks to be correct. I am not familiar enough with building cross-compilers to really give any further comment, so will let others who have done cross-compilers reply with any hints or suggestions they might have. The only thing I might add is an encouragement to keep the mingw-gcc built libstdc++.a separate and apart from the Cygwin built libstdc++.a. Peace, Paul G. On 25 Mar 2001, at 23:26, the Illustrious rei...@go... wrote: > On Thu, 22 Mar 2001, Paul Garceau wrote: > > Afaik, it is in process...since we only have a few people who want to > > volunteer their time as developers...it may be a little while before > > we can get a Mingw version of gcc-2.95.3 stable enough to put on the > > file download site. > > I work currently on a Linux to MinGW cross compiler. Maybe you can give > me some answers to some questions: > > I have started with the binutils 2.10.1 version without any patches. Are > this the right sources? Build done without problems. > > Then I have loaded the last gcc version (2.95.3) and patched > it with Mumits patches. I have analysed them and I think they are still > necessary. Is this correct? Are there other patches necessary? Build of > the compiler done without problems (without libstdc++.a). Only a tricky > part with the runtime includes is necessary. > > I got the runtime (mingw and w32api) from the cygnus package > cygwin-1.1.8-2. Earnie explained some weeks ago, that this is the right > source. I have not tried to build the runtime until now, but I used the > headers from this package to build gcc (limits.h, ...). > > After building the runtime, I would like to continue with gcc > libstdc++.a. Doing this in this order is necessary, because the build > process for libstdc++ needs the startup code (crt0.o ). > > Is this the corrent way in you opinion? > Are there some hints, that you can give me? > > Thank you for your suggestions > Reinhard > > -- > Ing. Reinhard Jessich mailto: rei...@go... > A-1190 Vienna, Goergengasse 2/2/1 phone: +43/1/3692600 > http://go.to/jessich mobile: +43/664/1735439 > Nothing real can be threatened. Nothing unreal exists. |