| Summary: | build linux kernel version is used when cross-compiling | ||
|---|---|---|---|
| Product: | [Developer tools] valgrind | Reporter: | Michael Olbrich <michael.olbrich> |
| Component: | general | Assignee: | Julian Seward <jseward> |
| Status: | REPORTED --- | ||
| Severity: | normal | CC: | cpigat242, daniel.klauer, f.fainelli, tom |
| Priority: | NOR | ||
| Version First Reported In: | 3.7 SVN | ||
| Target Milestone: | --- | ||
| Platform: | Debian unstable | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: | make kernel version a autoconf cache variable | ||
Does it actually make any difference though? As far as I can see we don't use the kernel version for anything so as long as the kernel version on the build machine is something we recognise it shouldn't make any difference whether it matches the version on the target. Well in that case maybe the check should be removed. It's a bad idea to check for runtime dependencies at build time I agree, this check should be removed, or Michael's patch should be merged. I just hit this while building with a host kernel version 3.0.0 and targetting linux 2.6.x. |
Created attachment 62658 [details] make kernel version a autoconf cache variable `uname -r` is always used as linux kernel version. This is the incorrect when cross-compiling. The attached patch adds a cache variable, that can be set when cross-compiling, to define the correct kernel version.