This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: [PATCH] Fix INSTALL description for modified files in sourcedir
On 05/18/2012 04:57 PM, Carlos O'Donell wrote:
> On Fri, May 18, 2012 at 11:53 AM, Pedro Alves <palves@redhat.com> wrote:
>> On 05/18/2012 04:49 PM, Carlos O'Donell wrote:
>>
>>> Please note that even though you're building in a separate build
>>> directory, the compilation may need to create or modify files and
>>> directories in the source directory, including creating the directory
>>> @file{autom4te.cache} or creating @file{.mo} files in the @file{po}
>>> directory.
>>
>> I'd suggest zapping everything starting at ", including", and filing
>> bugzilla bug reports for the other issues, assuming glibc aims at
>> being able to be built from a read-only src tree.
>
> The manual should represent reality. I agree that we should file bug
> reports, but that's orthogonal to the issue of documentation being
> accurate. Do you agree?
I agree, though mentioning the autom4te.cache directory doesn't sound useful
for the target audience this documented is aims at. IIUC from the
irc discussion, it's a side product of an autoconf check for working
autoconf. Knowing where the .mo files end up sounds useful though.
--
Pedro Alves