On Tue, Feb 02, 2010 at 01:23:33PM +0100, Robert Millan wrote:
> severity 567698 wishlist
> thanks
>
> On Sat, Jan 30, 2010 at 11:46:26AM -0800, Josh Triplett wrote:
> > Package: gcc-mingw32
> > Version: 4.4.2-5
> > Severity: serious
> > Justification: Policy 7.2
> >
> > I upgraded to 4.4.2-5, and noticed that it no longer Depends on
> > mingw32-runtime. Instead, it Recommends mingw32-runtime and mingw-w64.
> > I'd guess this occurred so that users don't need to install both of
> > those runtimes, just the one for the target platform. However, without
> > either of them, the package seems entirely non-functional. Without a
> > runtime for a given target, gcc fails with errors like "error: stdio.h:
> > No such file or directory".
>
> It works here:
>
> $ amd64-mingw32msvc-gcc -c test.c
> $
And what does test.c contain?
Results of a similar test here:
/tmp$ dpkg -l gcc-mingw32 mingw32-runtime mingw-w64
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Cfg-files/Unpacked/Failed-cfg/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version
Description
+++-=================================-=================================-==================================================================================
ii gcc-mingw32 4.4.2-5 The GNU
Compiler Collection (cross compiler for MingW32 / MingW64)
un mingw-w64 <none> (no
description available)
un mingw32-runtime <none> (no
description available)
/tmp$ cat ~/src/samples/hello.c
#include <stdio.h>
int main(int argc, char *argv[])
{
printf("hello world\n");
return 0;
}
/tmp$ i586-mingw32msvc-gcc ~/src/samples/hello.c -o /tmp/hello32
/home/josh/src/samples/hello.c:1:19: error: stdio.h: No such file or directory
/home/josh/src/samples/hello.c: In function ‘main’:
/home/josh/src/samples/hello.c:5: warning: incompatible implicit declaration of
built-in function ‘printf’
(1) /tmp$ file /tmp/hello32
/tmp/hello32: ERROR: cannot open `/tmp/hello32' (No such file or directory)
(1) /tmp$ amd64-mingw32msvc-gcc ~/src/samples/hello.c -o /tmp/hello64
/home/josh/src/samples/hello.c:1:19: error: stdio.h: No such file or directory
/home/josh/src/samples/hello.c: In function ‘main’:
/home/josh/src/samples/hello.c:5: warning: incompatible implicit declaration of
built-in function ‘printf’
(1) /tmp$ file /tmp/hello64
/tmp/hello64: ERROR: cannot open `/tmp/hello64' (No such file or directory)
(1) /tmp$
A C compiler that can't compile hello world hardly seems functional.
> > For the ideal solution, I'd propose putting the 32-bit and 64-bit
> > compilers in separate binary packages, each with Depends on the
> > corresponding runtime. That way, the installed compiler will always
> > work.
>
> That seems entirely unnecessary. ORed Depends would be an option though.
ORed Depends would make one or the other compiler work, but it would
mean that gcc-mingw32's dependencies would only guarantee one functional
compiler and one broken one.
- Josh Triplett
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
