On Mon, Oct 13, 2014 at 05:59:45PM +0200, Armin K. wrote:
> On 10/13/2014 05:05 AM, Ken Moffat wrote:
> > I'm getting ready to add the *real* from-source texlive build to
> > the book, using the texmf tarball to provide 3.6GB of scripts and
> > docs. But I've got a couple of questions:
> >
I'll reply to _some_ of the contributions now, then go off and play
with texlive _again_, and start to produce at least one prototype
for review.
> >
> > The reason for that question is that the install consists of
> > mkdir -pv /opt/texlive/2014
> > cd /opt/texlive/2014
> > tar -xf /path/to/texlive-20140525-texmf.tar.xz --strip-components=1
> >
>
> As we assume that main sources tarball was extracted and user changed to
> the extracted directory, other sources reside inside the parent
> directory (..), so it would be easie(r,st) to use tar with -C, ie
>
> tar -xf ../texlive-20140525-texmf.tar.xz --strip-components=1 -C
> /opt/texlive/2014
>
> from the source/build directory.
>
Thanks for reminding we that we assume that - I'll need to put a
big Note: at the top of the package. It untars 3.6GB of files, and
for me that takes 1.3 SBU. I do not want to force people to have
7.2GB of space available.
> > 2. When building texlive without a pre-existing tex installation,
> > the build has to be done twice: first time, a few parts (asy, xindy)
> > require various tex programs and cannot be built, also the install
> > is slightly different; second time (with the tex progs on $PATH) it
> > can all be built as we currently do. Of course die-hard TeX purists
> > might shun asy and xindy. For them, the smaller install may
> > suffice.
> >
>
> Are they built separately from main texlive build? If so, it should be
> possible with some hacking to let the build scripts use programs from
> the source/build dir that were just built. However, I am not sure nor
> aware what else do they require from a working texlive setup.
>
Looking back at my notes from February (when I eventually gave up
in disgust) it seems clear to me that xindy needs latex and
pdflatex. For asy I found that it did in fact build, but the tests
fell apart. For asy, one possibility is that it needs files shipped
in texmf [ at that time, I had not found the texmf source ].
For xindy, my several test runs in august ended with me doing the
double build of the texlive source. Along the way, I had tried to
separately configure xindy after the initial install, but got into
all sorts of wierd problems.
Here is a summary of what I currently do:
pass 1:
configure without the xindy options
make
make check
make install_strip
make -C texk/texlive/tl_scripts run-texlinks
# that creates the symlinks
pass 2 [ or if building on the binary, differences noted at ¹,² ]
configure with the xindy options
make
make check
# ¹ only if building on the binary, a full install
# including xindy
make install_strip
# ² for the extras
make -C utils/xindy install
# and for both pass 2 and building on the binary:
configure in asymptote
make in asymptote
make check in asymptote
make install in asymptote
I did find one of Robbie's slackbuild scripts, but for the moment I
don't have the URL handy. In that he built without xindy, did a
DESTDIR install, then I think he configured in xindy. His script
was from 2013, I think - by this time I was using 2014, and that
was where I hit all sort of weird problems.
ĸen
--
Nanny Ogg usually went to bed early. After all, she was an old lady.
Sometimes she went to bed as early as 6 a.m.
--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
