Subject: Re: pkg/30234: IRIX: PKGSRC_COMPILER=gcc uses mk/wrapper/gcc.mk,
To: None <pkg-manager@netbsd.org, gnats-admin@netbsd.org,>
From: Jared D. McNeill <jmcneill@invisible.ca>
List: pkgsrc-bugs
Date: 05/15/2005 19:52:01
The following reply was made to PR pkg/30234; it has been noted by GNATS.
From: "Jared D. McNeill" <jmcneill@invisible.ca>
To: Georg Schwarz <georg.schwarz@freenet.de>
Cc: gnats-bugs@NetBSD.org, pkg-manager@NetBSD.org,
gnats-admin@NetBSD.org, pkgsrc-bugs@NetBSD.org
Subject: Re: pkg/30234: IRIX: PKGSRC_COMPILER=gcc uses mk/wrapper/gcc.mk,
butcalls/usr/bin/cc(which is MIPSpro)
Date: Sun, 15 May 2005 15:51:28 -0400
Georg Schwarz wrote:
> > When the package calls 'cc', our wrapper gets called. Shouldn't our wrapper be smart
> > enough to look at PKGSRC_COMPILER, and realize that when 'cc -version' is called that
> > it outputs 'MIPSpro Compilers: Version 7.30', then start searching other names (gcc
>
> I hope that the wrapper will never be that "smart", i.e. bloated.
These scripts are generated, right? Why not determine the compiler to use when they're
generated (rather than each time they're run).
Either way, it doesn't seem unreasonable to me for a 'gcc wrapper' to attempt to call a
program called 'gcc' before the more generic 'cc'. The same especially goes for 'g++'
versus 'CC'.
Cheers,
Jared