On Fri, Sep 12, 2014 at 05:46:02PM -0500, Bruce Dubbs wrote:
> Ken,
>
> I've got a couple of problems when checking clisp. First you have:
>
> mkdir build &&
> cd build &&
> ./configure ...
>
>
> That needs to be ../configure ...
>
> I can easily fix that when I tag the package.
>
Bruce,
Oh. And yes please. If I had thought about this, I would have
tagged clisp when I tagged texlive, on the grounds that "I put this
in, so it must match my buildscript."
> Secondly, you have
>
> install -v -m644 doc/clisp.man /usr/share/man/man3/clisp_malloc.3 &&
> ln -sfv clisp_malloc.3 /usr/share/man/man3/clisp.3
>
> but there is no clisp.man anywhere. I can create the file in the build
> directory with 'make clisp.man', but it is complete garbage. The build
> gives about 20 errors like:
>
> lisp.1:1292: warning [p 9, 9.2i]: can't break line
>
> but worse, when I look at it with 'man -l clisp.man', I get complete garbage
> that looks like:
>
> [1mNAME[0m
> clisp - [34m[1mANSI[0m[1m[22m[38] [34m[1mCommon
> Lisp[0m[1m[22m[1] compiler, interpreter and debugger.
>
> Besides the make just creates that from clisp.1 which is OK.
>
> I'm inclined to just remove the last two lines, but wanted to check with you
> first.
>
> -- Bruce
>
Short answer - please remove them.
Long answer - I'm baffled how that got there. I can see that I
added it in r14114, but I cannot find anything like that in my
buildscript git tree. Occasionally, my editing in vim (in general,
not specifically for BLFS) gets a "mouse storm" some time after I
have switched machines using my KVM switch, and injects text from
another open application into the edit. But in this case my text in
BLFS seems to be the main result in google, and none of my likely
sources (slack, fedora, arch in this case) have anything like that.
I've just taken a look at gentoo (in the early stages I tried to
look at their ebuild, but the server I was trying to use did not
respond). During their install they have
doman clisp.1 || die
but I see that my x86_64 texlive build did indeed install clisp.1 :
/me boots that machine ... the page (when pasted into vim) reads as
something like this (the trailing CLISP(1) was linewrapped, it
should be in the columns up to 80).
CLISP(1) Platform: x86_64-unknown-linux-gnu CLISP(1)
NAME
clisp - ANSI[38] Common Lisp[1] compiler, interpreter and debugger.
SYNOPSIS
clisp [[-h] | [--help]] [--version] [--license] [-help-image]
where 'ANSI' and 'Common Lisp' in the name part are in blue (my
term is white on black). So, [34m[1m turns on a different colour
and the [0m[1m[22 variants both revert to normal colours.
Overall, I'm increasingly sorry that I ever touched TeX. [ raised a
ticket for 7.6 a little while ago, I now suspect the binaries have
different deps for i386 and x86_64, depending on who built them, but
perhaps my attempts to use ldd or scanelf went wrong on that
occasion ].
OTOH, I still want to get back to trying to set up my own UTF-8
bibliography for testing (my current example uses the example bib
from texlive, where any diacriticals (in practice, only diaeresis /
umlaut) are specified in old-fashioned TeX notation). sigh/
ĸ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
