From: "Eric Bénard" <eric@eukrea.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: modphp
Date: Fri, 7 Dec 2012 19:15:16 +0100 [thread overview]
Message-ID: <20121207191516.072c6bf1@eb-e6520> (raw)
In-Reply-To: <50C228F8.6060805@mlbassoc.com>
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
next prev parent reply other threads:[~2012-12-07 19:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-07 17:35 modphp Gary Thomas
2012-12-07 18:15 ` Eric Bénard [this message]
2012-12-07 18:59 ` modphp Gary Thomas
2012-12-07 20:28 ` modphp Gary Thomas
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20121207191516.072c6bf1@eb-e6520 \
--to=eric@eukrea.com \
--cc=openembedded-devel@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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.