Chris Gransden wrote:
Peter Naulls wrote:
Chris Gransden wrote:
I'd forgotton about xpdf. I'm getting the 'Can't open display' error
from xpdf too.
It's probably some toolkit check, since ChoX11 of course won't
check for it. Unless you've inadvertently linked to X11 instead.
If it's the former, then you can temporarily work around it
by setting the DISPLAY variable - "localhost:0" will do. But
you might want to find who is complaining.
I'm using shared libraries. I think I'd somehow managed to link to both
ChoX11 and X11.
If you could put a little more white space around quoting, I'd
appreciate it - makes it much easier to read ;-)
Anyway, I'd strongly recommend against shared libs right now
for otherwise untested programs. It adds too many confusing
issues - definitely start with static.
I had a quick go compiling it with gcc but no success so far. I was
hoping it would be easier to
get something working with the autobuilder as a stop gap.
I will take a look at compiling the existing old !PDF sources in
the AB. I think you said you had the new xpdf stuff I put in
building ok. From that, the next step for you would be the
merge the two versions, which is much more a programming
exercise than fighting with the toolchain, as is required
getting old stuff to build.
_______________________________________________
GCCSDK mailing list [email protected]
Bugzilla: http://www.riscos.info/bugzilla/index.cgi
List Info: http://www.riscos.info/mailman/listinfo/gcc
Main Page: http://www.riscos.info/index.php/GCCSDK
