Dirk may want to dig in here: Seems like you have a system with a /usr/lib64 dir for 64 bit libraries, but Tcl files in /usr/lib. If that is not an anomaly, it looks like we have a configure bug (conceiveably, a system might be using /usr/lib for architecture-independent files, and lib64/lib32 for binaries). It doesn't look too hard to modify configure to also check /usr/lib, but we probably shouldn't do it if one user has shot himself in the foot somehow.
-pd > On 19 Nov 2017, at 02:02 , Rolf Turner <r.tur...@auckland.ac.nz> wrote: > > Then I scanned through BldDir/config.log and found: > > LIBnn='lib64' > > (on line 19901 !!!) > > So it would appear that Peter D.'s conjecture is correct. > > OTOH this is waaayyy after the "checking for tclConfig.sh" business, which > happens at about line 15101 of config.log. So how does it have an impact on > that? > > And how did LIBnn get to be set to 'lib64'? I certainly didn't do it, and > there's nothing about 'lib64' in the environment variables that I have set. -- Peter Dalgaard, Professor, Center for Statistics, Copenhagen Business School Solbjerg Plads 3, 2000 Frederiksberg, Denmark Phone: (+45)38153501 Office: A 4.23 Email: pd....@cbs.dk Priv: pda...@gmail.com ______________________________________________ R-help@r-project.org mailing list -- To UNSUBSCRIBE and more, see https://stat.ethz.ch/mailman/listinfo/r-help PLEASE do read the posting guide http://www.R-project.org/posting-guide.html and provide commented, minimal, self-contained, reproducible code.
