Subject: Re: various problems with pkgsrc under solaris
To: None <tech-pkg@NetBSD.org>
From: Dan McMahill <dmcmahill@NetBSD.org>
Date: 06/20/2007 18:28:39
Dan McMahill wrote:
> Raymond Meyer wrote:
>> I'm building a lot of packages on SPARC Solaris from current pkgsrc
>> and haven't
>> noticed any problems. Are you building your packages inside chroot
>> jail? Which
>> GCC compilers do you use, the one bundled with Solaris under /usr/sfw
>> or the
>> one built from pkgsrc and which version?
> yes, inside a chroot jail. That part hasn't changed in quite some time.
> gcc-3.3.5. It was built via pkgsrc but with the following:
> TOOLCHAIN_BUILD= yes
> .if defined(TOOLCHAIN_BUILD)
> BUILDLINK_PASSTHRU_DIRS+= /opt/sfw/gcc-3.2/lib
> LDFLAGS+= -Wl,-R/opt/sfw/gcc-3.2/lib
> SITE_SPECIFIC_PKGS+= lang/gcc3-c
> SITE_SPECIFIC_PKGS+= lang/gcc3-c++
> SITE_SPECIFIC_PKGS+= lang/gcc3-f77
> LOCALBASE= /opt/tools/pkg
> PACKAGES= /opt/tools/packages
> PKG_DBDIR= /opt/tools/var
> and after that I commented out the TOOLCHAIN_BUILD part. This gave me a
> slightly more up to date compiler than the /opt/sfw one. I also then
> took /opt/sfw out of my path.
> I'll note that the compiler setup and chroot setup have not changed in
> probably a year and things were working correctly as recently as a few
> weeks ago.
Here is some more info. I have 2 chroot jails setup. jail #1 and jail
#2. They both were initially created with mksandbox and they null mount
/usr/bin /bin /top/tools/pkg, /opt/sfw, etc so they are essentially
identical. The difference is #1 has a new (as of a few days ago)
bootstrap and #2 has an old (a year or two or three) bootstrap.
In jail #1, pkgsrc-current and pkgsrc-2007Q1 both exhibit the problems
I've mentioned. in jail #2 neither exhibits the problem.
/usr/pkg/share/mk/* is identical between #1 and #2.
I've tried using the older bmake from #2 in #1 and that didn't change
I did printenv in both and they matched everywhere where they should.
I'm really stumped. I'm sure it will turn out to be something stupid,
but its just driving me nuts. I'm tempted to update the bootstrap in #2
and see that the problem shows up there, but then I've lost my working
Any other ideas?