> I've only heard of 'make' when talking about 'C' programs, so I assummed
> it was a 'C' thing. Of course it also could be a "UNIX" thing<G>.
I think it is a Unix thing, mostly.
But, yeah, used more often with C than other source langs.
I use it with Assembler sources. Have for years. Recently have
used a "native" CMS make tool, but used OpenVM make before that.
But ... back to the topic ...
> ./configure --enable-smartalloc --sbindir=/bacula/bin
> --sysconfdir=/bacula/bin --with-pid-dir=/bacula/bin/working
> --with-subsys-dir=/bacula/bin/working
> --with-sqlite=/bacula/depkgs/sqlite --with-working-dir=/bacula/working
Some reduction may be gained from
./configure --prefix=/bacula --enable-smartalloc
MOST packages have a smart enough 'configure' script
to lay things out nicely under a prefix. This renders
the package thus built as highly portable (in binary form,
so only across the same HW and OS architecture) and non intrusive
(does not collide with OS programs and files!).
I have no idea if such redux would help your situation.
> And from the ./configure status messages:
It detected SuSE, specifically rel 9, so that's good!
> ==>Entering directory /bacula/bacula-1.36.3/src/console
> make[1]: Entering directory `/bacula/bacula-1.36.3/src/console'
> conio.c:65:21: termcap.h: No such file or directory
> make[1]: *** [depend] Error 1
> make[1]: Leaving directory `/bacula/bacula-1.36.3/src/console'
This could be a show stopper.
The bacula developers need to be informed.
If it is a show stopper, then 'configure' should fail
(or should arrange things so that the BUILD won't fail).
-- R;
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
