On Wed, May 22, 2013 at 11:07:27PM +0100, Ramsay Jones wrote:
> Josh Triplett wrote:
> > On Tue, May 21, 2013 at 08:16:38PM +0100, Ramsay Jones wrote:
> >> Signed-off-by: Ramsay Jones <ramsay@xxxxxxxxxxxxxxxxxxx>
> >
> > I believe this will match both 32-bit and 64-bit MinGW, which seems
> > wrong. Please do check the architecture strings for 32-bit and 64-bit
> > MinGW, and handle them separately.
>
> Yes, given that, for me:
>
> $ uname -a
> MINGW32_NT-5.1 TOSHIBA 1.0.12(0.46/3/2) 2010-02-05 01:08 i686 unknown
> $
>
> I'm hoping that the following change will be sufficient (I don't have
> access to a 64-bit MinGW, so I don't know what 'uname -a' returns, but
> I think this will work ... ;-):
>
> $ git diff
> diff --git a/cgcc b/cgcc
> index e94a965..68f96b9 100755
> --- a/cgcc
> +++ b/cgcc
> @@ -226,7 +226,7 @@ sub add_specs {
> ' -D__OpenBSD__=1';
> } elsif ($spec eq 'unix') {
> return ' -Dunix=1 -D__unix=1 -D__unix__=1';
> - } elsif ($spec =~ /^mingw/) {
> + } elsif ($spec =~ /^mingw32/) {
Unfortunately, I don't think that suffices; I've seen a few different
architecture triples used for 64-bit MinGW, some of which include
"mingw32". I *think* it might work to match i[3-6]86-.*-mingw.
- Josh Triplett
--
To unsubscribe from this list: send the line "unsubscribe linux-sparse" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
