From owner-freebsd-questions@FreeBSD.ORG Wed Aug 22 18:15:44 2007 Return-Path: Delivered-To: questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 95D2416A420 for ; Wed, 22 Aug 2007 18:15:44 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx22.fluidhosting.com [204.14.89.5]) by mx1.freebsd.org (Postfix) with SMTP id 28AFC13C4A8 for ; Wed, 22 Aug 2007 18:15:43 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: (qmail 13397 invoked by uid 399); 22 Aug 2007 17:49:02 -0000 Received: from localhost (HELO slave.dougb.net) (dougb@dougbarton.us@127.0.0.1) by localhost with ESMTP; 22 Aug 2007 17:49:02 -0000 X-Originating-IP: 127.0.0.1 Date: Wed, 22 Aug 2007 10:49:00 -0700 (PDT) From: Doug Barton To: "Dan Mahoney, System Admin" In-Reply-To: <20070821135923.Q64507@prime.gushi.org> Message-ID: References: <20070821135923.Q64507@prime.gushi.org> X-message-flag: Outlook -- Not just for spreading viruses anymore! X-OpenPGP-Key-ID: 0xD5B2F0FB Organization: http://www.FreeBSD.org/ MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=us-ascii; format=flowed Cc: questions@freebsd.org Subject: Re: Building UNSTRIPPED binaries in ports? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Aug 2007 18:15:44 -0000 On Tue, 21 Aug 2007, Dan Mahoney, System Admin wrote: > Hello, > > I am encountering a bug with named-9.4.1-P1 that I am attempting to work with > ISC on, that I have built from ports (dns/bind94). That's great, every little bit helps. :) You might also be interested to know that they have a new beta out for 9.4.2. ftp://ftp.isc.org/isc/bind9/9.4.2b1/bind-9.4.2b1.tar.gz You should probably download that and take a look at the changelog to see if your issues are covered. > However, I need a non-stripped version of the binary to get a backtrace. > I can't "roll my own" binary because it may be related to some way that > the port is built so I need to maintain a similar build environment. I purposely do not do anything exotic with the port, so I doubt that's related. However, you can easily replicate the port's build environment by doing 'make config ; make -V CONFIGURE_ARGS' then running configure with that output and building it yourself. Of course, the advice you got on WITH_DEBUG is also good if you want to use the port anyway. hth, Doug -- This .signature sanitized for your protection