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:22: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:21:46 -0400
Georg Schwarz wrote:
> Now what you could do is trying to make use of the new tools framework by
> having it create a symlink called cc in the .tools/bin directory pointing
> to your gcc compiler. This should take priority over your system cc.
> I am not sure however whether the later wrapper stage will already recognize
> this when it searches for a usable cc. As a workaround you could also
> manually create a respective symlink in your ${LOCALBASE}/bin directory
> (which, unfortunately I should say for other reasons, the cc wrapper
> does detect and prefer).
Actually, this didn't work either. It ended up trying to pull in lang/gcc, which
tried to pull in pkgtools/pkg_install-info, which then tried to pull in lang/gcc
again...
The "workaround" which seems to be working thus far is:
PKGSRC_COMPILER=gcc
_CC=/usr/freeware/bin/gcc
Of course, now it's still calling 'CC' instead of 'g++' for a C++ compiler (which
again is MIPSpro here). Time to sort that one out next.
Cheers,
Jared