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 >>>> ... >>>> configure: WARNING: unrecognized options: --with-tclinclude, >>>> --without-tzdata, --enable-shared, --enable-threads >>>> >>>> >>>> >>>> Reason is that it is building more packages: >>>> sqlite3.8.6 itcl4.0.1 tdbc1.0.1 >>>> >>>> perhaps more. Each needs to run configure in a different >>>> subdirectory. sqlite worries, I cannot find how it could use system >>>> one. >>>> >>>> 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 trila, >>>> error and imitation, so cannot be sure if the are correct or >>>> redundant. >>>> >>>> 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 >>>> >>>> Many installed file are affected: >>>> >>>> >>>> >>>> $ grep -r /fernando/ DEST-tcl8.6.2-old/ | grep -v Arquivo | wc -l >>>> 20 >>>> >>>> >>>> >>>> This means 20 places with the build dir hardcoded. >>>> >>>> >>>> >>>> I have built today only 6 packages, because I am studying this, but >>>> really need help, or someone to replace me, because a deep study seems >>>> to be necessary. >>>> >>>> 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. >>>> >>>> >>>> >>> >>> >>> -- >>> []s, >>> Fernando >>> -- >>> http://lists.linuxfromscratch.org/listinfo/blfs-dev >>> FAQ: http://www.linuxfromscratch.org/blfs/faq.html >>> Unsubscribe: See the above information page >>> >>> >>> >> Hello Fernando, >> >> >> 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. >> >> Regards, >> >> >> Christopher. >> >> >> -- >> http://lists.linuxfromscratch.org/listinfo/blfs-dev >> FAQ: http://www.linuxfromscratch.org/blfs/faq.html >> Unsubscribe: See the above information page >> >> > 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. > > Regards, > > Christopher. >
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. Regards, Wayne. -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
