Some apps failing after 5.6.5 update

[knc1]

Originally Posted by NiLuJe

@knc1: Yeah, that sounds right, but at that rate, better to simply pass the linker the proper rpath at link-time and be done with it (which is how I handle that kind of stuff in my builds).
Sure, you lose a bit of flexibility, but it's not like we really need it anyway .

But that was my point, the build system will not pass ${ORIGIN} and the build system can not be fixed.
All they could do was document the limitation in the manual.

- - - -

But now I recall what it was I did (other than bitch at the maintainers of buildroot) - -
I came up with a layout that could be passed.
So that is 'worked around', I.E: "good enough".
And if I wasn't locked out of bitbucket - I'd fix the documents.

- - - -

They have since fixed up the "srcdir override" mechanisum, it should be 'fixed' at least good enough for our use.

- - - -

It was the release of about a year ago that they included the build of patchelf as one of the host tools.
(It seems some of there packages have an "rpath problem" that is hard to fix from within the build system.)

- - - -

One thing not (yet) in Buildroot to support after-market firmware for the Kindles - -
Deal with the ro root file system.
But there are a couple of choices on that point to choose from, I just haven't gotten around to deciding on one of them.

- - - -

So my goal of being able to run anything from Ubuntu 14.04LTS in USB storage is very close to being real.

And no one will have to depend on my being around to provide LTS - all they will need is a few (three? four?) config files and the ability to download buildroot to duplicate what I do.

someday - RSN (RSN == a few months)

- - - -

I sure do miss my #1 helper - but he had to get on with his own life.

[voidling]

Hi all!
I still have a problem executing kterm and sadly I am at an impasse.
In a nutshell kterm does find the library, but it throws an internal error (which I am too inexperienced to analyze further).
I have symlinked the library into /usr/lib (1st try) and I changed the kterm.sh to set the library path in the shell script to /mnt/us/extensions/kterm (2nd try).
Then I realised I was still using kterm 0.6 and upgraded to 0.7.
All those efforts produced the same result (see below).

This is what my /usr/lib/libpng* looks like

[root@kindle root]# ls -l /usr/lib/libpng*
lrwxrwxrwx    1 root     root            11 Aug 28 23:23 /usr/lib/libpng.so -> libpng16.so
lrwxrwxrwx    1 root     root            18 Aug 29 22:24 /usr/lib/libpng12.so.0 -> libpng12.so.0.50.0
-rwxr-xr-x    1 root     root        100388 Aug 28 07:30 /usr/lib/libpng12.so.0.50.0
lrwxrwxrwx    1 root     root            19 Jul 31 13:53 /usr/lib/libpng16.so -> libpng16.so.16.15.0
lrwxrwxrwx    1 root     root            19 Jul 31 13:53 /usr/lib/libpng16.so.16 -> libpng16.so.16.15.0
-rwxr-xr-x    1 root     root        158032 Jul 31 13:50 /usr/lib/libpng16.so.16.15.0

The main difference to Micky Wickys post is that he has libpng12.so.0.39.0 whereas I have libpng12.so.0.50.0.

When executing kterm from usbnet-shell without the library I get this error message.

/mnt/us/extensions/kterm/bin/matchbox-keyboard: error while loading shared libraries: libpng12.so.0: cannot open shared object file: No such file or directory
matchbox-keyboard failed to return valid window ID
: No such file or directory

So here I can not find the correct library - no big surprise.

When executing it with the library copied and symlinked in /usr/lib or when setting LD_LIBRARY_PATH in kterm.sh I get this message:

[root@kindle root]# /mnt/us/extensions/kterm/bin/kterm -d
config: /mnt/us/extensions/kterm/bin/../layouts/keyboard.xml
binary: /mnt/us/extensions/kterm/bin/matchbox-keyboard --xid
kb_env: MB_KBD_CONFIG=/mnt/us/extensions/kterm/bin/../layouts/keyboard.xml
/mnt/us/extensions/kterm/bin/matchbox-keyboard: error while loading shared libraries: /usr/lib/libpng12.so.0: internal error
matchbox-keyboard failed to return valid window ID
: No such file or directory

I am not concerned about the messages after the internal error - this is probably because I execute the binary from a remote shell (or not - I can start KOReader from usbnet and it works ). I wonder about the first line.
Do I get the "internal error" because I use libpng12.so.0.50.0?
Should I give it a try with *0.39.0? (if someone can provide the file)

Can you guys give me pointers how to investigate further?

I am pretty sure the problem is a case of PEBCAK as this works for everyone else ...but I am still grateful for any help.

Cheers!

[knc1]

The numbering system:
All digits after the first (*.so.0) ***should not*** matter.
(But not all open source builders get it right, they are human. )

Translation: *.so.0.50.<anything> **should be unchanged such that a calling program could tell** from *.so.0.39.<anything>

But -
Mine ( kTerm 0.4, 0.6, 0.7) works with *.0.39.x, other reports are the same.
Your failing but trying to use *.0.50.y - - - ah, that **might** be the problem.

You can find 0.39 in firmware for the PW-1, at least in version 5.3.3 and 5.3.4

The PW-1 and your PW-2 use a differen SoC (different ARM cpu core also) but your PW-2 should be able to run PW-1 code (ARM is good about those sort of things).

So get KindleTool from NiLuJe's snapshots (prefix: tools), download the PW-1 update package for 5.3.3 or 5.3.4 from Amazon, unpack the update, extract the library - carry on from there - - -

= = = =

The details of doing the above should be in:
https://www.mobileread.com/forums/sho...d.php?t=237083

= = = =

PLUS:
Anytime you change the contents of /lib and/or /usr/lib - - -

mntroot rw
ldconfig

Which re-builds the loader's cache (its the cache entries that resolve the sym-links made).
You shouldn't have to re-start the machine afterward, but it can't hurt.

[NiLuJe]

@voidling: Where did that libpng build come from?

[knc1]

Right!
That looks like the messages you get when trying to load a hard-float library.

[voidling]

Originally Posted by NiLuJe

@voidling: Where did that libpng build come from?

It was attached to Micky Wicky's post (#7) - which is a bit weird as he seems to use *0.39.0
https://www.mobileread.com/forums/att...9&d=1440718008

I will try to go for knc1's solution process (and learn something along the way) unless someone posts the other lib before I get around doing it (and thus enables my laziness).

EDIT:
Thanks to all involved!
Got NiJuLe's kindletool from https://www.mobileread.com/forums/sho...d.php?t=187880
and the image for 5.6.1.1 from amazon http://www.amazon.com/gp/help/custom...deId=201064850
Conversion with kindeltool, mounting the rootfs.img as loopback device and voila - I got my library from /usr/lib.
kterm works. Next step away from noob-dom: get it to work without /usr/lib/libpng12.so.0 and obtain a self-contained KUAL-extension

[knc1]

Originally Posted by voidling

- - -
Next step away from noob-dom: get it to work without /usr/lib/libpng12.so.0 and obtain a self-contained KUAL-extension

There is one issue open with matchbox-keyboard:
https://github.com/xlab/matchbox-keyboard/issues
Sounds familar? Right!

The general way to go about that would be to clone the public repo -
https://github.com/xlab/matchbox-keyboard

develop the fix in a branch of your copy -
send them a "pull request" and/or e-mail them a patch.

Plenty of references to using GIT on the 'net.

[Case]

Thanks guys, that did the trick for my PW2. Copied and linked old libpng12.so.0.39.0 for kterm and libjpeg.so.7.0.0 for gargoyle.

[root@kindle root]# ls -l /usr/lib/libpng12*
lrwxrwxrwx    1 root     root        18 Oct 11 19:38 libpng12.so.0 -> libpng12.so.0.39.0
-rwxr-xr-x    1 root     root    118812 Oct 11 19:36 libpng12.so.0.39.0
[root@kindle root]# ls -l /usr/lib/libjpeg.so.7*
lrwxrwxrwx    1 root     root        16 Oct 11 19:38 libjpeg.so.7 -> libjpeg.so.7.0.0
-rwxr-xr-x    1 root     root    171120 Oct 11 19:36 libjpeg.so.7.0.0

[palbeda]

I followed your instructions but l receive the error:
/usr/lib/libpng12.so.0: version `PNG12_0' not found

I would LOVE to get EBOARD running on my Kindle PW3, but this error stops Eboard from running...

Any suggestions??

[eschwartz]

Well, @baf has repackaged kterm for firmware >= 5.6.5 and libpng16
Maybe he can rebuild eboard as well, did you ask him?

Otherwise... whose instructions, what sources, etc.?

[palbeda]

Originally Posted by eschwartz

Well, @baf has repackaged kterm for firmware >= 5.6.5 and libpng16
Maybe he can rebuild eboard as well, did you ask him?

Otherwise... whose instructions, what sources, etc.?

Good suggestion, I will do that. But I was referring to the instructions in this thread (adding the two lib files to /usr/lib and fixing the symbolic links). Would have been nice if it worked, but I will ask @baf.

[knc1]

Originally Posted by palbeda

Good suggestion, I will do that. But I was referring to the instructions in this thread (adding the two lib files to /usr/lib and fixing the symbolic links). Would have been nice if it worked, but I will ask @baf.

If the error message you posted is correctly quoted, ...
The installing and adding sym-links to the older libraries as described here **will** fix it.
Consider the possibility of PEBKAC.

(If it doesn't fix it, it may cause a new error message to be generated, post that one.)

[palbeda]

SUCCES!!! I double checked my configuration and noted one of the symbolic links was wrong! I fixed that and now Eboard works just fine!

knc1, many thanks for your persistence!