Re: [lfs-dev] SVN 2020-08-11 chapter 8.4 tcl

2020-08-19 Thread Bruce Dubbs via lfs-dev

On 8/19/20 9:24 PM, Kevin Buckley via lfs-dev wrote:


Either way, actually, given the four PoIs above, make that, whichever way,
the LFS 10.0 TCL would seem to need a little more work, as it is missing
the manual installation of the HTML docs.


I came to realize that earlier today.  It will be done before the final 
release.


  -- Bruce

--
http://lists.linuxfromscratch.org/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page

Re: [lfs-dev] SVN 2020-08-11 chapter 8.4 tcl

2020-08-19 Thread Kevin Buckley via lfs-dev
On Wed, 19 Aug 2020 at 20:39, Roger via lfs-dev
 wrote:
> >
> >Meant to follow up on this one by asking if the TCL docs
> >are now required, or are still optional ?
>
> Optional, in that not having the docs hasn't caused any problem
> so far. Currently doing a mixed partition build with updated
> mpc-1.2.0. The gcc make check is taking hours and hours and...
> --
> Roger

That "Optional" is  less surprising, given the name of the "docs" tarball, vis

tar -xf ../tcl8.6.10-html.tar.gz --strip-components=1

Indeed, if you unpack the src tarball, you will see a docs subdirectory
that contains the man pages for TCL.

I could see that the optional HTML docs would have been added
into the LFS Book, so as to avoid having to have a TCL section
in BLFS that was only really there to ensure the HTML docs got
installed.

Having said that,

1) there's no HTML reader in LFS anyway

2) The TCL HTML docs come as pre-built HTML files (OK, so dot-htm) and unpack
into a single directory

tcl8.6.10/html/

which suggests that they could be installed into place, as a one-off separate
action, as opposed to needing to be done in the "core" install.

3) If you don't put the HTML tarball's pre-built contents in place, then  the
Makefile has a target that will try and build HTML pages from the man-pages
a using TCL tool anyway, vis:

#--
# This target creates the HTML folder for Tcl & Tk and places it in
# DISTDIR/html. It uses the tcltk-man2html.tcl tool from the Tcl group's tool
# workspace. It depends on the Tcl & Tk being in directories called tcl8.* &
# tk8.* up two directories from the TOOL_DIR.
#
# Note that for platforms where this is important, it is more common to use a
# build of this HTML documentation that has already been placed online. As
# such, this rule is not guaranteed to work well on all systems; it only needs
# to function on those of the Tcl/Tk maintainers.
#
# Also note that the 8.6 tool build requires an installed 8.6 native Tcl
# interpreter in order to be able to run.
#--

... some HTML targets ...

# You'd better have these programs or you will have problems creating Makefile
# from Makefile.in in the first place...
HTML_VERSION = `basename $(TOP_DIR) | sed s/tcl//`
BUILD_HTML = \
@${NATIVE_TCLSH} $(TOOL_DIR)/tcltk-man2html.tcl \
--useversion=$(HTML_VERSION) --htmldir="$(HTML_INSTALL_DIR)" \
--srcdir=$(TOP_DIR)/.. $(BUILD_HTML_FLAGS)

4) In the BLFS 9.1 Book, even if you do unpack the optional docs,
you still have to manually install them, from the unpacked location
with the following commands

If you downloaded the optional documentation, install it by issuing
the following commands as the root user:

mkdir -v -p /usr/share/doc/tcl-8.6.10 &&
cp -v -r  ../html/* /usr/share/doc/tcl-8.6.10


that are missing from the 10.0 LFS Book.

Either way, actually, given the four PoIs above, make that, whichever way,
the LFS 10.0 TCL would seem to need a little more work, as it is missing
the manual installation of the HTML docs.

Kevin
-- 
http://lists.linuxfromscratch.org/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page

Re: [lfs-dev] SVN 2020-08-11 chapter 8.4 tcl

2020-08-19 Thread Roger via lfs-dev
On Wed, 19 Aug 2020 13:34:12 +0100, Roger via lfs-dev
 wrote:

>On Wed, 19 Aug 2020 19:13:45 +0800, Kevin Buckley via lfs-dev
> wrote:
>
>>Meant to follow up on this one by asking if the TCL docs
>>are now required, or are still optional ?
>
>Optional, in that not having the docs hasn't caused any problem
>so far. Currently doing a mixed partition build with updated
>mpc-1.2.0. The gcc make check is taking hours and hours and...

The build, without tcl docs, has completed with /usr on a
separate partition. Booted up okay, logged in as root and
issued shutdown. Enough excitement for one day.
-- 
Roger

-- 
http://lists.linuxfromscratch.org/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page

Re: [lfs-dev] SVN 2020-08-11 chapter 8.4 tcl

2020-08-19 Thread Roger via lfs-dev
On Wed, 19 Aug 2020 19:13:45 +0800, Kevin Buckley via lfs-dev
 wrote:

>On Sat, 15 Aug 2020 at 16:31, Roger via lfs-dev
> wrote:
>>
>> The second paragraph begins "First, unpack the documentation..."
>>
>> This threw me until I remembered that with every package we
>> start by unpacking the source code and cd'ing into it. Perhaps
>> it would be as well to stop any possible confusion by starting
>> the second paragraph with something like:
>>
>> Having unpacked the source code and cd'd into it, unpack the
>> documentation...
>>
>> or
>>
>> As usual unpack the source code, cd into it, then unpack the
>> documentation...
>
>Meant to follow up on this one by asking if the TCL docs
>are now required, or are still optional ?

Optional, in that not having the docs hasn't caused any problem
so far. Currently doing a mixed partition build with updated
mpc-1.2.0. The gcc make check is taking hours and hours and...
-- 
Roger

-- 
http://lists.linuxfromscratch.org/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page

Re: [lfs-dev] SVN 2020-08-11 chapter 8.4 tcl

2020-08-19 Thread Kevin Buckley via lfs-dev
On Sat, 15 Aug 2020 at 16:31, Roger via lfs-dev
 wrote:
>
> The second paragraph begins "First, unpack the documentation..."
>
> This threw me until I remembered that with every package we
> start by unpacking the source code and cd'ing into it. Perhaps
> it would be as well to stop any possible confusion by starting
> the second paragraph with something like:
>
> Having unpacked the source code and cd'd into it, unpack the
> documentation...
>
> or
>
> As usual unpack the source code, cd into it, then unpack the
> documentation...

Meant to follow up on this one by asking if the TCL docs
are now required, or are still optional ?

The BLFS Book in 9.1 certainly had them as optional, in which
case, the text from there,

---
If you downloaded the optional documentation, unpack the tarball
by issuing the following command:
---

or some version of it that points out the optional status, might make
more sense, especially as the introductory text talks about TCL, Expect
and DejaGNU only being needed to run GCC tests, rather than being
sine qua non packages.
-- 
http://lists.linuxfromscratch.org/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page

[lfs-dev] SVN 2020-08-11 chapter 8.4 tcl

2020-08-15 Thread Roger via lfs-dev
The second paragraph begins "First, unpack the documentation..."

This threw me until I remembered that with every package we
start by unpacking the source code and cd'ing into it. Perhaps
it would be as well to stop any possible confusion by starting
the second paragraph with something like:

Having unpacked the source code and cd'd into it, unpack the
documentation...

or

As usual unpack the source code, cd into it, then unpack the
documentation...
-- 
Roger

-- 
http://lists.linuxfromscratch.org/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page