From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19899 invoked by alias); 28 Nov 2011 23:19:30 -0000 Received: (qmail 19878 invoked by uid 22791); 28 Nov 2011 23:19:27 -0000 X-SWARE-Spam-Status: No, hits=-2.4 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW X-Spam-Check-By: sourceware.org Received: from mail-pz0-f49.google.com (HELO mail-pz0-f49.google.com) (209.85.210.49) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 28 Nov 2011 23:19:14 +0000 Received: by pzk6 with SMTP id 6so5842510pzk.8 for ; Mon, 28 Nov 2011 15:19:14 -0800 (PST) MIME-Version: 1.0 Received: by 10.68.72.103 with SMTP id c7mr57183720pbv.1.1322522353990; Mon, 28 Nov 2011 15:19:13 -0800 (PST) Received: by 10.68.25.4 with HTTP; Mon, 28 Nov 2011 15:19:13 -0800 (PST) Date: Mon, 28 Nov 2011 23:19:00 -0000 Message-ID: Subject: build failure in native gdb with crosstool-ng-1.13.1 on openSUSE 12.1 From: Trevor Woerner To: crossgcc@sourceware.org Content-Type: text/plain; charset=ISO-8859-1 X-IsSubscribed: yes Mailing-List: contact crossgcc-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: crossgcc-owner@sourceware.org X-SW-Source: 2011-11/txt/msg00197.txt.bz2 Hi Yann, I recently upgraded to the latest openSUSE 12.1 release and discovered that crosstool-NG has trouble building native gdb. In scripts/build/debug/300-gdb.sh around line 249 is found: native_extra_config+=("--with-curses") # There's no better way to tell gdb where to find -lcurses... :-( gdb_native_CFLAGS+=("-I${CT_BUILD_DIR}/static-target/include") gdb_native_CFLAGS+=("-L${CT_BUILD_DIR}/static-target/lib") In previous builds (i.e. openSUSE 11.4, etc) the lib directory (as specified) exists. With my builds on openSUSE 12.1 this directory doesn't exist, but ${CT_BUILD_DIR}/static-target/lib64 does. The native gdb fails during the run of one of the many sub-directory ./configure scripts saying "no termcap library found". Manually tweaking the above to say "lib64" allows the native gdb build to succeed (but, obviously, is not a general solution). The build then fails a little later (during cleanup, stripping all binaries) but I haven't looking into that yet to provide much information. Best regards, Trevor -- For unsubscribe information see http://sourceware.org/lists.html#faq