From: Carlos O'Donell <carlos@redhat.com>
To: noloader@gmail.com, Leo Butler <leobutler@gmail.com>
Cc: libc-help@sourceware.org
Subject: Re: glibc 2.25 error during install
Date: Tue, 07 Aug 2018 11:18:00 -0000 [thread overview]
Message-ID: <d41a3dac-62f7-df2e-9bed-52cddbdd21fd@redhat.com> (raw)
In-Reply-To: <CAH8yC8n4L4-cdyE_V38mx_WROzTG7tN3hfuPe1wYRihzwBK-DA@mail.gmail.com>
On 08/07/2018 01:31 AM, Jeffrey Walton wrote:
> On Tue, Aug 7, 2018 at 1:00 AM, Leo Butler <leobutler@gmail.com> wrote:
>> Just to provide some closure to this issue, I want to report back that
>> 'makeinfo' isn't the true makeinfo at the time that installation of glibc
>> is initiated in Gentoo Prefix. I suspect the presence of this script is a
>> bootstrapping compromise that needs to be improved upon, as later in the
>> flow it becomes a symlink to a perl script called 'texi2any' from package
>> sys-apps/texinfo.
>
> Forcing users to build docs and making them do stupid tricks like
> MAKEINFO = true is an absolute waste of time and energy. I've got a
> half a dozen dev-boards and gadgets used for testing. Some of the
> boards don't have storage space for the tools or the docs. I am
> constantly patching configure scripts to get rid of the docs.
Nobody is forcing anyone to do anything. What you have is a need, and
it is not being met. This is free software, and your patches are welcome
to fix this use case by disabling the manual generation.
> The Configure scripts need to be fixed and stop trying to build docs
> if the doc tools are not installed. If the tools are installed then
> build them with an --enable-XXX just like any other feature.
Sounds great. I look forward to the patches.
--
Cheers,
Carlos.
next prev parent reply other threads:[~2018-08-07 11:18 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
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 [this message]
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=d41a3dac-62f7-df2e-9bed-52cddbdd21fd@redhat.com \
--to=carlos@redhat.com \
--cc=leobutler@gmail.com \
--cc=libc-help@sourceware.org \
--cc=noloader@gmail.com \
/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).