On Sat, 4 Jun 2011 17:33:20 +0200 Clemens Kofler <[email protected]> wrote:
> Hey Chris, > > thanks for trying to help. > I'm also kind of ruling out Homebrew as the bad buy because as I've > >indicated I've also tried compiling it manually, i.e. cloning the git > >repository and then running configure and make. It fails when trying to > >patch things (i.e. running the inject-xpdf.pl script) because the required > >patches are not there. If I manually copy the patches there, the patch > >stage is successful but make aborts later (I'd have to doublecheck on the > >error but it was also xpdf-related). Knowing the specific error may give a clue. I have to say I've not tried the latest Git. Will do it later when I get a spare moment or two. See what happens ( this'll be under Linux ). You could also try one or more of the following configure options, see if they give you more clues, --enable-checkmem turn on ccmalloc debugging --enable-debug turn on debugging --enable-profiling turn on profiling --enable-warnings turn on compiler warnings > > - the original source code version of 0.9.1? > > 0.9.1 compiles just fine but segfaults in both cases, when compiled > manually or via Homebrew. In which case it"s not Homebrew. Could easily be an errant library though. By the way, when you say 'segfaults in both cases', I take it you mean only the resulting pdf2swf binary, and not any of the other tools? Have you also checked the mailing list archives? http://lists.nongnu.org/archive/html/swftools-common/ > Thanks anyway! Welcome. > Maybe someone else will chime in, yes. Chris.
