From: Leo Butler <leobutler@gmail.com>
To: libc-help@sourceware.org
Subject: Re: glibc 2.25 error during install
Date: Mon, 06 Aug 2018 17:53:00 -0000 [thread overview]
Message-ID: <CAGi=dNpjmbaL96Qnqc688UYPLYAPn+JxbHv4NCAvTUrt_m4sHw@mail.gmail.com> (raw)
In-Reply-To: <06a0d1fe-75bd-4af4-6ab1-de80ba5f9443@redhat.com>
Hi Carlos,
No error, that worked just fine.
bash-4.1$ make pdf
make -r PARALLELMFLAGS="" -C
/auto/ins-tools/linux_cel69/var/tmp/portage/sys-libs/glibc-2.25-r11/work/glibc-2.25
objdir=`pwd` pdf
[snip]
Output written on libc.pdf (1124 pages, 5879560 bytes).
Transcript written on libc.log.
bash-4.1$ ls -rlt manual/libc.pdf
-rw-r--r-- 1 insrgr eng 5879560 Aug 6 10:48 manual/libc.pdf
Regards,
- Leo
On Mon, Aug 6, 2018 at 10:33 AM Carlos O'Donell <carlos@redhat.com> wrote:
> On 08/06/2018 12:18 PM, Leo Butler wrote:
> > Here's the specific error I get:
> >
> > LANGUAGE=C LC_ALL=C makeinfo -P
> >
> /auto/ins-tools/linux_rh6/var/tmp/portage/sys-libs/glibc-2.25-r11/work/build-amd64-x86_64-pc-linux-gnu-nptl/manual/
> >
> --output=/auto/ins-tools/linux_rh6/var/tmp/portage/sys-libs/glibc-2.25-r11/work/build-amd64-x86_64-pc-linux-gnu-nptl/manual/
> > libc.info libc.texinfo
> > makeinfo GNU texinfo 4.13
>
> Enter the build directory and issue 'make pdf', do you get an error?
>
> --
> Cheers,
> Carlos.
>
next prev parent reply other threads:[~2018-08-06 17:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-06 16:18 Leo Butler
2018-08-06 17:34 ` Carlos O'Donell
2018-08-06 17:53 ` Leo Butler [this message]
2018-08-06 19:16 ` Leo Butler
2018-08-06 19:29 ` Carlos O'Donell
2018-08-06 20:32 ` Leo Butler
2018-08-06 21:25 ` Leo Butler
2018-08-07 5:00 ` Leo Butler
2018-08-07 5:31 ` Jeffrey Walton
2018-08-07 11:18 ` Carlos O'Donell
2018-08-06 19:17 ` Carlos O'Donell
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='CAGi=dNpjmbaL96Qnqc688UYPLYAPn+JxbHv4NCAvTUrt_m4sHw@mail.gmail.com' \
--to=leobutler@gmail.com \
--cc=libc-help@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).