HELLO AND WELCOME! Before you can post your question, you'll have to register -- it's completely free and registered users see less advertising! If you just want to browse through the existing questions, just select the forum that you want to visit from the selection below. Otherwise, click here to register!. We highly recommend that you print a copy of our Guide for New Members. Enjoy!

Having Problem Installing BitchX ...

i do a ./configure after un-tarring the archive and get the following ..

checking whether to use use tgetent or setupterm... setupterm
checking for setupterm in -lncurses... no
checking for setupterm in -lcurses... no
checking for tgetent in -ltinfo... no
checking for tgetent in -lmytinfo... no
checking for setupterm in -ltinfo... no
configure: WARNING: cannot find setupterm - trying tgetent
checking for tgetent in -ltermlib... no
checking for tgetent in -ltermcap... no
checking for tgetent in -lcurses... no
configure: error: cannot find setupterm or tgetent

checking for setupterm in -lncurses... no
checking for setupterm in -lcurses... no

You need libncurses5-dev

checking for tgetent in -ltinfo... no
checking for tgetent in -lmytinfo... no
checking for setupterm in -ltinfo... no
configure: WARNING: cannot find setupterm - trying tgetent

you need ncurses-term

checking for tgetent in -ltermlib... no
checking for tgetent in -ltermcap... no
checking for tgetent in -lcurses... no

You need libterm-query-perl

But the one thing you might want to ask yourself, do I have the build-essential installed... Since these kind of errors usualy comes from a poorly fitted build environment.

Originally Posted by Compunuts

OK, I'm sorry that I helped you.

I would go with Compunuts on this, just install the precompiled version, in todays processors theres so much power, that it isn't such a gain to specific compile for your architecture and configuration. So you lose a couple of cyckles.. But what, the processor might have a few hundreds to spare...

Yeah, see, this is my main point. I've worked far and wide with all the distros and programs and all it comes down to it, it's what works.

It's nice to have it specific to your hardware when the computing power was low. It makes sense to have it even custom kernel compiled for your CPU when you are talking about dual P 200 server and you want the most out of your computing power. But the reality is, most of us have far too many computing power than we need. So why bother compiling it when all you need is install the binary and be done with it unless of course you want to learn how something works. Then again, if it's the case, the poster should have mentioned it that he is just doing it for testing and learning. Otherwise, we will just give what's WORKS.