On Wed, Feb 27, 2008 at 11:50:19AM -0800, mike.sullivan at sun.com wrote: > >From Nicolas.Williams at sun.com Wed Feb 27 11:36:47 2008 > > >> >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/... > > Ah so you mean the --with-tclinclude and --with-tkinclude options > that expect points into the tcl/tk source don't work?
I didn't know about those. SQLite3 doesn't have any such options. I could shoehorn them in with CPPFLAGS. I'll see if that works, if not then it will take more patching of SQLite3 build bits, and I'm loath to take that on right now. > It certainly could be missing some other options. I know lots of > things should be looking in the proto are but don't, and someday > I'll go look at that after all the more annoying problems are fixed. > It wasn't a huge priority when so few people were working on sfw. Right! We need to look at this problem more comprehensively. _After_ I'm done, hopefully ;)
