From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 5283E3858419; Sat, 3 Sep 2022 21:15:57 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 5283E3858419 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1662239757; bh=eR2pDPf8PIYXG7aa9E8ZYjJ+k4agKTfS4mIAy8wcMUs=; h=From:To:Subject:Date:In-Reply-To:References:From; b=MR1x6PH+3h3VLCq8OSinwfD8Kdw1evYZTMLqZCUCxRV7DQ/6373GN0TH7VvinKsQS j4dHfHe+Do3A2k8JY6yJNDILjTqHdl/x2ohOPOviCEwwbyo2VZ/x2NfXi4Cireqmna unjp8Zg2sPX1RYLZJJTvdXUR47PR2dNmC4A/Mc1s= From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug cli/29315] Completion warning: could not convert ... from the host encoding (ANSI_X3.4-1968) to UTF-32 Date: Sat, 03 Sep 2022 21:15:56 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: cli X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tromey at sourceware dot org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://sourceware.org/bugzilla/show_bug.cgi?id=3D29315 --- Comment #2 from Tom Tromey --- (In reply to Patrick Monnerat from comment #1) > In the mingw context, current code conditionals cause libiconv to be > replaced by a minimal phony_iconv that does not support such conversions. > These conditionals were implemented to make sure libiconv implements UTF32 > and fail on mingw because the wchar_t is 16-bit wide and the installed > libiconv is not the Bruno Haible's one. See PHONY_ICONV in gdb/gdb_wchar.= h. Are there any defines in the mingw libiconv headers that could be used to detect this situation? E.g., for Haible's we use _LIBICONV_VERSION. Anyway I'd be curious to know exactly which situation makes gdb decide not to use iconv in your configuration. > @maciej: is your context similar (no Haible's libiconv or too old and no > ISO-10646 support) ? Ideally this path shouldn't even be taken. However it may be hard to avoid due to a combination of factors including multi-language searches. One question I had is whether the required iconv converters are installed. It sounds like he's using glibc... > @tom: as you're the commit's author, what is your opinion ? In the past we couldn't assume host iconv was any good. Solaris in particular was broken (I forget how). I suppose I'm ok with changing this decision though it might be good to find out how Solaris is doing. --=20 You are receiving this mail because: You are on the CC list for the bug.=