Re: xnu-1228.7.58 build failure
Re: xnu-1228.7.58 build failure
- Subject: Re: xnu-1228.7.58 build failure
- From: Michael Reeves <email@hidden>
- Date: Wed, 8 Oct 2008 09:43:14 -0400
It terminates with the fallowing error:
/usr/bin/lipo: can't open replacement file: /private/var/tmp/xnu/
xnu-1228.7.58.obj/RELEASE_PPC/./mach_kernel.sys.dSYM/./Contents/
Resources/DWARF//mach_kernel.sys (No such file or directory)
make[2]: *** [/private/var/tmp/xnu/xnu-1228.7.58.sym/mach_kernel]
Error 1
make[2]: *** Waiting for unfinished jobs....
WARNING: ctfmerge: Can't read input file /private/var/tmp/xnu/
xnu-1228.7.58.obj/RELEASE_PPC/*/RELEASE/*.*o.ctf: No such file or
directory
ERROR: ctfmerge: Some input files were inaccessible
Removing /private/var/tmp/xnu/xnu-1228.7.58.obj/RELEASE_PPC/./
mach_kernel.ctfsys
/usr/bin/lipo: can't open replacement file: /private/var/tmp/xnu/
xnu-1228.7.58.obj/RELEASE_PPC/./mach_kernel.ctfsys (No such file or
directory)
make[2]: *** [/private/var/tmp/xnu/xnu-1228.7.58.root/mach_kernel]
Error 1
make[1]: *** [build_install] Error 2
make: *** [install] Error 2
The ctfconvert error is the only other error in the build log. Looking
in resulting build directory reveals that the make seems to using an
in correct path for mach_kernel.sys which is at /private/var/tmp/xnu/
xnu-1228.7.58.obj/RELEASE_PPC/ . The file mach_kernel.sys.dSYM exits
only in private/var/tmp/xnu/xnu-1228.7.58.sym and does not contain
mach_kernel.sys but instead has mach_kernel at the same relitive
location within the package. I will investigate further. I wanted to
make sure the ctfconvert error was symptomatic of something else.
On Oct 8, 2008, at 1:12 AM, nawcom wrote:
is that error killing the entire build process? ctfconvert is only
needed for dtrace support in the kernel afaik. mv /usr/local/bin/
ctfconvert /usr/local/bin/ctfconvert.bak or however you want to hide
it if it's causing issues. it should report that cftconvert is
missing and will report it and continue over it whenever the
makefile tries to use it. that will help you find out what the real
issue is, if it isn't directly related to it.
-Ben
Shantonu Sen wrote:
ctfconvert is never fatal to the overall build. Your issue is
somewhere else. Please find the compiler invocation error in your
build log
Shantonu
Sent from my MacBook
On Oct 4, 2008, at 8:10 PM, Michael Reeves wrote:
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-kernel mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden