From owner-freebsd-toolchain@FreeBSD.ORG Wed Sep 10 17:24:19 2014 Return-Path: Delivered-To: freebsd-toolchain@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B8737F57; Wed, 10 Sep 2014 17:24:19 +0000 (UTC) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id BBFF31D3; Wed, 10 Sep 2014 17:24:18 +0000 (UTC) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id UAA22498; Wed, 10 Sep 2014 20:24:17 +0300 (EEST) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1XRlcu-000N2y-Tz; Wed, 10 Sep 2014 20:24:16 +0300 Message-ID: <54108909.7050908@FreeBSD.org> Date: Wed, 10 Sep 2014 20:23:21 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.0 MIME-Version: 1.0 To: freebsd-toolchain@FreeBSD.org, freebsd-dtrace@FreeBSD.org Subject: WITH_CTF vs -g Content-Type: text/plain; charset=X-VIET-VPS Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Sep 2014 17:24:19 -0000 In my opinion WITH_CTF should imply -g in CFLAGS otherwise, as far as I can see, there is nothing to generate CTF data from. Forcing an end-user to remember to additionally pass -g is not nice. Also, I think that we can always have -g in CTFFLAGS, because the stripping step takes care of the original DWARF data in any case. But I am not 100% sure about this. What do you think? Thanks! -- Andriy Gapon