From owner-freebsd-current@FreeBSD.ORG Sun Aug 8 18:49:45 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 401BA16A4CF; Sun, 8 Aug 2004 18:49:45 +0000 (GMT) Received: from gravy.kishka.net (pcp04097789pcs.neave01.pa.comcast.net [68.81.192.94]) by mx1.FreeBSD.org (Postfix) with ESMTP id 945BB43D39; Sun, 8 Aug 2004 18:49:44 +0000 (GMT) (envelope-from bryan@kishka.net) Received: from gravy.kishka.net (gravy.kishka.net [192.168.1.2]) by gravy.kishka.net (8.13.1/8.13.1) with ESMTP id i78InhTP001186; Sun, 8 Aug 2004 14:49:43 -0400 (EDT) (envelope-from bryan@kishka.net) Date: Sun, 8 Aug 2004 14:49:43 -0400 (EDT) From: Bryan Liesner To: Robert Watson In-Reply-To: Message-ID: <20040808144250.S1181@gravy.kishka.net> References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed cc: kan@freebsd.org cc: freebsd-current@freebsd.org Subject: Re: INCLUDE_CONFIG_FILE doesn't work anymore X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Aug 2004 18:49:45 -0000 On Sun, 8 Aug 2004, Robert Watson wrote: > > On Sun, 8 Aug 2004, Conrad J. Sabatier wrote: > >> Including "options INCLUDE_CONFIG_FILE", while it doesn't break the >> kernel build, no longer actually seems to include the config file in the >> kernel. Using the magic "strings -n 3 ..." incantation returns only a >> couple of lines of gibberish now. > > It could be that gcc 3.4 is cleverly optimization out the unused symbols? > The below works for me. I've been using it for quite some time now, definitely before gcc 3.4. Something changed a while back and I just adapted. ========================================================================== #!/bin/sh # the perl re now includes a "not underscore" for the fourth character # since a couple of bogus strings match the old three underscore pattern. # You have to put the character back with a back reference, or lose the # first character of the kernel config string. strings -n3 /boot/kernel/kernel | perl -ne 'print if s/^___([^_])/$1/' ========================================================================= -Bryan