* modphp
@ 2012-12-07 17:35 Gary Thomas
2012-12-07 18:15 ` modphp Eric Bénard
0 siblings, 1 reply; 4+ messages in thread
From: Gary Thomas @ 2012-12-07 17:35 UTC (permalink / raw)
To: openembedded-devel
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
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: modphp
2012-12-07 17:35 modphp Gary Thomas
@ 2012-12-07 18:15 ` Eric Bénard
2012-12-07 18:59 ` modphp Gary Thomas
0 siblings, 1 reply; 4+ messages in thread
From: Eric Bénard @ 2012-12-07 18:15 UTC (permalink / raw)
To: openembedded-devel
Hi,
Le Fri, 07 Dec 2012 10:35:52 -0700,
Gary Thomas <gary@mlbassoc.com> a écrit :
> 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.
>
it was build and run tested here on an ARM target before sending the
patches.
Eric
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: modphp
2012-12-07 18:15 ` modphp Eric Bénard
@ 2012-12-07 18:59 ` Gary Thomas
2012-12-07 20:28 ` modphp Gary Thomas
0 siblings, 1 reply; 4+ messages in thread
From: Gary Thomas @ 2012-12-07 18:59 UTC (permalink / raw)
To: openembedded-devel
On 2012-12-07 11:15, Eric Bénard wrote:
> Hi,
>
> Le Fri, 07 Dec 2012 10:35:52 -0700,
> Gary Thomas <gary@mlbassoc.com> a écrit :
>
>> 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.
>>
> 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
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: modphp
2012-12-07 18:59 ` modphp Gary Thomas
@ 2012-12-07 20:28 ` Gary Thomas
0 siblings, 0 replies; 4+ messages in thread
From: Gary Thomas @ 2012-12-07 20:28 UTC (permalink / raw)
To: openembedded-devel
On 2012-12-07 11:59, Gary Thomas wrote:
> On 2012-12-07 11:15, Eric Bénard wrote:
>> Hi,
>>
>> Le Fri, 07 Dec 2012 10:35:52 -0700,
>> Gary Thomas <gary@mlbassoc.com> a écrit :
>>
>>> 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.
>>>
>> 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..
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2012-12-07 20:43 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2012-12-07 17:35 modphp Gary Thomas
2012-12-07 18:15 ` modphp Eric Bénard
2012-12-07 18:59 ` modphp Gary Thomas
2012-12-07 20:28 ` modphp Gary Thomas
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.