Re: Using vanilla kernels headers to do backport testing -- issueswith memcpy()

[Luis R. Rodriguez]

On Wed, Aug 8, 2012 at 5:43 AM, Ozan ÃaÄlayan <ozancag@xxxxxxxxx> wrote:
> On Tue, Aug 7, 2012 at 10:28 PM, Luis R. Rodriguez <mcgrof@xxxxxxxxxxxxx> wrote:

>> mcgrof@garbanzo ~/compat (git::master)$ objdump -T
>> /home/mcgrof/compat-ksrc/lib/modules/3.4.4-030404-generic/build/scripts/genksyms/genksyms

<-- snip -->

>> Bleh:
>>
>> 0000000000000000      DF *UND*  0000000000000000  GLIBC_2.14  memcpy

<-- snip -->

> Can't we just rebuild genksyms in compat? I already have glibc 2.15 on
> my system so I can't test this but normally this should adapt to the
> build environment as it rebuilds and relinks the binary.

Indeed! Implemented and pushed upstream:

https://github.com/mcgrof/compat/commit/42faf2dc8d8bbbdc5b8913183fcd021a27e953c9

So if you run into this issue all you have to do now is run:

./bin/get-compat-kernels -r

New users of the script will automatically have this run after it
downloads and installs the kernel headers.

Case closed, thanks :)

  Luis
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/