On 2/28/2023, Leon Pollak wrote:
I recall my previous mail about cross-compilation.
When i did exactly what is recommended, I managed to cross-compile.
The unexpected issue appeared when I run wvalgrind myappw:
FATAL: kernel too old
My kernel is 2.6.37 and seemed to be ok.
Is it final or can I do
Thank you, John for your humor...:-)))
This is ARMv7 (Cortex-A8) the TI TMS320DM8148 CPU with 1GB RAM and there is
no chance to switch to something else.
The Valgrind manual says that it supports Linux 2.6.31 and younger, 2.6.37
seems to be younger...:-)
Why are you so pessimistic...:-)
On Tue, 28
On 2/28/2023, Leon Pollak wrote:
I recall my previous mail about cross-compilation.
When i did exactly what is recommended, I managed to cross-compile.
The unexpected issue appeared when I run wvalgrind myappw:
FATAL: kernel too old
My kernel is 2.6.37 and seemed to be ok.
Is it final or can I do
I recall my previous mail about cross-compilation.
When i did exactly what is recommended, I managed to cross-compile.
The unexpected issue appeared when I run wvalgrind myappw:
FATAL: kernel too old
My kernel is 2.6.37 and seemed to be ok.
Is it final or can I do something further? Old Valgrind ve
Thank you, Paul - you were right - I missed the autogen.sh script.
Doing it and trying to satisfy its and configure requirements brought me to
so many incompatible version errors, that I gave up on "native" compilation
(for DM8148 arm Cortex-A8, Linux 2.6.37) and decided to switch to
cross-compilat
