On 14-09-2014 00:15, Wayne Blaszczyk wrote: > On 14/09/14 11:06, Christopher Gregory wrote: >> On Sun, September 14, 2014 12:01 pm, Christopher Gregory wrote: >>> On Sun, September 14, 2014 5:04 am, Fernando de Oliveira wrote: >>>> On 13-09-2014 13:09, Fernando de Oliveira wrote:
>>>>> I have identified some aspects of the tcl build that may be wrong. >>>>> $ grep WARNING: make.log >>>>> configure: WARNING: unrecognized options: --without-tzdata This still appears, dozens of times. >>>>> configure: WARNING: unrecognized options: --with-tclinclude, >>>>> --without-tzdata, --enable-shared, --enable-threads This still appears some time. >>>>> Reason is that it is building more packages: >>>>> sqlite3.8.6 itcl4.0.1 tdbc1.0.1 sqlite3.8.6 moved to proper sqlite-3.8.6 package, as optional instructions. >>>>> Perhaps more. Each needs to run configure in a different >>>>> subdirectory. sqlite worries, I cannot find how it could use system >>>>> one. Fixed, sqlite. >>>>> itcl and tdbc worries due to the warning messages. But worse, they >>>>> need correction to remove buid dir hardcoded. I seem to have succeeded >>>>> to gte sed's for both, based on the one in the book, but was by trial, >>>>> error and imitation, so cannot be sure if the are correct or >>>>> redundant. My seds were not correct. Warnings are there, but hard coded build dir are removed, now. >>>>> Files needing to be fixed, one new sed for each of them, they are >>>>> under tcl8.6.2/unix: >>>>> pkgs/itcl4.0.1/itclConfig.sh pkgs/tdbc1.0.1/tdbcConfig.sh >>>>> Can send privately my sed's, because they are ugly and "heuristic", >>>>> as I >>>>> said, made by imitation, but could serve as a base to make the new >>>>> ones >>>> >>>> Let me rephrase this: I know how the sed's work, I am not sure if the >>>> replacements I chose for the build dir entries are correct. >>>> >>>>> >>>>> I don't know how these observations might affect LFS, probably not, >>>>> as it is only used in tools. >>>>> >>>>> Thanks in advance. >>> I have just checked my log files for tcl that I built on Friday and found >>> the warnings that you have said. >>> >>> With regards to using system sqlite, it may require doing what we do in >>> ghostscript and removing the bundeled sqlite and any other included system >>> package that is located in the tcl pkgs dir. Right. >> Well as a test I deleted the bundled sqlite and compiled and did a destdir >> install and it does not build the sqlite library. So it must be somewhere >> deeper in the Makefile that governs what to use. > > Not sure if this helps, but you might want to look at what Arch has done. > https://projects.archlinux.org/svntogit/packages.git/tree/trunk/PKGBUILD?h=packages/tcl > https://projects.archlinux.org/svntogit/packages.git/tree/trunk/PKGBUILD?h=packages/sqlite > > They seem to remove the bundled sqlite from tcl, then build the tcl > sqlite interface from the sqlite package. > I have personally not done this. Thanks, Wayne and Christopher. I knew Arch's instructions. Had not noticed they removed sqlite. Moved its install to SQLite page. Have used a modified version of their seds. Still think that the version of one of them which I commented out in the xml is more robust, that was the reason I didn't use Arch's, yesterday. If someone know how to write the two new ones needed as the first version, I would still prefer. Was waiting for this, but its fixed in a less robust and less elegant way. -- []s, Fernando -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
