woods@weird.com (Greg A. Woods) writes:
> 
> The failure, as I recall, was simply that libXaw3d was not found and
> that was because the only '-L' passed to the linker was for
> /usr/X11R6/lib, but of course my libXaw3d is in /usr/pkg/lib.

That doesn't sound right and would point to a bug in xpkgwedge, no in
print/gv.  Since gv uses imake to generate its Makefile, there is
something wrong with the Makefile generation caused by xpkgwedge's
presence.

> I can't possibly see how it could ever work in the presence of xpkgwedge
> without the obviously available and apparently necessary buildlink.mk
> from Xaw3d.  The buildlink.mk file should always be necessary in this
> case and the build should not work without it when xpkgwedge is in use.

print/gv builds correctly on my own machine, which also has xpkgwedge
installed, so I can't verify the error you're experiencing.

> I may have missed also adding the USE_BUILDLINK_ONLY line though, as
> I've got that (effectively) in my /etc/mk.conf

That will break many more packages than just print/gv, as most
packages rely on finding libraries and headers under ${LOCALBASE}.
Only the small (but growing!) collection of packages a few of us have
been "buildlinkifying" don't assume the presence of libraries and
headers in the installation tree.

Could you show me what you have in /etc/mk.conf that makes your pkgsrc
builds effectively non-standard?  It sounds like you've been working
on the same problem that buildlink was invented to solve, and it would
be beneficial to compare methods.

	Thanks,

     -- Johnny C. Lam <lamj@stat.cmu.edu>
        Department of Statistics, Carnegie Mellon University
        http://www.stat.cmu.edu/~lamj/