On Wed, Sep 09, 2009 at 06:19:47AM -0700, wvoice wrote: > > I'm actually trying to figure where things are breaking. I ran make in > ../src/win32/. Then I grep'd for bacula.pdf to see what was trying to build > it. That's originally what took me to newinstaller. But the same happens for > win32_installer as well. > > Here's the output of the top level make in ../src/win32: > > \n===== Make of scripts succeeded =====\n\n > make[1]: Entering directory > `/data/bacula-devel/bacula/bacula/src/win32/win32_installer' > make[1]: *** No rule to make target > `/data/bacula-devel/bacula/docs/manual/bacula.pdf', needed by > `release32/manual/bacula.pdf'. Stop. > make[1]: Leaving directory > `/data/bacula-devel/bacula/bacula/src/win32/win32_installer' > \n!!!!! Make of win32_installer failed !!!!!\n\n > > As you can see, there's not a lot to go on here. That's the good and the bad > news. Is this supposed to go into the docs folder and do a make there? I'm > not yet seeing anything in the top level Makefile that passes that path. > Then again, I could be grepping for the wrong variables there.
Ah, I think that the reason that it works for me is that I commented out the following lines in src/win32/win32_installer/Makefile some time ago: #DOC_FILES := \ # manual/bacula.pdf \ # manual/bacula/*.html \ # manual/bacula/*.png \ # manual/bacula/*.css That out to help. :) ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Bacula-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bacula-devel
