Re: [Mingw-users] SourceForge File Release Notice

[Soren A. <so...@wo...>]

On Thu, 16 Nov 2000 16:02:28 -0800, no...@so... wrote 
(Regarding  [Mingw-users] SourceForge File Release Notice):
 
> A new version of gcc has been released. 
> You can download it from SourceForge by following this link: 
> 
> <http://sourceforge.net/project/showfiles.php?group_id=2435&release_id=16289> 

I have been trying over the last 12 hours to download this file; most 
generally it stalls out at 2% and never resumes. It currently has just failed 
again. Is this sort of server failure common with Sourceforge? Is there any 
alternate download site I can use to get this?

I am having a problem with `protoize'. I am trying to use it to generate 
function declarations for a package that won't build under mingw-gcc 
2.95.2 due to compiler errors. The package is "Benny's DL Quantizer v2.4:" -
- `pngdl3' :

http://www.geocities.com/SiliconValley/Program/8979/color/index.htm

 a console program for doing color reduction on truecolor PNG files 
(outputs a GIF). The package includes something called `GIFsaver' which 
I have encountered before (and never been able to successfully build with 
mingw) before, and is source written for (as the author puts it, "oriented 
towards") the Watcom compiler.

BTW, I am aware that apps using LZW for GIFs are encumbered legally. 
I'd love to rid Benny's code of the GIF aspect if I only knew how.

If any reader knows of successful compilation of these sources, please help.

Back to the main point:
`Protoize' is behaving strangely; it at one point called `gcc' to build a file 
with an extension of 'X'. Then I did some tweaking (because gcc couldn't do 
it, returned a failure, so `protoize' wouldn't run). Now, `protoize' is for 
some reason *not* calling `gcc' but instead calling `cc1' and it fails because 
somewhere it (`cc1.exe') tries to write to `/dev/null' (which obviouly 
doesn't exist on DOS/Win32; instead, the equivalent is `nul'). This seems 
like a bug. I therefore am hoping that I am dealing with a known bug in 
that version of protoize.exe, and downloading a new gcc with fix it. Any 
help?

   Thanks,
     soren andersen

--
"Dont shoot the messenger."
     - me