On Tue, Jun 07, 2005 at 09:25:06AM -0700, Jeremy C. Reed wrote:
> On Tue, 7 Jun 2005, Geert Hendrickx wrote:
> 
> > > >Concerning the usage of xaw (also relevant to my previous patch which
> > > >you already committed), I'm not sure what the impact of XAW_TYPE would
> > > >be on that.  teTeX's ./configure accepts --with-dvi-x-toolkit=(motif|
> > > >xaw|xaw3d|neXtaw), but I'm not familiar with xaw as to know what the
> > > >difference is.
> 
> The variable XAW_TYPE will tell you what "xaw" is used.
> 
> If for some reason, --with-dvi-x-toolkit=xaw doesn't work with xaw3d and
> neXtaw, then maybe use XAW_TYPE to set the  --with-dvi-x-toolkit=.
> XAW_TYPE is either: standard, xpm, 3d, or neXtaw. You could use that to
> define --with-dvi-x-toolkit=.
> 
> For "xpm" and "standard" use =xaw, but it seems like "xaw" should work for
> all since they should have the same interface.
> 
> You could test by replacing the include for ../../mk/xaw.buildlink3.mk
> with a specific Xaw like: ../../x11/neXtaw/buildlink3.mk or
> ../../x11/Xaw3d/buildlink3.mk or ../../x11/Xaw-Xpm/buildlink3.mk.

I'm currently trying all combinations.  They build fine but give errors
on make install...  

GH

-- 
:wq