Date: Thu, 3 Dec 2015 10:28:10 +0100 From: Erik Cederstrand <erik+lists@cederstrand.dk> To: John Baldwin <jhb@freebsd.org> Cc: freebsd-arch@freebsd.org, Ed Maste <emaste@freebsd.org> Subject: Re: Removing build metadata, for reproducible kernel builds Message-ID: <B95FC2E1-FCBD-48F6-854C-730906590AE5@cederstrand.dk> In-Reply-To: <1920964.NJpSim6qZF@ralph.baldwin.cx> References: <CAPyFy2AYeN9XNg=b0=JMWDC9ctWarfiZ-5zQorOPhguDJgxYpg@mail.gmail.com> <1920964.NJpSim6qZF@ralph.baldwin.cx>
next in thread | previous in thread | raw e-mail | index | archive | help
> 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=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?B95FC2E1-FCBD-48F6-854C-730906590AE5>