--uh9ZiVrAOUUm9fzH
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Wed, Mar 10, 2004 at 01:07:58PM -0600, MLH wrote:

> > Try specifying PATCH on mk.conf, don't you have patch in your system?
>=20
> Ok. Actually I think using bpatch is a move in the right direction
> because solaris' /bin/patch had problems last I tried to use it.
> I was using the installed SUNWspro cc, but I think I'll install
> the solaris gcc3 and try to build gpatch using that.

I have no reason to believe there is a problem building GNU patch on
Solaris with SunPro. because of the way the GNU patch dependency is
handled now, any packages with patches will automatically gain a build
dependency on devel/gpatch (if you didn't optionally install it from
the 2nd CD).

I blow away /usr/pkg and rebuild everything regularly, as well as run
bulk builds with SunPro, and both would fail very early if GNU patch
didn't build.

what was the problem building packages with SunPro, and what version
do you have?

the specific problem of building a compiler from pkgsrc before all
necessary tools are available is a bootstrapping problem which we hope
to address in the near future...

> > I don't know nothing about Solaris, but it should have this at least, r=
ight?
>=20
> $ which patch
> /bin/patch
>=20
> but devel/gcc3 maybe can't use it?  Might be nice to document this
> in the bootstrap-pkgsrc for Solaris so someone else trying to use
> SUNWspro cc doesn't trip over it.

Solaris' /bin/patch is not sufficient for pkgsrc use.

grant.


--uh9ZiVrAOUUm9fzH
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (NetBSD)

iD8DBQFAT5mMluYOb9yiFXoRAjWoAKCCQptbSfnKRV2h83+HxzvOLx1fQwCfTVFg
emd8GaRKRPBodwh945jwsu4=
=v05I
-----END PGP SIGNATURE-----

--uh9ZiVrAOUUm9fzH--