public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "deller at gmx dot de" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug build/29583] iconv failures on 32bit platform due to missing large file support
Date: Tue, 20 Sep 2022 19:13:15 +0000 [thread overview]
Message-ID: <bug-29583-131-W0vTeR3Tls@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29583-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=29583
--- Comment #3 from Helge Deller <deller at gmx dot de> ---
On 9/20/22 12:13, fweimer at redhat dot com wrote:
> https://sourceware.org/bugzilla/show_bug.cgi?id=29583
>
> Florian Weimer <fweimer at redhat dot com> changed:
>
> What |Removed |Added
> ----------------------------------------------------------------------------
> Resolution|--- |FIXED
> Target Milestone|--- |2.37
> Status|ASSIGNED |RESOLVED
>
> --- Comment #2 from Florian Weimer <fweimer at redhat dot com> ---
> Fixed for 2.37 via:
>
> commit f97905f24631097af325d6a231093071c3077a5f
> Author: Florian Weimer <fweimer@redhat.com>
> Date: Tue Sep 20 12:12:43 2022 +0200
>
> gconv: Use 64-bit interfaces in gconv_parseconfdir (bug 29583)
>
> It's possible that inode numbers are outside the 32-bit range.
> The existing code only handles the in-libc case correctly, and
> still uses the legacy interfaces when building iconv.
>
> Suggested-by: Helge Deller <deller@gmx.de>
>
> Please let us know if we should backport this anywhere.
Yes, could you please backport it to 2.34+ ?
I'm running on Debian/unstable and it has 2.34.
Thanks,
Helge
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2022-09-20 19:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-18 16:53 [Bug build/29583] New: " deller at gmx dot de
2022-09-18 17:07 ` [Bug build/29583] " danglin at gcc dot gnu.org
2022-09-19 6:59 ` fweimer at redhat dot com
2022-09-19 7:27 ` fweimer at redhat dot com
2022-09-20 10:13 ` fweimer at redhat dot com
2022-09-20 19:13 ` deller at gmx dot de [this message]
2022-09-21 12:13 ` fweimer at redhat dot com
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=bug-29583-131-W0vTeR3Tls@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@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).