From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23866 invoked by alias); 13 Sep 2003 02:22:44 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 23853 invoked from network); 13 Sep 2003 02:22:44 -0000 Received: from unknown (HELO concert.shout.net) (204.253.184.25) by sources.redhat.com with SMTP; 13 Sep 2003 02:22:44 -0000 Received: from duracef.shout.net (duracef.shout.net [204.253.184.12]) by concert.shout.net (8.12.9/8.12.9) with ESMTP id h8D2MD9Q030113; Fri, 12 Sep 2003 21:22:13 -0500 Received: from duracef.shout.net (localhost [127.0.0.1]) by duracef.shout.net (8.12.9/8.12.9) with ESMTP id h8D2MDHK030219; Fri, 12 Sep 2003 21:22:13 -0500 Received: (from mec@localhost) by duracef.shout.net (8.12.9/8.12.9/Submit) id h8D2MCI5030218; Fri, 12 Sep 2003 22:22:12 -0400 Date: Sat, 13 Sep 2003 02:22:00 -0000 From: Michael Elizabeth Chastain Message-Id: <200309130222.h8D2MCI5030218@duracef.shout.net> To: zack@codesourcery.com Subject: Status of gcc/intl and src/intl? Cc: binutils@sources.redhat.com, gcc@gcc.gnu.org, gdb@sources.redhat.com X-SW-Source: 2003-09/txt/msg00180.txt.bz2 Hi Zack, I saw your message about an intl/ update: http://sources.redhat.com/ml/binutils/2003-07/msg00032.html Here's my story. Gdb has a build problem, PR gdb/857, which is about intl/Makefile.in and the lack of a few files in the 'distclean' rule. I started working on this and I noticed that gcc/intl is a lot newer than src/intl. My plan is to add a few lines of kludgery to the top level src-release file and not touch src/intl/Makefile.in at all, on the grounds that src/intl is about to get a big upgrade soon anyways. The specific kludgery is a couple of lines like 'rm -f intl/config.cache' and 'rm -f intl/stamp-h'. I think this will be benign if an upgrade happens. I just wanna make sure that my plan is okay in light of whatever's going on with src/intl these days. Can you comment on the status of that? Thanks, Michael C