modphp
I just tried to build modphp_5.3.19.bb for my ARM target.
It seems that the make is using the wrong tools (or libraries), as it fails with this error:
| /usr/lib/libbz2.so: could not read symbols: File in wrong format | collect2: error: ld returned 1 exit status | make: *** [libphp5.la] Error 1
Any ideas how to make this work? Has it ever been built/tested for a cross target? I can see that the cross paths for libz and libbz2 are being passed to the configure step, but they don't seem to be reflected in the actual link step when making the modphp.so library.
Thanks
Signature · 4 lines
------------------------------------------------------------ Gary Thomas | Consulting for the MLB Associates | Embedded world ------------------------------------------------------------
Hi,
Quoted 4 lines · Gary Thomas
I just tried to build modphp_5.3.19.bb for my ARM target.
It seems that the make is using the wrong tools (or libraries), as it fails with this error:
Quoted 9 lines
| /usr/lib/libbz2.so: could not read symbols: File in wrong format | collect2: error: ld returned 1 exit status | make: *** [libphp5.la] Error 1Any ideas how to make this work? Has it ever been built/tested for a cross target? I can see that the cross paths for libz and libbz2 are being passed to the configure step, but they don't seem to be reflected in the actual link step when making the modphp.so library.
it was build and run tested here on an ARM target before sending the patches.
Eric
Quoted 13 lines · Eric Bénard
Hi,
Quoted 8 lines · Gary Thomas
I just tried to build modphp_5.3.19.bb for my ARM target.
It seems that the make is using the wrong tools (or libraries), as it fails with this error:
| /usr/lib/libbz2.so: could not read symbols: File in wrong format | collect2: error: ld returned 1 exit status | make: *** [libphp5.la] Error 1
Quoted 7 lines
Quoted 5 lines
Any ideas how to make this work? Has it ever been built/tested for a cross target? I can see that the cross paths for libz and libbz2 are being passed to the configure step, but they don't seem to be reflected in the actual link step when making the modphp.so library.
it was build and run tested here on an ARM target before sending the patches.
So why did it not work for me? What can I do to diagnose this?
Thanks
Signature · 4 lines
------------------------------------------------------------ Gary Thomas | Consulting for the MLB Associates | Embedded world ------------------------------------------------------------
Quoted 19 lines · Gary Thomas
Quoted 18 lines · Eric Bénard
Hi,
Quoted 13 lines · Gary Thomas
I just tried to build modphp_5.3.19.bb for my ARM target.
It seems that the make is using the wrong tools (or libraries), as it fails with this error:
| /usr/lib/libbz2.so: could not read symbols: File in wrong format | collect2: error: ld returned 1 exit status | make: *** [libphp5.la] Error 1Any ideas how to make this work? Has it ever been built/tested for a cross target? I can see that the cross paths for libz and libbz2 are being passed to the configure step, but they don't seem to be reflected in the actual link step when making the modphp.so library.
Quoted 4 lines
Quoted 2 lines
it was build and run tested here on an ARM target before sending the patches.
So why did it not work for me? What can I do to diagnose this?
I found that there was a libbz2.la installed in the sysroot/usr/lib This is what was causing the problem. I deleted it manually and reran the build and now the modphp package builds.
I'll continue to look to see how that libbz2.la file got there..
Signature · 4 lines
------------------------------------------------------------ Gary Thomas | Consulting for the MLB Associates | Embedded world ------------------------------------------------------------