Lubomir Sedlacik <salo@Xtrmntr.org> wrote:
 
> the path i am thinking about is:
> 
> 1a) decide what compiler $CC is in defs.${OPSYS}.mk, set a unique
>     variable, e.g. USE_SUNFORTE, USE_MIPSPRO, USE_GCC{,3}
> 1b) let the user set the variable, defaulting to USE_GCC(?) in mk.conf,
>     provide sane defaults for $CC, et al.
> 
> 2) fix gcc.buildlink2.mk to take effect only of one of the USE_GCC{,3}
>    variables is set

Yes, that makes a whole lot sense and shouldn't be too tricky.  Sorry
about the hack, I was just so happy to have X-apps working on Irix, I
was in a commit-frenzy. ;-)

> 3) fix buildlink wrappers and other mk/ files to avoid gccisms and
>    sanitize the environment (e.g., -Wl, or -Whatever transforms)

This might get a little more hairy.

> i have few local patches which allow me to use the Forte compiler quite
> successfully (all my ~70 pkgsrc packages are built with the native
> compiler, no gcc installed at all.  man, everything is _SO_ fast!, no
> libgcc dependencies, ...).  i will rethink this a bit more and send
> diffs soon.

I'll be happy to test and extend your patches on Irix.

-Jan

-- 
Ancient Principle of WYGIWYGAINGW:
What You Get Is What You're Given, And It's No Good Whining.
--Terry Pratchett et al. (The Science of Discworld)