From: karl@aspodata.se
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] sci-libs/{amd,camd}-2.4.6/ doc wierdness
Date: Wed, 16 Dec 2020 23:16:43 +0100 (CET) [thread overview]
Message-ID: <20201216221643.2B58182CBBF6@turkos.aspodata.se> (raw)
In-Reply-To: <0105de14-a276-d0c0-87fc-a79d064acc06@gentoo.org>
Michael:
> On 12/16/20 1:17 PM, Michael Orlitzky wrote:
> > On 12/16/20 12:30 PM, karl@aspodata.se wrote:
> >> Both sci-libs/{amd,camd}-2.4.6 gives this error in their build log:
> >>
> >> ! Package inputenc Error: Unicode character ^^H (U+0008)
> >> (inputenc) not set up for use with LaTeX.
> >>
> >
> > I can reproduce this... I'll take a look.
> It looks like the Makefile.am for the documentation was only tested with
> bash.
Yes, this part:
CAMD_UserGuide.pdf:
echo '\begin{verbatim}' > camd_h.tex
expand -8 $(top_srcdir)/Include/camd.h >> camd_h.tex
echo '\end{verbatim}' >> camd_h.tex
-ln -s $(srcdir)/*.{tex,bib} .
$(PDFLATEX) CAMD_UserGuide
$(BIBTEX) CAMD_UserGuide
$(PDFLATEX) CAMD_UserGuide
$(PDFLATEX) CAMD_UserGuide
Unfortunately, different echos handles excapes differently, see e.g.
https://helpmanual.io/man1/echo-posix/
In /bin/sh (dash) echo always converts thoose excapes (a' la sysV),
where bash needs -e to do it (a' la BSD).
One could replace the echos with printf "%s\n" as in
$ printf "%s\n" '\begin' | od -a
0000000 \ b e g i n nl
Note: echo '\e' is said to be undefined in dashs manual.
///
Also, the $(srcdir) seems defined as ".", and I get this useless link:
# ls -l
total 140
lrwxrwxrwx 1 portage portage 13 Dec 16 16:58 '*.{tex,bib}' -> './*.{tex,bib}'
///
> Try e.g.,
>
> CONFIG_SHELL=/bin/bash USE=doc emerge -v1 sci-libs/amd
>
> If that works for you, I'll add it to the ebuilds.
It will probably, cannot test just now, rust is compiling....
Regards,
/Karl Hammar
next prev parent reply other threads:[~2020-12-16 22:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-16 17:30 [gentoo-user] sci-libs/{amd,camd}-2.4.6/ doc wierdness karl
2020-12-16 18:17 ` Michael Orlitzky
2020-12-16 18:29 ` Michael Orlitzky
2020-12-16 22:16 ` karl [this message]
2020-12-17 1:02 ` Michael Orlitzky
2020-12-17 19:16 ` karl
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20201216221643.2B58182CBBF6@turkos.aspodata.se \
--to=karl@aspodata.se \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox