I checked out head Sunday and now my attempt at building a kernel says:
ERROR: ctfconvert: failed to initialize DWARF: Unimplemented code at
[dwarf_init_attr(400)]
on every module it compiles (though it seems happy enough to keep
compiling). Should I just ignore this?-- George
On 2012-12-18 12:30, George Mitchell wrote:
I checked out head Sunday and now my attempt at building a kernel says:
ERROR: ctfconvert: failed to initialize DWARF: Unimplemented code at
[dwarf_init_attr(400)]
on every module it compiles (though it seems happy enough to keep
compiling). Should
a kernel says:
ERROR: ctfconvert: failed to initialize DWARF: Unimplemented code at
[dwarf_init_attr(400)]
on every module it compiles (though it seems happy enough to keep
compiling). Should I just ignore this?-- George Mitchell
This problem was fixed in libdwarf in r239872; did
On 2012-12-18 22:37, Ryan Stone wrote:
On Tue, Dec 18, 2012 at 7:15 AM, Dimitry Andric d...@freebsd.org
mailto:d...@freebsd.org wrote:
On 2012-12-18 12:30, George Mitchell wrote:
ERROR: ctfconvert: failed to initialize DWARF: Unimplemented code at
[dwarf_init_attr(400
On Tue, Dec 18, 2012 at 4:56 PM, Dimitry Andric d...@freebsd.org wrote:
The question is if ctfconvert (and dependencies) are rebuilt when you do
kernel-toolchain. Can you figure out if it runs ctfconvert from base?
Aha! You're right:
[rstone@rstone-laptop vll]make buildenv
Entering world
On 12/18/12 07:15, Dimitry Andric wrote:
On 2012-12-18 12:30, George Mitchell wrote:
I checked out head Sunday and now my attempt at building a kernel says:
ERROR: ctfconvert: failed to initialize DWARF: Unimplemented code at
[dwarf_init_attr(400)]
on every module it compiles (though it seems
