amd64/165845: Unable to build kernel on 8.2-STABLE

Justin Smith freebsd.users at gmail.com
Thu Mar 8 10:50:13 UTC 2012


The following reply was made to PR amd64/165845; it has been noted by GNATS.

From: Justin Smith <freebsd.users at gmail.com>
To: Peter Wemm <peter at wemm.org>
Cc: freebsd-gnats-submit at freebsd.org
Subject: Re: amd64/165845: Unable to build kernel on 8.2-STABLE
Date: Thu, 8 Mar 2012 18:41:35 +0800

 > This is some sort of user error and a problematic bug report as well.
 >
 > First.. please don't use pastebin type things that expire. =A0When the
 > context goes away in 31 days, the bug report becomes meaningless and
 > loses its search reference value. =A0In a month or two, somebody might
 > have the same problem and if there's a documented solution here then
 > the search engines will never find the context to give them the
 > solution.
 >
 > Second.. =A0 The last error you hit was:
 > ld =A0-d -warn-common -r -d -o aac.ko.debug aac.o aac_pci.o aac_disk.o aa=
 c_cam.o
 > -L VERSION -g -o aac.ko.debug aac.o aac_pci.o aac_disk.o aac_cam.o
 > -L:No such file or directory
 >
 > The only things that look like that are in share/mk/sys.mk:
 > # C Type Format data is required for DTrace
 > CTFFLAGS =A0 =A0 =A0 =A0?=3D =A0 =A0 =A0-L VERSION"
 >
 > And that's used with a SYSTEM_CTFMERGE in the kernel makefiles.
 >
 > So, what you've done is partially disabled dtrace or CDDL or the CTF
 > flags. =A0Or you've got a stale /usr/obj/* tree. =A0Or got stray, stale
 > build files in your source tree.
 >
 > This is an environmental issue on your end in some way. =A0(I don't mean
 > the $ENV variables.. It is something else.)
 >
 > --
 > Peter Wemm - peter at wemm.org; peter at FreeBSD.org; peter at yahoo-inc.com; KI6F=
 JV
 > "All of this is for nothing if we don't go to the stars" - JMS/B5
 > "If Java had true garbage collection, most programs would delete
 > themselves upon execution." -- Robert Sewell
 
 Yup, I removed DTrace support from kernel and make.conf. It works now.
 I guess I need DTrace support, what do I do to fix it.


More information about the freebsd-amd64 mailing list