On 04/20/2016 03:41 PM, Nathan Bibb wrote:
Hi Alz,
On Sat, Apr 16, 2016 at 2:58 PM, Nathan Bibb <[email protected]
<mailto:[email protected]>> wrote:
On Apr 16, 2016 8:42 AM, "Alz" <[email protected]
<mailto:[email protected]>> wrote:
> There is an assert in cacheinfo.c code for any guessed Intel CPU. Your
build seems to get here and fail.
>
> You can try a quick test. Before compiling glibc, modify the code
to prevent the assert to fail in your machine. Add a line in:
>
>
Thanks for the advice. I will try out the code change and see what
happens. I have done a little Python scripting, but I've never
written anything in C so hopefully I don't make things worse :)
If that gives no insight, I will check out how to set the CFLAGS
correctly.
I made the exact change you indicated, and 'make check' ran its entire
course. The summary was:
40 FAIL
2308 PASS
84 XFAIL
2 XPASS
I went ahead with 'make install', and it seemed to go well. Very
interesting. I am going to keep moving forward and see if this ends up
being a problem later on, but so far so good.
Thanks for your help!
Nathan
Hi Nathan, I'm glad to hear that!
Keep in mind that the problem is not solved, just "avoided". You now
have a patched Glibc and no clear explanation about the reason why...
However, it turns out that something similar was an actual patch that
Debian [1] and Suse [2] where using for the Valgrind issue that akh
pointed out. Looks like this was used arround glibc-2.21 and later
discarded when Valgrind "solved" the issue.
If you have spare time, reviewing those 40 fails in the tests could
provide you more information. Who knows. Maybe this is something about
your specific system, maybe you found an issue in Glibc for such old CPUs.
Regards.
Alz.
[1]
https://sources.debian.net/patches/glibc/2.21-4/i386/local-cpuid-level2.diff/
[2]
https://build.opensuse.org/package/view_file?file=x86-cpuid-level2.patch&package=glibc&project=openSUSE%3AFactory&rev=2ff3e72112056f23a49e21f6b5059492
--
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
Do not top post on this list.
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
http://en.wikipedia.org/wiki/Posting_style
