The following reply was made to PR pkg/29470; it has been noted by GNATS.

From: grant beattie <grant@NetBSD.org>
To: gnats-bugs@netbsd.org
Cc: solaris-pkg-people@netbsd.org, gnats-admin@netbsd.org,
	pkgsrc-bugs@netbsd.org
Subject: Re: pkg/29470
Date: Wed, 23 Feb 2005 19:55:37 +1100

 --dgjlcl3Tl+kb3YDk
 Content-Type: text/plain; charset=us-ascii
 Content-Disposition: inline
 Content-Transfer-Encoding: quoted-printable
 
 On Tue, Feb 22, 2005 at 03:00:03PM +0000, Eric Boutilier wrote:
 
 >  > is it possible that Solaris 10 lacks the static libc? ...
 > =20
 >  Confirmed. In fact, as it turns out, Solaris 10 lacks all 32-bit
 >  static system libraries (including statically linked utilities),
 >  and all X11 static libraries.
 > =20
 >  See: http://iforce.sun.com/protected/solaris10/adoptionkit/general/remov=
 ed.html
 
 ok, a couple of options come to mind:
 
 	- detect this situation and manipulate the compiler arguments
 	  so that it remains possible to "statically" link (statically
 	  link against any static libraries present, otherwise
 	  dynamic).
 	- add the proper ABI support in pkgsrc for SunPro and gcc to
 	  produce 64bit binaries, as Solaris 10 still has the 64bit
 	  static libraries.
 
 the first is probably not that difficult, and solves the issue in
 the most elegant way, imho. most, if not all packages which are broken
 because of this on Solaris 10 will probably start working again. only
 those with the most convoluted of compiler arguments might escape.
 
 the above URL leads me to think that there are no static libraries in
 Solaris 10/x86, and maybe won't be any in /amd64?
 
 there are hopefully not too many packages affected by this issue. popt
 is probably trying to be ultra-conservative and make sure that all
 required symbols are present in a static executable regardless of linker
 argument order.
 
 of course, we should do the latter in pkgsrc, too, but more so for
 other reasons, I guess, and I guess it doesn't help much here for
 X11 stuff or /x86 :)
 
 grant.
 
 
 --dgjlcl3Tl+kb3YDk
 Content-Type: application/pgp-signature
 Content-Disposition: inline
 
 -----BEGIN PGP SIGNATURE-----
 Version: GnuPG v1.2.4 (NetBSD)
 
 iD8DBQFCHEUJluYOb9yiFXoRAsjOAJ90NzWxpFBnRTBCgYZkWHOHsxFLQACbBBeG
 1E7Wbq0RnWnSxHvAnS/jlSo=
 =EmJ/
 -----END PGP SIGNATURE-----
 
 --dgjlcl3Tl+kb3YDk--