From owner-freebsd-arch@freebsd.org  Thu Dec  3 09:29:22 2015
Return-Path: <owner-freebsd-arch@freebsd.org>
Delivered-To: freebsd-arch@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 39C84A3CCDD
 for <freebsd-arch@mailman.ysv.freebsd.org>;
 Thu,  3 Dec 2015 09:29:22 +0000 (UTC)
 (envelope-from erik+lists@cederstrand.dk)
Received: from mailrelay5.public.one.com (mailrelay5.public.one.com
 [91.198.169.199])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 718A814F3
 for <freebsd-arch@freebsd.org>; Thu,  3 Dec 2015 09:29:21 +0000 (UTC)
 (envelope-from erik+lists@cederstrand.dk)
X-HalOne-Cookie: 6c000cc0dac24553dbd60456d335038214bcaeb8
X-HalOne-ID: 2a548f93-99a0-11e5-be90-b82a72d03b9b
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple;
 d=cederstrand.dk; s=20140924;
 h=from:subject:date:message-id:to:cc:mime-version:content-type:
 content-transfer-encoding:in-reply-to:references;
 bh=NPgf0CYPfvuXpBFThBClrTAqx/+BMzwZDTLQt7sNSQI=;
 b=dPcnfimEwJi/2kISzzIfvRCNtnSx7BQeYs4/bOqZPATTGtX64UGVGKrQJb+1uBqH28Gow84iw4SjJ
 o+fRs+hHJ00odEREcp2UoB1CrvmxX3OugJVCJY/s3ei1dH2ZvgABLC/7UksC7Ufiaynlqq2Hz76G1C
 1mfoi+eTssbI1ye8=
Received: from [192.168.1.76] (unknown [217.157.7.221])
 by smtpfilter2.public.one.com (Halon Mail Gateway) with ESMTPSA;
 Thu,  3 Dec 2015 09:28:08 +0000 (GMT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 9.1 \(3096.5\))
Subject: Re: Removing build metadata, for reproducible kernel builds
From: Erik Cederstrand <erik+lists@cederstrand.dk>
In-Reply-To: <1920964.NJpSim6qZF@ralph.baldwin.cx>
Date: Thu, 3 Dec 2015 10:28:10 +0100
Cc: freebsd-arch@freebsd.org,
 Ed Maste <emaste@freebsd.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <B95FC2E1-FCBD-48F6-854C-730906590AE5@cederstrand.dk>
References: <CAPyFy2AYeN9XNg=b0=JMWDC9ctWarfiZ-5zQorOPhguDJgxYpg@mail.gmail.com>
 <1920964.NJpSim6qZF@ralph.baldwin.cx>
To: John Baldwin <jhb@freebsd.org>
X-Mailer: Apple Mail (2.3096.5)
X-BeenThere: freebsd-arch@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: Discussion related to FreeBSD architecture <freebsd-arch.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-arch>,
 <mailto:freebsd-arch-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-arch/>
List-Post: <mailto:freebsd-arch@freebsd.org>
List-Help: <mailto:freebsd-arch-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-arch>,
 <mailto:freebsd-arch-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Dec 2015 09:29:22 -0000


> Den 2. dec. 2015 kl. 21.03 skrev John Baldwin <jhb@freebsd.org>:
>=20
> As I noted in the review, this will break kgdb -n (and possibly =
crashinfo,
> less certain about that).  Keeping the path (which should not vary if =
you
> build out of the same tree) will be sufficient to let kgdb -n still =
work
> (though it may need some changes to recognize both formats).

Would it be feasible to include the relative build path instead of the =
absolute path? I seem to remember patches floating around for the =
__FILE__ macro, but I don't know if (k)gdb can work with relative paths.

Erik=