The Debian bug tracking system may be found at: These maintainers will work with the upstream software developers (in this case, the CinePaint developers) to work out problems like this. You should also consider reporting the problems to Debian they provide their own bug reporting facilities. The CinePaint project page can be seen at: Īs per the support page for this project, they offer a -users mailing list and a Bug Reporting Tracker either of these would be a good way to report the problems you've had: Before posting, you should check to see if similar problems hae already been reported (there may well be an answer to your problem in the mailing list archives). provides a common set of facilities to each project, including tools to help manage bug reports, as well as mailing lists. Have you reported the issue to the CinePaint project team? CinePaint (formerly FilmGimp) is hosted on, a web site that provides hosting for tens of thousands of different Open Source software development projects. I just long so much for 16bit support in the Gimp. Well, I guess that's why it is called like it's called. My 512MB ram are barely enough, it will swap out all the time. If it helps? I'll try it myself soon.īut the thing that bothers me the most is that clearly it is not optimized to handle large images (this may also be the root problem of the segfaults). Maybe also have a look at available configure options. That will build it against the libs on your system, and you still get a nice managed Debian-package to install. They seem to have pretty long release cycles (0.18 is from last July), so I guess another version won't help much.īut you could try to compile the package yourself with "apt-get source cinepaint" and doing "debian/rules binary" in the source directory. The Debian version I have is 0.18, so it's the same as the realease version on Sourceforge. But beware: saving in xcf does not seem to get layer masks right (they are just black when opened again). But usually I can do "enough" steps of editing before it crashes, so I just save often. So if you wanted to try install the above mentioned packages, make sure the red ones are not installed.I also use it, also with Debian (unstable), and have similar problems. A muck around all the linking issues will be to use an LDFLAGS= in the configure. In this case no reason to as the app will likely not be worth using or using very often. The proper way would be to identify which ones & patch. The other issue that some of the individual makefiles (makefile.am in various folders) have their linking in the wrong order so your build will fail. The deps above in red will enable the red configure option, you don't want them as it likely will cause a build error that I've no reason to look in to. =In addition to the 2 mentioned packages above (liblcms1-dev libfltk1.1-dev Thread dependent plug-ins: yes icc_examine deb package of filmgimp or glasgow or similar programs that will work on Ubuntu.Ĭode: =įLTK dependent plug-ins: yes bracketing_to_hdr collect pdf I will be grateful for any suggestions or links to documentation relevant to new versions of Ubuntu or even a way to find/install a. I usually research Ubuntu forums/askUbuntu/Google to see if there is relevant content to my problem before I post a question, however I was unable to find any content relative to Ubuntu past 8.04/.10. Has any suggestions about how to get the. So I was wondering if anyone knows where to find the missing dependencies or can advise me as to how to locate them myself I'm very interested in trying this program, but because the error list doesn't give specific package names, I'm not sure how to locate/install the missing dependencies. Thread dependent plug-ins: no !! ICC Examin will not build !!įlex dependent plug-ins: yes =Ĭonfigure: error: !!! An ERROR occured !!!Please check the above messages to see why.For bug reports please include the complete above output. LittleCMS no !! CinePaint will not build without !!įLTK dependent plug-ins: no !! CinePaint will not build without !!
0 Comments
Leave a Reply. |