Subject: Re: CVS commit: pkgsrc/mk/compiler
To: Manuel Bouyer <bouyer@antioche.eu.org>
From: Johnny C. Lam <jlam@buildlink.org>
List: tech-pkg
Date: 02/07/2004 23:54:40
On Sat, Feb 07, 2004 at 08:30:45PM +0100, Manuel Bouyer wrote:
> On Sat, Feb 07, 2004 at 05:37:52PM +0100, Manuel Bouyer wrote:
> > On Sat, Feb 07, 2004 at 04:23:20PM +0100, Marc Recht wrote:
> > > >Symlink the compiler into ${WRKDIR} so that there's a consistent path to
> > > >the compiler and that it's behind .tools/bin and .buildlink/bin,
> > > >regardless of whether or not we're using gcc3-c or not, or whether it's
> > > >been installed yet in the process of satisfying dependencies, etc.
> > > 
> > > This commit breaks pkgsrc for me (1.6ZI). I get the same errors describe in 
> > > pkg/24345.
> > 
> > For me too (on solaris). From what I found on solaris, .gcc/bin/gcc is called
> > with ld's options, because work/.buildlink/bin/ld has:
> > cmd="/local/metal1/pkgbuild/security/openssh/work.metal/.gcc/bin/gcc"
> 
> Hum, I'm not sure it's related to this commit. In fact work/.buildlink/bin/ld
> is a (hard) link to work/.buildlink/bin/gcc.
> This seems to be a buildlink2-only problem, buildlink3-packages (e.g. openssl)
> don't have this problem, because  work/.buildlink/bin/ld is a separate
> script from work/.buildlink/bin/gcc.

This particular problem you're experiencing is actually a
openssh*/Makefile problem as it redefines LD to ${CC}, which is
generally a bad thing to do (as you've noted).  It should just pass
LD=${CC} to the configure process as the comment in the Makefile says
that it wants to do.

	Cheers,

	-- Johnny Lam <jlam@buildlink.org>