Randy McMurchy wrote these words on 03/23/08 08:18 CST: > I believe you are reading a bit too much into this. It actually > doesn't list the entire build directory, just a portion of it. > And that directory won't exist on the root of the filesystem.
I'm wrong here. My installed tclConfig.sh doesn't reflect my normal build directory and that confused me. Rebuilding Tcl (using 8.4.18) indeed shows the exact build path is identified. How did I get a path in my tclConfig.sh that doesn't exist on my system? Because I built Tcl during the chroot phase of LFS. And that path is indeed different, and the installed tclConfig.sh reflects the exact path I used in LFS chroot. I'm not against fixing this. I just felt it to be unnecessary. How can this be exploited? So, just for the exercise. let's see who can come up with the most diminutive command(s) to insert in our instructions to modify tclConfig.sh or tclConfig.sh.in. We definitely don't want to modify the installed tclConfig.sh in /usr/lib. -- Randy rmlscsi: [bogomips 1003.22] [GNU ld version 2.16.1] [gcc (GCC) 4.0.3] [GNU C Library stable release version 2.3.6] [Linux 2.6.14.3 i686] 10:07:00 up 35 days, 55 min, 1 user, load average: 0.00, 0.01, 0.06 -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
