here is the toolchain to test
https://sourcery.mentor.com/sgpp/lite/arm/portal/release1803
you should compile without errors, and after compile you can check with
"readelf -a owhttpd" for example, that should show ARM-EABI-v4 or something
like it in elf file header
a tutorial file
https://sourcer
:/ i don´t know how, but maybe rewrite some code of owlib makefile
ther´s something that don´t allow crosscompile to work well maybe something
that don´t add the crosscompiler prefix in ld,em,as, and others 3 and 2
letters commands inside that makefiles, must read the full file, since i´m
not very
Are there suggested changes for easing the ARM/omap build?
Paul
On Mon, Nov 14, 2011 at 1:26 PM, Roberto Spadim wrote:
> uhmmm i couldn´t compile some time ago...
> i checked that owlib have something that don´t use ./configure compile
> options
> what i did? install a virtual box, changed the d
uhmmm i couldn´t compile some time ago...
i checked that owlib have something that don´t use ./configure compile
options
what i did? install a virtual box, changed the default compilers files (ld,
and other) with sourcery gcc files (or anyother gcc package for arm)
compiled again with configure opt
On 11/14/2011 12:27, Mikael Aalto wrote:
Dear all,
I'm trying to cross-compile the owfs for ARM, but with no luck. I get a
sudden error:
/usr/bin/ld: .libs/error.o: Relocations in generic ELF (EM: 40)
.libs/error.o: could not read symbols: File in wrong format
Perhaps error.o was left over from
Dear all,
I'm trying to cross-compile the owfs for ARM, but with no luck. I get a
sudden error:
/usr/bin/ld: .libs/error.o: Relocations in generic ELF (EM: 40)
.libs/error.o: could not read symbols: File in wrong format
-Can't figure out how it might work, I use the following switches:
conf:
CFL
