On 07/19/2017 10:04 PM, William Bader wrote: > From: Gregory Pittman <gpittman at iglou.com> > > Sent: Wednesday, July 19, 2017 9:43 PM > To: Scribus User Mailing List > Subject: Re: [scribus] libpodofo.so.0.9.1: cannot open shared object file: No > such file or directory > > On 07/19/2017 08:12 PM, Doug Hutcheson wrote: >> I have just upgraded my Fedora system from 25 to 26. Now, my Scribus >> 1.5.4 is broken. I have tried re-compiling it, but this fails with the >> following message: >> >> [ 9%] Linking CXX executable scribus >> CMakeFiles/scribus.dir/pdf_analyzer.cpp.o: In function >> `PDFAnalyzer::PDFAnalyzer(QString&)': >> pdf_analyzer.cpp:(.text+0x9f6): undefined reference to >> `PoDoFo::PdfMemDocument::PdfMemDocument(char const*)' > ... >> dnf reports: >> Package podofo-libs-0.9.5-4.fc26.x86_64 is already installed > > Hi Doug, > Yes, you want podofo-devel.x86_64 also. > Greg > > --- > > Hi. > I am curious what happened because I am going to do the same update on my > laptop soon. > If Scribus built on Fedora 25, shouldn't podofo-devel have been installed on > Fedora 25, and shouldn't the Fedora upgrade have carried over updated > versions of all of the installed packages to Fedora 26? > If podofo-devel were missing, cmake probably would not have gotten passed the > configuration step. Could the link error mean that the Fedora 25 scribus > objects were not cleaned before starting the Fedora 26 build? > I always do out of source builds to make it easier to delete all of the > objects. http://cprieto.com/posts/2016/10/cmake-out-of-source-build.html
It depends on how you upgrade. I don't like the automated upgrade method, since in the past it rendered my computer unbootable afterward -- what a mess! Greg
