Wit wrote:
Wit wrote:
Confirmed! I get the same results as you now.
Executive summary: the text in the book can be interpreted to mean both
commands (Configure and ./configure) should be run. I did that and the
results caused the problem.
The proper interpretation of the text is closer to something like this.
============ My Corrected interpretation =============
If the defaults Perl would use are not going to be acceptable, run the
Configure command. Otherwise, ,/configure ...". The use of the word
"its" in the current second sentence is semantically misleading as "its"
would normally reference the most recent noun, Configure, rather than Perl.
I suggest that those two sentences may be reworked for less ambiguity.
That paragraph has already been corrected in the development book...
"To have full control over the way Perl is set up, you can run the
interactive Configure script and hand-pick the way this package is
built. If you prefer, you can use the defaults that Perl auto-detects,
by preparing Perl for compilation with:"
--
Dan
Dan, "you da man".
Thank you!
--
W.I
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
