On Wed, Feb 27, 2008 at 11:21:23AM -0800, Mike.Sullivan at Sun.COM wrote: > >From Nicolas.Williams at sun.com Wed Feb 27 10:58:42 2008 > > >On Wed, Feb 27, 2008 at 12:10:08PM -0600, Nicolas Williams wrote: > >> On Wed, Feb 27, 2008 at 01:40:44AM -0600, Norm Jacobs wrote: > >> > Be sure that you are linking against the TCL in the gate instead of > >> > build system so we don't end up with a mismatch if/when TCL upgrades > >> > at some future date. > >> > >> Hmmm, good point. > > > >Actually, this is not doable, unfortunately. That's because > >--with-tcl=$(ROOT)/usr/lib would find a tclConfig.sh file with... > >non-ROOT paths. > > expect points at the tcl/tk in the workspace, and that seems to work. > both because it needs access to the source and because it needs > the tclConfig.sh that points to the compiler being used rather than > the massaged one that we ship (in the proto area) which doesn't.
But the header files and what not will be found in /usr/... not in $ROOT/usr/...
