Date: Sun, 21 Oct 2012 04:41:51 -0500 From: Brooks Davis <brooks@freebsd.org> To: meowthink <meowthink@gmail.com> Cc: freebsd-arch@freebsd.org Subject: Re: bsd.own.mk - just let WITHOUT_* take precedence Message-ID: <20121021094151.GC27212@lor.one-eyed-alien.net> In-Reply-To: <1350794580507-5753746.post@n5.nabble.com> References: <20121007001423.9878F58094@chaos.jnpr.net> <20121008154853.GC23400@lor.one-eyed-alien.net> <20121008175206.5961858094@chaos.jnpr.net> <1350794580507-5753746.post@n5.nabble.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--R+My9LyyhiUvIEro Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable 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. >=20 > 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. -- Brooks --R+My9LyyhiUvIEro Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (FreeBSD) iD8DBQFQg8NeXY6L6fI4GtQRAu+2AKDDtyEGfA2ljw6KNlJ1rB4pXekjrQCeKFSJ YC+05Rn74jH0shjKBfhx18w= =LGc9 -----END PGP SIGNATURE----- --R+My9LyyhiUvIEro--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20121021094151.GC27212>