From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8387 invoked by alias); 15 Apr 2009 15:08:25 -0000 Received: (qmail 8351 invoked by uid 22791); 15 Apr 2009 15:08:24 -0000 X-SWARE-Spam-Status: No, hits=-2.3 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (66.187.233.31) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 15 Apr 2009 15:08:17 +0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.13.8/8.13.8) with ESMTP id n3FF8Fpx023939 for ; Wed, 15 Apr 2009 11:08:15 -0400 Received: from ns3.rdu.redhat.com (ns3.rdu.redhat.com [10.11.255.199]) by int-mx1.corp.redhat.com (8.13.1/8.13.1) with ESMTP id n3FF8FiP024509 for ; Wed, 15 Apr 2009 11:08:15 -0400 Received: from opsy.redhat.com (vpn-12-183.rdu.redhat.com [10.11.12.183]) by ns3.rdu.redhat.com (8.13.8/8.13.8) with ESMTP id n3FF8Eb4007123; Wed, 15 Apr 2009 11:08:15 -0400 Received: by opsy.redhat.com (Postfix, from userid 500) id 2CF9250830B; Wed, 15 Apr 2009 09:08:14 -0600 (MDT) To: Eli Zaretskii Cc: gdb-patches@sources.redhat.com Subject: Re: Configuring gdb_wchar.h References: <8363hboz5x.fsf@gnu.org> <833acbo32k.fsf@gnu.org> <83myajma7a.fsf@gnu.org> <83iql7m7r1.fsf@gnu.org> <83hc0rm1mh.fsf@gnu.org> <8363h6mdue.fsf@gnu.org> From: Tom Tromey Reply-To: Tom Tromey Date: Wed, 15 Apr 2009 15:08:00 -0000 In-Reply-To: <8363h6mdue.fsf@gnu.org> (Eli Zaretskii's message of "Wed\, 15 Apr 2009 13\:05\:29 +0300") Message-ID: User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.2 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2009-04/txt/msg00306.txt.bz2 >>>>> "Eli" == Eli Zaretskii writes: Eli> It builds fine, but the result seems strange to me: GDB now lists a Eli> long list of character sets in response to "set target-charset TAB". Eli> What happens is that find_charset_names correctly notices that Eli> "iconv -l" exited with a non-zero status (this is still with libiconv 1.7, Eli> where the -l switch is not supported), but then _initialize_charset Eli> falls back on using DEFAULT_CHARSET_NAMES, which seem to assume a Eli> glibc-based system. I rather expected the result to be that only a Eli> single target charset be available. Am I missing something? Should Eli> DEFAULT_CHARSET_NAMES be redefined on DJGPP to something different Eli> from what charset-list.h defines it? Your situation is somewhat odd. You have a working iconv but no way to get a list of available character sets. This ought to be a rare setup. In this case I chose to make gdb fall back on a fairly large built-in list. If you try pick a charset which your iconv cannot handle, gdb should give an error. Eli> I will upgrade to a newer libiconv and try with that, once the result Eli> for 1.7 is as expected (whatever that might be). I think the current result is as good as any other. Tom