On Friday 25 March 2005 15:06, Tom Plancon wrote: > Tobias Barth wrote: > > "make install" always does a "make" when the things that should be > > installed are not there. This is why the compiler errors occur. On my > > SuSE system I also encountered this problem and I installed the > > "ncurses-devel" and "termcap" packets and then bacula was compiled > > without errors.
Well, I am sorry, but a "make install" does not *always* do a "make". It may be the case on simple systems and on some not so simple ones, but it is not true in general, and it is not true in the case of Bacula. Virtually all documentation is written to do "make" followed by "make install", and this is for good reason, because even in the case where a "make install" will chase all the pre-requisites, it is not a good idea to do a "make install" without a preceding make -- what happens if it fails in the middle? Maybe it is not catastrophic, I would prefer to have a make fail rather than have a "make install" fail half way through. > > > > Greetings, > > > >Tobias Barth > >Web Arts AG > >Max-Planck-Str. 9 > >61381 Friedrichsdorf > >------------------------------- > >Tel.: +49.6172.599833 > >Fax : +49.6172.599830 > >[EMAIL PROTECTED] > >www.web-arts.com > >------------------------------- > >Content Management für den Mittelstand: > >http://cira.web-arts.de > > > > Kern Sibbald schrieb: > >>On Thursday 24 March 2005 21:45, Tom Plancon wrote: > >>>Hi all, > >>> > >>>I'm attempting to build 1.36.2 on RH9 from source. Very green at this so > >>>bear with me. Here is my configure script: > >>> > >>>#!/bin/sh > >>># Tom's config script on Emperor > >>>CFLAGS="-g -Wall" ./configure \ > >>> --prefix=/usr \ > >>> --sbindir=/usr/sbin \ > >>> --sysconfdir=/etc/bacula \ > >>> --with-scriptdir=/etc/bacula \ > >>> --enable-smartalloc \ > >>> --enable-gnome \ > >>> --with-postgresql \ > >>> --with-working-dir=/var/bacula \ > >>> --with-pid-dir=/var/run \ > >>> --with-subsys-dir=/var/lock/subsys \ > >>> --enable-conio > >>> > >>>Above was modified from the sample "traditional RedHat Linux install" > >>>script in the manual. > >>> > >>> > >>> > >>> > >>> > >>>Everything seemed OK until "make install" when I got the following > >>>errors, culled from the whole log: > >> > >>Well, you skipped over the "make" step. > >> > >>>make[1]: *** No rule to make target `../findlib/libfind.a', needed by > >>>`bacula-fd'. Stop. > >>>.... > >>>make[1]: *** No rule to make target `../lib/libbac.a', needed by > >>>`bconsole'. Stop. > >>>make[1]: Leaving directory `/bacula-1.36.2/src/console' > >>>.... > >>>make[1]: *** No rule to make target `../lib/libbac.a', needed by > >>>`bacula-dir'. > >>>Stop. > >>>.... > >>>make[1]: *** No rule to make target `../lib/libbac.a', needed by > >>>`bacula-sd'. Stop. > >>>... > >>>make[1]: Entering directory `/bacula-1.36.2/src/tools' > >>>g++ -c -I. -I.. -g -Wall bsmtp.c > >>>make[1]: *** No rule to make target `../lib/libbac.a', needed by > >>>`bsmtp'. Stop.make[1]: Leaving directory `/bacula-1.36.2/src/tools' > >>>make: *** [install] Error 1 > >>> > >>>Any suggestions are appreciated! Thanks. > > Sorry if my procedure was unclear. What I actually did was: > > configure script > make > make clean > make install -- That is when the errors occurred. > > Do the errors mean there are lines missing from the makefile, or there > are components not on my system that I need to install? I ran bacula > 1.30 for over a year on the same machine. Does 1.36.2 require very > different components? > > Thanks. -- Best regards, Kern ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_ide95&alloc_id396&op=click _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
