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

grant beattie <grant@netbsd.org> wrote:
> On Sun, Apr 25, 2004 at 11:45:19AM -0400, Jan Schaumann wrote:

> > _OPSYS_RPATH_NAME is used in several ways.  On the one hand, it's used
> > to specify the flags to the *compiler* which flags are to be passed on
> > to the linker, ie '-Wl,${_OPSYS_RPATH_NAME}'.  In this instance, the
> > correct flags for MIPSPro compilers would be '-Wl,-rpath,/path'.
> > Setting _OPSYS_RPATH_NAME to "-rpath " would not work, in this scenario
> > (nor did using two '-Wl' flags (as "-Wl,-rpath -Wl,/path"), which is why
> > we set _OPSYS_RPATH_NAME to "-rpath," for Irix to begin with).
>=20
> a minor tangent - packages should not directly use _OPSYS_RPATH_NAME,
> only RPATH_FLAG.

Yes, but the latter just becomes the former, so the difference for this
discussion is null. :-)

While looking at this, I notice that we have something called *LD*FLAGS
which is passed to the compiler (obviously during linking) as well as to
the linker.  That is, if there ever is a need to have flags that differ
when passed directly to the linker vs when passed to the compiler during
linking, then we're SOL.  Ugh, see above.  :-/

-Jan

--=20
I seem to be having this tremendous difficulty with my lifestyle.

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

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

iD8DBQFAjmrofFtkr68iakwRAkrkAKDAy1K1Rr+t+/HuFv6B8fwQBAQFMACfUj0q
9nKFwE569X1WtWnkhUzrj2s=
=reJ2
-----END PGP SIGNATURE-----

--xHFwDpU9dbj6ez1V--