| 1 |
On 2/3/2013 12:24, Nilesh Govindrajan wrote: |
| 2 |
> On Sunday 03 February 2013 09:19:58 PM IST, Dustin C. Hatch wrote: |
| 3 |
>> On 2/3/2013 04:10, Nilesh Govindrajan wrote: |
| 4 |
>>> Okay that solved the ebuild problem, but I'm stuck with another |
| 5 |
>>> problem now -_- |
| 6 |
>>> |
| 7 |
>> ... |
| 8 |
>>> /usr/lib/libdb-4.8.so: file not recognized: File format not recognized |
| 9 |
>> |
| 10 |
>> Looks like it is trying to use the libdb shared object from the host |
| 11 |
>> system instead of the sysroot. |
| 12 |
>> |
| 13 |
>> How are you calling emerge? Can you post the command you ran that was |
| 14 |
>> used to install PAM? I don't have PAM on my Raspberry Pi, but I just |
| 15 |
>> tested cross-compiling it and it worked fine. |
| 16 |
>> |
| 17 |
> |
| 18 |
> Following your blog post you posted a link earlier; calling emerge as - |
| 19 |
> |
| 20 |
> armv6j-hardfloat-linux-gnueabi-emerge --onlydeps -1 -v $base |
| 21 |
> |
| 22 |
> It was pulled in as a dependency (for berkdb use flag, set by |
| 23 |
> default/linux/arm/10.0/armv6j profile) |
| 24 |
> |
| 25 |
> -- |
| 26 |
> Nilesh Govindarajan |
| 27 |
> http://nileshgr.com |
| 28 |
> |
| 29 |
Okay, the problem is probably the way PAM tries to link against db. |
| 30 |
Unless you need that functionality, I'd go ahead and remove the berkdb |
| 31 |
USE flag and try again. You may also want to file a bug. |
| 32 |
|
| 33 |
-- |
| 34 |
♫Dustin |
Archives