Re: Empty pdf output under Mac OS 10.7 (Lion)

Ryan Schmidt <[email protected]>
Newsgroups gmane.comp.lib.cairo
Message-ID <[email protected]>
On Jul 25, 2011, at 11:04, Ethan Tira-Thompson wrote:

> No matter what I do with my cairo pdf surface calls (both my own code and also rsvg-convert), it consistently generates a 414 byte file with PDF headers and footer, but no ‘content'. Thus, Preview and Adobe Reader complain about an invalid file (Preview says it "can't be opened" and that it is damaged or unknown format, whereas Reader complains it "has no pages”).  If I restrict the cairo version to 1.4, I see it does change the version number in the header, but that's the only diff.
> 
> PDF export actually worked in Lion with a cairo binary previously compiled under Snow Leopard.  However, I eventually triggered a recompile and now the new cairo binary is no long functional for PDFs.  PNG and other surfaces do work.
> 
> This is primarily with 1.10.2, but I have also tried a few 1.11.2 builds, which don’t seem to change anything.
> 
> There’s some discussion here
>  http://comments.gmane.org/gmane.os.apple.macports.devel/15083
> that suggestions the llvm backend may be to blame, but my own test with gcc-4.2 suggests that’s not the whole story.  FYI were some llvm issues with the build scripts however:
>  https://trac.macports.org/ticket/29842
> I attached a sample of the bad pdf output there if that would be helpful:
>  https://trac.macports.org/attachment/ticket/29842/bad_cairo_output.pdf
> 
> Anyway, not sure where to start looking at this, it seems like a very strange error.  Some pointers would be appreciated.

You told me in...

https://trac.macports.org/ticket/30370

...that using clang instead of llvm-gcc-4.2 to compile libpixman fixed this cairo issue, so that's what we now do in MacPorts on Lion.


--
cairo mailing list
[email protected]
http://lists.cairographics.org/mailman/listinfo/cairo
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.