From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 88501 invoked by alias); 25 Oct 2017 08:54:06 -0000 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 Received: (qmail 85540 invoked by uid 89); 25 Oct 2017 08:54:04 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.7 required=5.0 tests=AWL,BAYES_00,RCVD_IN_BRBL_LASTEXT,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=no version=3.3.2 spammy=H*r:sk:gdb@sou X-HELO: smtp.eu.adacore.com Received: from mel.act-europe.fr (HELO smtp.eu.adacore.com) (194.98.77.210) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Wed, 25 Oct 2017 08:54:03 +0000 Received: from localhost (localhost [127.0.0.1]) by filtered-smtp.eu.adacore.com (Postfix) with ESMTP id 406E68222C for ; Wed, 25 Oct 2017 10:54:01 +0200 (CEST) Received: from smtp.eu.adacore.com ([127.0.0.1]) by localhost (smtp.eu.adacore.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HRyfh7MjU-RE for ; Wed, 25 Oct 2017 10:54:01 +0200 (CEST) Received: from Xaviers-MacBook-Pro.local (unknown [10.10.8.7]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.eu.adacore.com (Postfix) with ESMTPSA id C93008137E for ; Wed, 25 Oct 2017 10:54:00 +0200 (CEST) To: gdb@sourceware.org From: Xavier Roirand Subject: Faillure when adding file to ALL_64_TARGET_OBS in Makefile.in Message-ID: Date: Wed, 25 Oct 2017 08:54:00 -0000 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.4.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes X-SW-Source: 2017-10/txt/msg00068.txt.bz2 Hi, For a test, I've created a new aarch64 file specific to a runtime, and I'm trying to add this file to ALL_64_TARGET_OBS macro in Makefile.in in GDB. This step is ok but when I'm configuring GDB then I have to specifiy: configure.... --enable-targets=all --enable-64-bit-bfd in order to have my new aarch64 added during the build. Of course, adding --enable-targets=all make my GDB executable size increasing from 30 Mb to 105 Mb. Did I missed something here or is it the only way to have my new aarch64 runtime specific file taken in account ? Thanks.