public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Adhemerval Zanella <adhemerval.zanella@linaro.org>
To: Florian Weimer <fweimer@redhat.com>
Cc: Adhemerval Zanella via Libc-alpha <libc-alpha@sourceware.org>
Subject: Re: [PATCH v2] Use LFS and 64 bit time for installed programs (BZ #15333)
Date: Wed, 29 Dec 2021 10:08:51 -0300	[thread overview]
Message-ID: <4b222a15-5249-98a2-4aba-117e20489863@linaro.org> (raw)
In-Reply-To: <87h7arbnc1.fsf@oldenburg.str.redhat.com>



On 29/12/2021 09:35, Florian Weimer wrote:
> * Adhemerval Zanella:
> 
>> On 28/12/2021 17:37, Florian Weimer wrote:
>>> * Adhemerval Zanella via Libc-alpha:
>>>
>>>> The installed programs are built with a combination of different
>>>> values for MODULE_NAME, as below.  To enable both Long File Support
>>>> and 64 bt time, -D_TIME_BITS=64 -D_FILE_OFFSET_BITS=64 is added for
>>>> nonlibi, nscd, lddlibc4, libresolv, ldconfig, locale_programs,
>>>> iconvprogs, libnss_files, libnss_compat, libnss_db, libnss_hesiod,
>>>> libutil, libpcprofile, and libSegFault.
>>>
>>> -D_TIME_BITS=64 does not work for building glibc because the internal
>>> aliases such as __fstat64 do not follow _TIME_BITS and are hard-wired to
>>> 32-bit time.  A symptom is a broken ldconfig, e.g.:
>>>
>>> $ elf/ldconfig -p
>>> elf/ldconfig: mmap of cache file failed.
>>> : Invalid argument
>>
>> I think the real problem is the usage of internal symbol in installed
>> binaries, it works for LFS stat because they are either redirected to
>> compat xstat ones or __stat (which I think it is also error prone).
>>
>> I am fixing it by using the default stat names, installed programs 
>> should not use proper LFS and time64.
> 
> They need to be able to deal with 64-bit inode numbers, though.

Oops, I meant that installed programs *should* use proper LFS and time64
(using default stat names accomplish it for static linking).

      reply	other threads:[~2021-12-29 13:08 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-22 17:27 Adhemerval Zanella
2021-12-14 19:35 ` DJ Delorie
2022-01-12 14:13   ` Stefan Liebler
2022-01-12 14:44     ` Adhemerval Zanella
2022-01-12 16:07       ` Stefan Liebler
2021-12-28 20:37 ` Florian Weimer
2021-12-29 11:59   ` Adhemerval Zanella
2021-12-29 12:35     ` Florian Weimer
2021-12-29 13:08       ` Adhemerval Zanella [this message]

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=4b222a15-5249-98a2-4aba-117e20489863@linaro.org \
    --to=adhemerval.zanella@linaro.org \
    --cc=fweimer@redhat.com \
    --cc=libc-alpha@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).