Subject: motif.buildlink3.mk/Solaris and symlinks
To: None <tech-pkg@NetBSD.org>
From: grant beattie <grant@NetBSD.org>
List: tech-pkg
Date: 06/13/2004 10:18:00
--VS++wcV0S1rZb1Fb
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

hi all,

I'm trying to figure out why packages can't find the motif header
files on Solaris, and it appears that the motif files aren't symlinked
from /usr/dt into ${BUILDLINK_DIR}.

if we are not using "native" motif, the appropriate buildlink3.mk file
is included (eg. lesstif), which will result in symlinks being
created, but no such logic exists for native motif.

how should this be handled? I guess we either need to symlink the
motif files into the buildlink dir (how?), or allow /usr/dt on the
compiler command line to remain unmodified (BUILDLINK_PASSTHRU_DIRS?)

thoughts?

grant.


--VS++wcV0S1rZb1Fb
Content-Type: application/pgp-signature
Content-Disposition: inline

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

iD8DBQFAy504luYOb9yiFXoRAnAlAJ9M2SkztxCe9VjSKgddYeB27U16gACePHeM
LFtU62bidZa4rocbXKU5ksw=
=YCW8
-----END PGP SIGNATURE-----

--VS++wcV0S1rZb1Fb--