hobbit install under debian sarge? 🔗 link

On Tue, Jun 13, 2006 at 04:30:25PM -0700, Dan Simoes wrote:

Has anyone gotten hobbit to install under vanilla sarge?
I had to upgrade a previous machine to testing in order to get it to work,
but I thought that was because of my port from ubuntu.

I've tried both the 4.2 alfa and beta snapshots, and can't get either to
build.
They both fail here:

hecking how to run the C++ preprocessor... /lib/cpp
configure: error: C++ preprocessor "/lib/cpp" fails sanity check

Has anyone gotten hobbit to install under vanilla sarge?
I had to upgrade a previous machine to testing in order to get it to work,
but I thought that was because of my port from ubuntu.

I've tried both the 4.2 alfa and beta snapshots, and can't get either to
build. 
They both fail here:

hecking how to run the C++ preprocessor... /lib/cpp
configure: error: C++ preprocessor "/lib/cpp" fails sanity check
See `config.log' for more details.
make[1]: *** [c-ares/Makefile] Error 1 
make[1]: Leaving directory `/home/dan/hobbit-4.2-alfa-20060423/bbnet'
make: *** [bbnet-build] Error 2

I do have cpp installed, so I'm not sure why it fails the sanity check.

I also tried the .deb version of the beta.  Once I located all the config
files :), I got hobbit to start, but it didn't like the version of the ssl
libraries and was punting on other things. 

Thanks.

Dan

On 6/14/06, Costa, Todd (DMH) <user-dba585b1b7bf@xymon.invalid> wrote:

Hi Dan,

I have been using Debian Sarge and Hobbit 4.1.2p1 successfully since last
November. I used the default install for sarge and added the apache2
components during the build of the debian system. Then I needed to apt-get
install the RRDTOOL, fping packages. Added the hobbit user, downloaded the
hobbit-*.deb and installed that. Then had hobbit running at a base level
before I mod'd the settings to get what I wanted. I thought it worked
really
well and no source grinding was needed.

On another note, if you install the desktop components and use synaptic
you
can search the package db for all the components required. And like I said
I
only had to manually add 3 pieces after the initial install of debian for
the hobbit server. Of course I added other tools to function like I want
but
minimally its doable from deb packages instead of trying to compile from
source. Yet if that's how you want to do it, that's cool too. Look at the
Debian Maintainers guide for the required packages needed to successfully
grind with source. Of course there are other places to refer to for what
is
best but that's your choice. That's what I like about Debian, it is pretty
much everything you need without alot of trouble IMHO, aside from the
research. A few commands or clicks. Bang, you off and running. Good Luck.

TMC

-----Original Message-----
From: hobbit-return-7510-Todd.Costa=user-a9d372c5d972@xymon.invalid
[mailto:hobbit-return-7510-Todd.Costa=user-a9d372c5d972@xymon.invalid]On Behalf Of Dan
Simoes
Sent: Tuesday, June 13, 2006 7:30 PM
To: user-ae9b8668bcde@xymon.invalid
Subject: [hobbit] hobbit install under debian sarge?


Has anyone gotten hobbit to install under vanilla sarge?
I had to upgrade a previous machine to testing in order to get it to work,
but I thought that was because of my port from ubuntu.

I've tried both the 4.2 alfa and beta snapshots, and can't get either to
build.
They both fail here:

hecking how to run the C++ preprocessor... /lib/cpp
configure: error: C++ preprocessor "/lib/cpp" fails sanity check
See `config.log' for more details.
make[1]: *** [c-ares/Makefile] Error 1
make[1]: Leaving directory `/home/dan/hobbit-4.2-alfa-20060423/bbnet'
make: *** [bbnet-build] Error 2

I do have cpp installed, so I'm not sure why it fails the sanity check.

I also tried the .deb version of the beta.  Once I located all the config
files :), I got hobbit to start, but it didn't like the version of the ssl
libraries and was punting on other things.

Thanks.

Dan

On Wed, Jun 14, 2006 at 04:04:21PM -0700, Dan Simoes wrote:

Thanks for the comments.  I'm hoping to stick with the .deb, but right now
it's got a few issues (changing ownership of /tmp among other things!)