On Sat, Feb 16, 2008 at 11:45:23AM +1000, James Bird wrote:
> Is it possible to get this work? Is there something else I can provide  
> to help diagnose problems?
>
> Begin forwarded message:
>
>> From: James Bird <[EMAIL PROTECTED]>
>> Date: 23 January 2008 7:27:09 PM
>> To: [email protected]
>> Subject: Re: [Pdfedit-support] Installation on Mac OSX Leopard -  
>> Boost        Libraries not found

Strange but I haven't recieved this email and it is not also in
pdfedit-support archive AFAICS.

>>
>> Hello again, I've been away for a time... now back to this.
>>
>> I tried 'make' and got the following:
>>
>> cd /Users/James/Software/PDFEditor/pdfedit-test/src && make
>> cd /Users/James/Software/PDFEditor/pdfedit-test/src/xpdf && make  
>> libxpdf
>> cd goo && make
>> make[3]: Nothing to be done for `all'.
>> cd fofi && make
>> make[3]: Nothing to be done for `all'.
>> cd splash && make
>> make[3]: Nothing to be done for `all'.
>> cd xpdf && make libxpdf
>> make[3]: Nothing to be done for `libxpdf'.
>> cd /Users/James/Software/PDFEditor/pdfedit-test/src/utils && make
>> make[2]: Nothing to be done for `all'.
>> cd /Users/James/Software/PDFEditor/pdfedit-test/src/kernel && make
>> make[2]: Nothing to be done for `all'.
>> cd /Users/James/Software/PDFEditor/pdfedit-test/src/kpdf-kde-3.3.2 && 
>> make staticlib
>> make[2]: Nothing to be done for `staticlib'.
>> cd /Users/James/Software/PDFEditor/pdfedit-test/src/qsa && make  
>> staticlib
>> make -f Makefile.qsa
>> cd src && make -f Makefile
>> cd qsa && make -f Makefile
>> make[5]: Nothing to be done for `first'.
>> /bin/sh /Users/James/Software/PDFEditor/pdfedit-test/tools/ 
>> generate_online_help.sh "/Users/James/Software/PDFEditor/pdfedit- 
>> test/doc" "/Users/James/Software/PDFEditor/pdfedit-test/src/gui"
>> Online help seems to be generated.
>> cd /Users/James/Software/PDFEditor/pdfedit-test/src/gui && /sw/lib/ 
>> qt3/bin/qmake pdfedit.pro -o Makefile.qt
>> WARNING: doc_kernel_images.path is not defined: install target not  
>> created

Seems that you need do make clean after you have changed your configure
parameters. I am not sure what is your current state, but I would
suggest "back on trees" approach and start from scratch here. Download
current devel-msts-unified_makefiles branch from CVS, do the configure
with all suggested parameters. Run make (report result) and finally make
install. 
If you want to see the installation result, you can add
--with-root-dir=SOME_DIRECTORY_WITH_ABS_PATH and check that directory
after make install. If everything is correct then you can either copy
all files/directories to / or run configure with same parameters except
--with-root-dir and simply do make install again.

[...]

-- 
Michal Hocko

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Pdfedit-support mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/pdfedit-support

Reply via email to