From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 32599 invoked by alias); 6 Dec 2012 12:13:23 -0000 Received: (qmail 32589 invoked by uid 22791); 6 Dec 2012 12:13:21 -0000 X-SWARE-Spam-Status: No, hits=-4.7 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,KHOP_RCVD_TRUST,KHOP_THREADED,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_YE X-Spam-Check-By: sourceware.org Received: from mail-bk0-f41.google.com (HELO mail-bk0-f41.google.com) (209.85.214.41) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 06 Dec 2012 12:13:18 +0000 Received: by mail-bk0-f41.google.com with SMTP id jg9so2887009bkc.0 for ; Thu, 06 Dec 2012 04:13:16 -0800 (PST) Received: by 10.204.157.26 with SMTP id z26mr490589bkw.101.1354795996572; Thu, 06 Dec 2012 04:13:16 -0800 (PST) MIME-Version: 1.0 Received: by 10.205.32.12 with HTTP; Thu, 6 Dec 2012 04:12:36 -0800 (PST) In-Reply-To: <201212061051.qB6Ap9CU012302@new.toad.com> References: <201212061051.qB6Ap9CU012302@new.toad.com> From: Hui Zhu Date: Thu, 06 Dec 2012 12:13:00 -0000 Message-ID: Subject: Re: Request change name of function lookup_enum in libbabeltrace to make GDB use this lib To: Tom Tromey Cc: gdb@sourceware.org, John Gilmore Content-Type: text/plain; charset=ISO-8859-1 X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2012-12/txt/msg00024.txt.bz2 On Thu, Dec 6, 2012 at 6:51 PM, John Gilmore wrote: > I suggest that it's best if both GDB and Libbabeltrace change the name > of lookup_enum. That way you'll be able to compile any version of GDB > with any version of libbabeltrace (fixed or unfixed) and all four > combinations will work except "unfixed GDB" and "unfixed > libbabeltrace"). > > If you just change it in the library, gdb stops building on machines that > have the old library. > > If you just change it in GDB, older gdb's won't be compatible with > newer libraries. Hmm, but older gdb's don't link with that library > anyway. So you might as well just fix it in GDB; that works for all > cases. > > John Thanks, John. Hi Tom, What do you think about the suggest from John? Thanks, Hui