public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "fweimer at redhat dot com" <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: Mon, 19 Sep 2022 07:27:44 +0000	[thread overview]
Message-ID: <bug-29583-131-PcPXdBHMkt@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 #1 from Florian Weimer <fweimer at redhat dot com> ---
Patch posted:

[PATCH] gconv: Use 64-bit interfaces in gconv_parseconfdir (bug 29583)
<https://sourceware.org/pipermail/libc-alpha/2022-September/142060.html>

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2022-09-19  7:27 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 [this message]
2022-09-20 10:13 ` fweimer at redhat dot com
2022-09-20 19:13 ` deller at gmx dot de
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-PcPXdBHMkt@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).