Date: Thu, 30 Oct 2014 09:10:19 -0400 From: Ed Maste <emaste@freebsd.org> To: Steve Kargl <sgk@troutmask.apl.washington.edu> Cc: FreeBSD Current <freebsd-current@freebsd.org>, Steven Hartland <killing@multiplay.co.uk> Subject: Re: HEADS UP: Standalone kernel debug files moving out of /boot/kernel/ Message-ID: <CAPyFy2DZzxiZUdh4h1ETe2Ozbecnc2-yMOZArfzytCO6c2B=HQ@mail.gmail.com> In-Reply-To: <CAPyFy2AHyau5RhhZ628tbRQWa_smAYntHUrP0Ftd1EW8buZGXg@mail.gmail.com> References: <CAPyFy2APVUxpAztmWY-ux7gUZ7B8Qk65CLHV_fVYmxsazKgCPg@mail.gmail.com> <54511A7E.1020307@multiplay.co.uk> <CAPyFy2Bw9JH4w0iZ5hj2R1Ga9T4BZn_Z-8UBJ-jT6tmO%2Bi8VeA@mail.gmail.com> <20141030023224.GA42236@troutmask.apl.washington.edu> <CAPyFy2AHyau5RhhZ628tbRQWa_smAYntHUrP0Ftd1EW8buZGXg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 30 October 2014 09:07, Ed Maste <emaste@freebsd.org> wrote:
> On 29 October 2014 22:32, Steve Kargl <sgk@troutmask.apl.washington.edu> wrote:
>> On Wed, Oct 29, 2014 at 03:15:50PM -0400, Ed Maste wrote:
>>> On 29 October 2014 12:49, Steven Hartland <killing@multiplay.co.uk> wrote:
>>> > Hmm not sure I like this idea as it would make it more difficult to make a
>>> > copy / backup a kernel.
>>> >
>>> > ATM when I want to copy a kernel for debugging its a one liner, splitting
>>> > debug symbols off to /usr/lib would prevent this.
>>>
>>> To retain the current behaviour you can set DEBUGDIR= (i.e., empty),
>>> as the debug file install path is ${DESTDIR}${DEBUGDIR}${KODIR}.
>>
>> No, you can't.
>>
>> su root
>> cp -pR /boot/kernel /boot/good
>>
>> Where does DEBUGDIR enter the picture?
>
> In your kernel build configuration (src.conf or similar ways).
Oops, that should be "build / install configuration (src.conf or
similar)." That is, if you set DEBUGDIR= then the debug data will be
installed in the same directory as the kernel / binaries / libraries,
and everything will work as it does today.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAPyFy2DZzxiZUdh4h1ETe2Ozbecnc2-yMOZArfzytCO6c2B=HQ>