Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - jandr

Pages: 1 [2] 3
Zaurus - pdaXrom / Native -- C++ / Qt
« on: April 12, 2005, 02:29:44 pm »
This isn't a general solution -- it's pretty much the exact opposite of an SDK -- but if all you're looking for is pdaXrom-compatible QT libraries to link a certain program against, you can try the ones I compiled  (natively) for Konqueror.  There's QT3.3.3 (which required Debian's diffs) as well QT2.3.1 there.  To get Konq to compile against these libs I had to use a lot of the binary utilies from sarge; you may find the same with your app.  Similarly QT3 expected pdaXrom's Xft.h to be named XftFreetype.h, so you might expect to have to do some analogous symlinking of your own.

I have no idea if this helps, but I figure it can't hurt.  

Zaurus - pdaXrom / A Plea For Help..
« on: March 23, 2005, 07:54:44 pm »
I wanted to donate, but I dislike paypal, moneybookers wanted a fax (!) of my credit card, and iKobo kept refusing my payment with a very vague error message.  Would you be able to use an international postal money order sent to the contact address on the website?

Zaurus - pdaXrom / Emacs Runs Fine. Pdaxrom Now Rocks
« on: March 23, 2005, 07:51:28 pm »
For something similar to but a little lighter than emacs, you can try jed.
I got the ipk from here.
It installed & runs fine on rc8, and you can delete the helpfiles to save about a Meg of space.

Zaurus - pdaXrom / Minor Suggestions
« on: March 02, 2005, 04:32:57 pm »
I don't disagree in principle with anything HardenCoonor said, but want to make a plug that any such major changes (e.g. kernel-major/gcc/binutils/X versions) wait for pdaXrom 1.2, and that first priority be given to  getting the bugs out of 1.1.0rcX as currently configured, so that it can be officially released.

and as always, thanks for what's by far the best ROM out there!  (Well, actually the only one for me

Zaurus - pdaXrom / latex
« on: February 14, 2005, 11:28:58 pm »
I am stuck with ghostview. I get a screen for a second then it stop and, among mnay other
stuff, it gives the following error:

Error: /undefinedresult in --div--
Operand stack:
          Fa 136 --nostringval-- w 46000.0 -0.0

It seems to be doing fine for a while and then a hickup. I have had this problem for
a while and cannot get it to disappear.

dvipdfm claims to need but I cannot see anywhere in my configs that
[div align=\"right\"][{POST_SNAPBACK}][/a][/div]

Hi Marcus,
It sounds like you're still having library issues with gs... try following my instructions [a href=\"]here[/url] to get gs going.  (I see on your page that you give similar instructions as on mine, but you say export LD_PRELOAD=/lib/ instead of export LD_PRELOAD=/lib/  Is the extra g intentional?  If not that may be the problem.)

For dvipdf, I wasn't able to get dvipdfm to work at all, but using the same technique as for gs (but replacing 'gs' with 'dvipdf' everywhere in the script file & its filename of course) I got the dvipdf from Zazz' gs distribution working great.  I may also have had to copy a bunch of files from my desktop's latex tree over in order to avoid the same problem you had; I'm sorry but I honestly can't remember.  Then again, your page says that you've got dvipdfm to work on "simple files", so it's possible that all my files are simple and I've just never come across the bug that yours trigger.  


p.s. I'm glad to hear that the OCAML was useful for you.

[C760 / Ambicom Wifi CF / various SD cards, none of which I'm happy with]

Zaurus - pdaXrom / Konqueror
« on: February 03, 2005, 06:28:32 pm »
hmmm... konqueror puts the cached pages in directories directly under /...

i think it is missing its standard directory for cached pages...

does anyone know the path to this directory so i can create it by hand?

Hi Titus,
On my Z, Konq puts cached pages in single-character subdirectories of /tmp, e.g.  /tmp/b/, /tmp/i/ and so on.
Not ideal, I know, but I wouldn't know how to change it (or how to predict what characters it'll use).

Also, I probably missed a -nodebug flag when I did ./configure, at least I assume that's why it spews so much debug info to the console.  Sorry about that; if it was less of a pain to compile I'd re-do it.


Zaurus - pdaXrom / Experiences With Rc8
« on: January 24, 2005, 02:22:24 pm »
it wants an xdvi.bin, which I can nowhere find. Your sources only
supply xdvi-motif.bin and xdvi-xaw.bin. What to do?

Meanwhile I have downloaded the extra packages. I shall try to compile ocaml
myself first for the simple reason that I need to learn how it works so that I
won't anyone to do this for me when a new version comes up. Thanks for the
offer, I'd rather ask for help when I am stuck.

That one is (hopefully) simple: just rename one of them to xdvi.bin, e.g.
"mv /usr/bin/xdvi-xaw.bin /usr/bin/xdvi.bin" and try again.

And I did go ahead and package up OCAML for 1.1.0rc8 already, it's at
I got the sources from Debian, and couldn't get the newest version they had (3.08) to compile without errors, so I went back to version 3.07.2a.  Using the instructions in its INSTALL file, it compiled the bytecode parts cleanly but wouldn't do the native compilers (which according to its README, isn't surprising.)

Zaurus - pdaXrom / Experiences With Rc8
« on: January 20, 2005, 08:33:06 pm »
Hi Marcus,
ack!  I see that my webpage nowhere said that you didn't need the "src" file, i.e. the idea isn't that you should have to compile xdvi yourself.  Sorry about leading you down that path.  What happens if you just use one of the binaries from the "bin" file?  That file should unpack over top of ztex and work out-of-the-box, if ztex itself was installed properly already -- ztex comes with a script called simply "xdvi" which itself runs "xdvi-xaw.bin", and it's the latter that my xdvi.bin tarball overwrites.  So you shouldn't need gcc or extra headers or anything like that.

(Sorry I haven't done a better job packaging it up... you may not be a linux guru, but the inner workings of tex and ghostscript leave me completely befuddled!)

If you do want to compile it yourself, I can't say that I know of any extra packages I needed to get it to compile, but here are some that I already had installed that it might conceivably expect: console-tools & consoletools-libs, diffutils, groff, freetype, patch, perl, pango.  (Some of those probably come standard with your 1.1.0 installation already).  What error messages does ./configure give?  Usually it's pretty explicit about whatever problem it found.

If all you need is OCAML, I can take a shot a compiling it up.  (If you trust me that is

Re: things from your previous post, 1.1.0 does come with awk, and while there is the full GNU awk available in the "gawk" package, I haven't needed it to do any latexing.  I'm not sure what's causing your startx problems, but I do recall seeing other threads in which folks expressed similar frustrations.  (When I startx as non-root, it works fine, but it gives me an ugly TWM-based session by default.)

Here's an example of the "wrapper script" I've been mentioning, this one for gs:

Code: [Select]
export LD_PRELOAD=/lib/
export LD_LIBRARY_PATH=/usr/local/oldlibs
exec /usr/share/ghostscript/8.14/bin/gs "$@"

If you put that code into a file named "gs" in /usr/local/bin, and do "chmod a+rx /usr/local/bin/gs" to make it an executable, then the command "gs" should run ghostscript for you... if you've gotten all the older libraries that gs requires and put them in /usr/local/oldlibs that is.  gv and ps2pdf should also work when given the same treatment.  (Note: I'm not a guru in any sense, so others may have a better way of doing this!  In particular, if the older binary you're putting a wrapper around is in a directory in your $PATH, then you might have to name the wrapper file something different.)

I got my old libs from Debian, but that was easy as I've got a Debian desktop with the "dpkg" package manager included... if you don't have easy access to a debian system you can grab them from my  webpage I linked to in my previous post.

again, I hope all this helps.  And I'm sure I haven't been completely clear and/or general, so don't bang your head too much if you find my instructions don't quite do the trick for you.

Zaurus - pdaXrom / pdf viewer for pdaxrom?
« on: January 20, 2005, 11:42:14 am »
if you have 6.3.4 installed you can remove 6.3.7 .. because when it is linked xpdf will not work .. if it's not then it won't be used.. but the next time ldconfig runs it automatically symlinks to the newer version
if 6.3.4 is not there you should not remove 6.3.7 because X won't start without libfreetype

I'd recommend against removing 6.3.7: when I did and tried to compile something (QT3? I forget) against 6.3.4, g++ bombed, complaining that libfreetype used hardware FP where the other libs on the system used software.  Switching back to 6.3.7 made g++ happy again.

My impression is that xpdf has a bug somewhere that causes it to erroneously want hardware FP, and using 6.3.4 on the Z counteracts that bug instead of fixing it.  So you might want to leave 6.3.7 in /usr/lib, put 6.3.4 somewhere outside ldconfig's search path, and put a wrapper around xpdf that setenvs LD_PRELOAD=/where/you/put/ so that 6.3.7 is what everything else still uses.


Zaurus - pdaXrom / Experiences With Rc8
« on: January 19, 2005, 10:37:41 pm »
(1) startx will not work. It says:

[w100fb] set 640x480 (VGA 90 degree)

waiting for X server to shut down set_power_state: what=256 state=0
send_event: event=0

(It seems to be a power issue ... I get a message "start check battery" -- hm, I
have been using using AC power all the way, that is strange)

Hi Marcus,
the "start check battery"  confused me for a while too...I believe it just means the battery-status daemon is starting up.  When my startx stopped working  it was because I'd installed some QT libraries tgat were conflicting with the system ones that the new WM expected.  Do you have older QT libs somewhere in your ldconfig path or do you manually set QTDIR?

(2) I am a user of LaTeX and had a working system under pdaXrom 1.0.5
includng a xdvi and xpdf. Now, however, xdvi complains: "illegal instruction"
and conversion to .pdf via dvipdfm aborts at the end. Thus, viewing the result
is barred. I converted to .ps, which worked, and used the viewer "v"
provided by Zazz -- and kaboom! The system stalled. (It was after that that
starx ceased to function properly.)

First of all, let me thank you for providing your tex-on-pdaxrom page, it helped me get going and I still use your bibtex and libkpathsea.  The pwers that be tell me that FP emulation in libc changed between 1.0.5 and 1.1.0rc8, so some but not all apps need recompiling -- or you can simply get libraries that use the older FP model, install them in their own directory, and write a wrapper script for the apps that need them which setenvs LD_LIBRARY_PATH to that directory.  I got the libc and xlibs packages from debian/woody, and put wrappers around Zazz' dvips and gs binaries, as well as around your bibtex.  (Zazz' latex embeds .ps figures into the dvi, which is why I switched to his.)

That gives me the ability to view latex docs in gv, which isn't quite ideal.  But it turns out xdvi
 compiles out-of-the-box on rc8, and on the C760's screen it's absolutely amazing.  You can grab my binaries of it from here.

If you want pdfs, Zazz' gs comes with it.  But see the xpdf thread in this forum for its own library issues.


Zaurus - pdaXrom / Konqueror
« on: January 18, 2005, 01:03:10 am »
Well, I've managed to get Konq/embedded compiled for 1.1.0rc8.  make ipkg seemed to expect a different version of than I have, so it's simply in a tar.gz file (plus two more for the QT3 and PCRE libraries -- the pcre that comes with pdaXrom didn't include libpcreposix so I had to roll my own).  It works great, even with my FMP7 server that firefox refuses to talk to!

You can get it from my little Z page.

(Now that I understand the Konq configuration process a bit better, I may try to whip up a QT2-based one,
simply because its make ipkg does seem to work.  If/when I do, it'll be on the same page.)


Zaurus - pdaXrom / Konqueror
« on: January 12, 2005, 02:33:16 pm »
Alas, I can't use firefox or links for this one task: it's a web interface
to FileMakerPro7 which is "designed for use with Safari 1.1 or IE 5.1 or 5.2".
(Stupid, I know, but there's nothing to be done about it.)  On the desktop Opera
works fine with it, while Moz & FF let me log in but then can't navigate at all,
and FMP7 doesn't thinks links -g even has javascript in the first place.
And the same things happen on pdaX.  Hence the desire for Opera or for Konq
(which, like Safari, is KHTML-based).

I wonder if there's any chance that Opera would work if I could just find
a reasonable version of libqt3 and libqpe?  I've already got most of the
other older versions of X11 libraries that older apps seem to require.

[SL-C760 "spoon" with pdaXrom 1.1.0rc8, 32MB Panasonic SD (after my 256MB
Viking started giving too many I/O errors) & AmbiCom CF 802.11b cards]

...sorry for the wacky formatting.  I'm posting this from lynx.

Zaurus - pdaXrom / Konqueror
« on: January 12, 2005, 11:05:09 am »
Hi, I tried installing konq/E 1.51 straight to the internal memory on my 1.1.0rc8 c760 with the exact same results as you had.  I'm guessing there's a hidden library dependency somewhere?  I've tried the few tricks I know, like grabbing older libraries from Debian & pointing konq at them, to no avail here.

It'd be great to get a real graphical non-Gecko browser for pdaXrom (esp. since my work's online scheduler works with KHTML and with Opera but not with Gecko (or Dillo)).  I haven't had any luck finding a libqpe that'll allow Opera mobile to run either.  Has anyone else gotten Opera or Konq running on rc8?

Zaurus - pdaXrom / latex
« on: January 11, 2005, 10:35:13 am »
Well, I can finally contribute something concrete to this thread: imagine my amazement to find that gcc in kathrin comes complete with X libraries and headers, including Xaw and Motif.  So I was able to compile a 1.1.0-happy xdvi straight from the original sources.  You can get the binaries from

Thanks Zazz for doing all the hard work!

Zaurus - pdaXrom / latex
« on: January 10, 2005, 10:25:42 pm »
Sir. I thank you!  Not knowing how to extract 1.0.5's lib[cm] from the ROM image, I simply grabbed the libc6 deb for woody, unpacked it, set LD_LIBRARY_PATH and voila!  xdvi works beautifully.

gs still has issues but that's of no concern for me... I've now got a full LaTeX authoring environment on my Z!  (It's one of the main uses I wanted it for.)  Thanks so much!  

Pages: 1 [2] 3