Subject: Re: pkg/30234: IRIX: PKGSRC_COMPILER=gcc uses mk/wrapper/gcc.mk, butcalls/usr/bin/cc
To: None <pkg-manager@netbsd.org, gnats-admin@netbsd.org,>
From: Georg Schwarz <georg.schwarz@freenet.de>
List: pkgsrc-bugs
Date: 05/15/2005 19:18:01
The following reply was made to PR pkg/30234; it has been noted by GNATS.

From: Georg Schwarz <georg.schwarz@freenet.de>
To: "Jared D. McNeill" <jmcneill@invisible.ca>
Cc: Georg Schwarz <georg.schwarz@freenet.de>, 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 21:17:35 +0200 (CEST)

 > 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.
 
 > seems like it would be an obvious one to check if PKGSRC_COMPILER=gcc). Surely that's
 > not a package bug, but a wrapper bug.
 
 The way the wrappers find the real target (by searching some shell paths)
 is broken IMHO. I think jlam is planning to address this once he has
 stabelized the new tools framework. In my opinion there ought to be a
 way to specify precisely which binary to ultimately call as cc (or ld, or
 ar, ...). For the time being to my knowledge you could only resort to
 workarounds as described.
 
 -- 
 Georg Schwarz    http://home.pages.de/~schwarz/
  georg.schwarz@freenet.de  +49 178 8545053