From: Sternbach, W. [IT] <wil...@ss...> - 2002-03-28 21:29:22
|
Hello, I found another problem with gcc 2.95.3-6. gcc 2.95.2 can compile the extremely large and complex Larry Wall Perl interpreter (which is written in "C"). You download the "C" source code and you build it using gcc. But, with our "new" gcc 2.95.3-6 compiler, it doesn't compile. I spent alot of time to figure out why. Someone (making a patch to the gcc after version 2.95.2, decided to change the c:\gcc\include\winbase.h and other header files. In c:\gcc\include\winbase.h, someone modified the structure to have a name _ANONYMOUS_UNION and _ANONYMOUS_STRUCT preceding which contains wProcessorArchitecture. Also other similar changes were made. Now, Perl (which is one of the most used language used to process data from web pages on the internet) can no longer be compiled with the gcc 2.95.3 compiler. Every other Microsoft, Borland, Watcom, Sun, and gcc on Sun can compile the "C" source code of the "Perl Interpreter". The only people who cannot are the people who use gcc 2.95.3-6. As a result, I have been forced to go back to using the gcc 2.95.2 compiler. If someone would be willing to fix the 2.95.3-6 compiler, it would be great. I hope the new gcc version 3 compiler will not inherit have these bad header files from 2.95.3-6 compiler. I have a question: If I go back to using the gcc 2.95.2 compiler, is there any serious bugs I should be aware of? I'm sure the 2.95.3-6 compiler contains bug fixes, but I'm not sure where to look to find a history of the bug fixes. Thanks in advance for your Email reply. - Bill |
From: <dan...@ya...> - 2002-03-28 23:55:05
|
--- "Sternbach, William [IT]" <wil...@ss...> wrote: > Hello, > > I found another problem with gcc 2.95.3-6. > In c:\gcc\include\winbase.h, someone modified the > structure to have a name > _ANONYMOUS_UNION and _ANONYMOUS_STRUCT preceding > which contains wProcessorArchitecture. > Also other similar changes were made. > I think the quickest way to fix your problem may be to simply include windows.h before winbase.h. That will define those macros. Perhaps the defines you mention don't really belong in windows.h but in windef.h. Any patch you care to submit will be reviewed. Danny > _______________________________________________ > MinGW-users mailing list > Min...@li... > > You may change your MinGW Account Options or unsubscribe at: > https://lists.sourceforge.net/lists/listinfo/mingw-users http://www.sold.com.au - SOLD.com.au Auctions - 1,000s of Bargains! |
From: Chris H. <pop...@so...> - 2002-03-29 17:46:05
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > -----Original Message----- > From: min...@li... > [mailto:min...@li...]On Behalf Of > Danny Smith > Sent: Friday, March 29, 2002 12:55 AM > To: Sternbach, William [IT]; 'min...@li...' > Subject: Re: [Mingw-users] Another bug in gcc 2.95.3-6. > > I think the quickest way to fix your problem may be to simply > include windows.h before winbase.h. That will define those > macros. > Perhaps the > defines you mention don't really belong in windows.h but in > windef.h. Any > patch you care to submit will be reviewed. According to Charles Petzold's book "Programming Windows" 'windows.h' should always be included before any other header files. Regards Chris P.S. Sorry, Danny! I was only going to post this on the list, not to your private mailbox. -----BEGIN PGP SIGNATURE----- Version: PGP 7.0.4 iQA/AwUBPKSpAg6qxNNoghKpEQIs2QCg2E6u6l38XzIA9w+BHsY7M5QIIq0AoNbS 8QJ+Lqr3iiADC1EAPh4sTWJM =ppUu -----END PGP SIGNATURE----- |
From: Max B. <ma...@uk...> - 2002-03-29 21:17:33
|
> > I found another problem with gcc 2.95.3-6. > > In c:\gcc\include\winbase.h, someone modified the > > structure to have a name > > _ANONYMOUS_UNION and _ANONYMOUS_STRUCT preceding > > which contains wProcessorArchitecture. > > Also other similar changes were made. > > > > I think the quickest way to fix your problem may be to simply include > windows.h before winbase.h. That will define those macros. Perhaps the > defines you mention don't really belong in windows.h but in windef.h. Any > patch you care to submit will be reviewed. > > Danny Isn't winbase.h one of a group of files that you are _never_ supposed to include itself? Just include windows.h, and let it do the rest? Max. |