public inbox for libc-help@sourceware.org
 help / color / mirror / Atom feed
From: Carlos O'Donell <carlos@redhat.com>
To: Leo Butler <leobutler@gmail.com>, libc-help@sourceware.org
Subject: Re: glibc 2.25 error during install
Date: Mon, 06 Aug 2018 19:29:00 -0000	[thread overview]
Message-ID: <eab15fd0-c360-2bd4-8220-7047d75686a0@redhat.com> (raw)
In-Reply-To: <CAGi=dNodQrwEuFJWLLQPrt5nzzj+Crr3hZFtJqKYkNFchQ0Ang@mail.gmail.com>

On 08/06/2018 03:16 PM, Leo Butler wrote:
> Removing the empty manual/libc.info and running "make info" generates
> another empty libc.info.
> 
> bash-4.1$ rm manual/libc.info
> bash-4.1$ make info
> make -r PARALLELMFLAGS="" -C
> /auto/ins-tools/linux_cel69/var/tmp/portage/sys-libs/glibc-2.25-r11/work/glibc-2.25
> objdir=`pwd` info
> make[1]: Entering directory
> '/auto/ins-tools/linux_cel69/var/tmp/portage/sys-libs/glibc-2.25-r11/work/glibc-2.25'
> make  -C manual info
> make[2]: Entering directory
> '/auto/ins-tools/linux_cel69/var/tmp/portage/sys-libs/glibc-2.25-r11/work/glibc-2.25/manual'
> LANGUAGE=C LC_ALL=C makeinfo -P
> /auto/ins-tools/linux_cel69/var/tmp/portage/sys-libs/glibc-2.25-r11/work/build-amd64-x86_64-pc-linux-gnu-nptl/manual/
> --output=/auto/ins-tools/linux_cel69/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
> make[2]: Leaving directory
> '/auto/ins-tools/linux_cel69/var/tmp/portage/sys-libs/glibc-2.25-r11/work/glibc-2.25/manual'
> make[1]: Leaving directory
> '/auto/ins-tools/linux_cel69/var/tmp/portage/sys-libs/glibc-2.25-r11/work/glibc-2.25'
> bash-4.1$ !find
> find . -name libc.info
> ./manual/libc.info
> bash-4.1$ ls -rlt manual/libc.info
> -rw-r--r-- 1 insrgr eng 0 Aug  6 12:01 manual/libc.info
> 
> I do see the texinfo file, looks like it's part of the source tarball (not
> generated):
> 
> bash-4.1$ ls -rlt
> /auto/ins-tools/linux_rh6/var/tmp/portage/sys-libs/glibc-2.25-r11/work/glibc-2.25/manual/libc.texinfo
> -rw-r--r-- 1 insrgr eng 4460 Feb  5  2017
> /auto/ins-tools/linux_rh6/var/tmp/portage/sys-libs/glibc-2.25-r11/work/glibc-2.25/manual/libc.texinfo

It should be doing way more work than this.

grep 'makeinfo' config.log
configure:4799: checking for makeinfo
configure:4815: found /usr/bin/makeinfo
configure:4826: result: makeinfo
configure:4841: checking version of makeinfo
ac_cv_prog_MAKEINFO=makeinfo
MAKEINFO='makeinfo'

Which makeinfo is being used?

Then run makeinfo --version?

-- 
Cheers,
Carlos.

  reply	other threads:[~2018-08-06 19:29 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
2018-08-06 19:16     ` Leo Butler
2018-08-06 19:29       ` Carlos O'Donell [this message]
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=eab15fd0-c360-2bd4-8220-7047d75686a0@redhat.com \
    --to=carlos@redhat.com \
    --cc=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).