Alexander E. Patrakov wrote these words on 12/31/05 09:40 CST: > I was able to circumvent this for hal-0.5.5.1, but I am not sure if this > is OK for the book: > > PYTHON=no ./configure --... > make > make -k install || true
I think it would be difficult to explain why we are circumventing the Python check. There is no configure switch that can be passed, and your way is simply taking advantage of the if test -z "$PYTHON"; then test in the configure script. As configure scripts are so convoluted and difficult to follow, I didn't try to see if there was an else clause or what it does if $PYTHON is set to something. We can let the folks here on the list have comment in this, and perhaps some good reasoning can be put forth as to why we would want to make configure not required. It would take examining all the executables and support files that are installed and see what all Python hooks are really there. -- Randy rmlscsi: [GNU ld version 2.15.94.0.2 20041220] [gcc (GCC) 3.4.3] [GNU C Library stable release version 2.3.4] [Linux 2.6.10 i686] 09:43:00 up 97 days, 19:07, 3 users, load average: 0.02, 0.11, 0.25 -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
