Date: Mon, 22 Oct 2012 09:40:39 -0400 From: John Baldwin <jhb@freebsd.org> To: freebsd-arch@freebsd.org Cc: meowthink <meowthink@gmail.com>, Brooks Davis <brooks@freebsd.org> Subject: Re: bsd.own.mk - just let WITHOUT_* take precedence Message-ID: <201210220940.39281.jhb@freebsd.org> In-Reply-To: <20121021094151.GC27212@lor.one-eyed-alien.net> References: <20121007001423.9878F58094@chaos.jnpr.net> <1350794580507-5753746.post@n5.nabble.com> <20121021094151.GC27212@lor.one-eyed-alien.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sunday, October 21, 2012 5:41:51 am Brooks Davis wrote: > On Sat, Oct 20, 2012 at 09:43:00PM -0700, meowthink wrote: > > I encouraged the same issue when build with dtrace-enabled kernconf. > > I do think it's a problem of Makefile.inc1 which manually defined these > > NO_CTFs. By Simon's hack on bsd.own.mk, the build process goes on, but not > > as before. For instance, /libexec/ld-elf.so.1 contains CTF data but > > /libexec/ld-elf32.so.1 not (it contains CTF data before MFC r228158). At > > least all 32-bit libraries on amd64 are built without CTF. > > Though didn't use userland dtrace(esp. with 32-bit compat), I doubt this > > somehow breaks such functionalities. > > > > Also cc'ed jhb & fjoe who brought us this change. > > I've MFCd r228120 which allows WITH_CTF to be set in make.conf. > It looks like there may be another bug effecting the setting of > CTFCONVERT_CMD. I had this change as a question mark to merge in my list, thanks. Can you also merge it to 8? -- John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201210220940.39281.jhb>