On 11/29/2010 04:07 PM, Arun Sharma wrote: > On Mon, Nov 8, 2010 at 5:16 PM, Zachary T Welch <[email protected]> > wrote: >> This series includes additional cleaning of the libunwind build system. > > There is a new test failure after applying the patch set: > > ERROR: Extraneous symbols: > 000000000000b143 T _Ux86_64_handle_signal_frame > 000000000000b11f T _Ux86_64_is_signal_frame > FAILURE: Detected 1 errors > FAIL: run-check-namespace > > Hopefully an easy one to fix.
I never saw it during my original testing, but I somehow managed to reproduce the above output on my x86_64 test box. Unfortunately, the problem disappeared when I tried to use 'git bisect' in order to find the problematic patch. Subsequently, I have been unable to reproduce this problem again, so I am curious whether we experienced some kind of transient build failure. I think the nature of this series could easily explain such a glitch. Incidentally, I have yet to resolve my linker problem on x86, but I had to put it aside when the answer failed to make itself apparent. AFAIK, that lingering issue only disqualifies the last patch of the series, assuming that this present issue turns out to be user error. -- Zach Welch CodeSourcery [email protected] (650) 331-3385 x743 _______________________________________________ Libunwind-devel mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/libunwind-devel
