(old)Puppy Linux Discussion Forum

What puppy are you using SHS? Have you tested with a recent version? (I haven't).

Wait... I just booted with pfix=ram and discovered that it works fine...

Copied /etc/cups from the save file and restarted cups - still works.
Copied the updated Poppler from my save file - still works.

What else could be the problem? My locale?

Hmmm.
Installing HPLIP-lite makes no difference.
Copying /etc/profile makes no difference.
The ppd and the backend are the same.

Hmmm.
It doesn't seem to be my pango or my glib or my cairo or my up/downgraded freetype.
`ldd epdfview` isn't showing quite the same thing. Does anyone know how to trace which dependencies are pulled in by which other dependencies?
I thought ldd -v would show me, but it doesn't seem to

disciple wrote:What puppy are you using SHS?

A September 5 local woofbuild of t2-8.0rc Quirky.

What is really needed is a fresh compile of the whole pango chain. Correct compilation of it and especially poppler is, indeed, the key to PDF printing, and Puppy's poppler just isn't complete. I believe that at least somewhere around half our PDF problems stem from our poppler's several features-shortfalls.

Puppy's "stock" gcc just isn't up to the task of compiling pango/poppler. I noticed this a year ago when I was creating my extravagantly-patched gcc 4.4.1. Now I have a nearly almighty gcc 4.4.3, but even it fails. The problem lies in, extends back clear into, the toolchain. Not even Quirky's toolchain is good enough, and it's t2.

So, I've been studying LFS (and CLFS), and keeping an eye on Saluki, and have made a start on an LFS Puppy, or really I should say LFS Quirky.

I'll have a go at compiling poppler then pango this weekend, and may come up with something intelligent to say.

Yes, I was trying to build poppler on Windows last night. It was a bit of a nightmare, but I think I almost got there