FX wrote:
I’m building with binutils 2.17.50.0.6, which is a bit old but I cannot find
any mention of needing later binutils on the installation notes.
Is bootstrap broken, or am I missing something?
Second build, this time with trunk binutils. Still fails in libsanitizer at
stage1, this time with:
../../../../trunk/libsanitizer/sanitizer_common/sanitizer_platform_limits_linux.cc:25:30:
fatal error: linux/perf_event.h: No such file or directory
I run a Linux 2.6.18, with kernel headers installed. Are there stricter
requirements on the linux version in GCC? Where is it documented?
I don’t remember that bootstraping used to be so hard :(
In principle, you could try --disable-libsanitizer
--disable-target-libsanitizer but I am not sure whether that works, a
fortnight ago, Janne remarked at #gcc that it didn't seem to work –
maybe you have more luck.
Your Linux 2.6.18 is already quite old (September 2007) thus I wouldn't
be surprised that that's the reason. According to
https://github.com/torvalds/linux/commit/cdd6c482c9ff9c55475ee7392ec8f672eddb7be6
, the file "perf_event.h" was renamed from "perf_counter.h" in September
2009 (2.6.32?).
Regarding Binutils: "GNU binutils – Necessary in some circumstances,
optional in others. See the host/target specific instructions for your
platform for the exact requirements." Thus, that's kind of documented at
http://gcc.gnu.org/install/prerequisites.html – even if it is not that
helpful. – I don't know how old your binutils were.
Actually, gcc20 (Debian 6/Squeeze) of the compile farm has Linux kernel
2.6.32, binutils 2.20.1 and glibc 2.11.3; those seem to be (just)
sufficient.
Tobias
