Bug 8083 - HP-UX 11.00: problems with HP's Xlib?
Summary: HP-UX 11.00: problems with HP's Xlib?
Status: RESOLVED DUPLICATE of bug 8082
Alias: None
Product: cairo
Classification: Unclassified
Component: xlib backend (show other bugs)
Version: 1.2.5
Hardware: x86 (IA32) HP-UX
: high normal
Assignee: Carl Worth
QA Contact: cairo-bugs mailing list
Depends on:
Reported: 2006-08-31 03:42 UTC by Johannes Abt
Modified: 2006-08-31 03:47 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Description Johannes Abt 2006-08-31 03:42:41 UTC
I've finally succeeded compiling GTK+-2.10 for HP-UX 11.00,
using the current source for cairo.
Though it does not run.

I suspected that a broken Xlib von HP-UX 11.00 might be the reason.
That's why:

When I start gtk-demo with DISPLAY on Linux X.org 6.8.2, I get

SEGV_UNKNOWN - Unknown Error
#0  0xc10ebf00 in XRenderQueryFormats (dpy=0x400146a8) at Xrender.c:335
335     in Xrender.c

When I start gtk-demo with display on a HP-UX 11.11, I get
Error: Cairo 1.2.5 does not yet support the requested image format:
        Depth: 8
        Alpha mask: 0x00000000
        Red   mask: 0x00000000
        Green mask: 0x00000000
        Blue  mask: 0x00000000
Please file an enhacement request (quoting the above) at:
Assertion failed: NOT_REACHED, file
image-surface.c, line 155

The same problem occurs with DISPLAY on an SGI, although
both the HP-UX 11.11 and the SGI have not only an 8bit visual, 
but plenty of 24bit TrueColor and DirectColor visuals, too.

Then I installed GTK+2.10 and all its libraries that I had compiled
for HP-UX 11.00 on the HP-UX 11.11... and it worked!
On all my Linux, HP-UX 11.11 and SGI displays!
(Though the fonts do not have any anti-aliasing, even on the
Linux display with XRender extension.)

Unfortunately, I could not test with DISPLAY on an HP-UX 11.00

Any advice? (except the obvious: avoiding HP-UX)
Comment 1 Carl Worth 2006-08-31 03:47:25 UTC

*** This bug has been marked as a duplicate of 8082 ***

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.