View Single Post
Old 04-07-2020, 10:03 PM   #13
NiLuJe
BLAM!
NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.
 
NiLuJe's Avatar
 
Posts: 13,506
Karma: 26047202
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
It won't meet *any* of the dependencies, that's going to be (one of) the tricky part.

You'll have to pull the whole deptree by hand (or possibly with Debian's help if something in its package manager tooling allows to do something like printing the whole depgraph for a specific package. I haven't used Debian is over 15 years, though, so, no idea ).

Or go with a chroot like @knc1 did at one point (with a hardfloat tree, IIRC), in which case you still need the whole deptree, but you bypass the glibc issues, because you'll then rely on the Debian glibc & dynamic loaded. The only compatibility left with that approach is the kernel.

And in that case, you don't really have to bother because people have already made Alpine chroots tailored to the Kindle .

Last edited by NiLuJe; 04-07-2020 at 10:09 PM.
NiLuJe is offline   Reply With Quote