I dunno but why are you trying to cpu mine bitcoin? It's a waste of time and energy.

For compiling, the presence of the actual libraries is not important, you need the development files (libcurl-dev or similar).

Also, you may want to check out cgminer, which is actually maintained.

Ok I did. New problem.

the configure script demands libdbcurces-dev. I install it but it insists on installing libdbcurces5-dev. configure script STILL insists on libdbcuces.

Go get compiled version.

when I run cgminer-cpuonly it says it can't find the file. when I run ./cgminer-cpuonly it says

bash: ./cgminer-cpuonly: cannot execute binary file

when I write a script file with the # and everything it says

./cgminer-cpuonly: 1: Syntax error: Unterminated quoted string

You know - in WINDOWS this just up and ran first time. No trouble.
[/quote]

If you really want an answer, you should head over to the thread I pointed you to, that is where cgminer discussion & development is happening.

I can't really help you with ubuntu package names, since I use debian. However, the configure script shouldn't depend on a package version as much as the files in that package. Also, did you misspell the package name? The required packages should be:

Cgminer comes with a README, which contains detailed instructions on how to build it.

The testnet RPC port is 18332 by default, so:

As far as I know Deepbit doesn't mine on the testnet. You'll have to mine against a local instance of the Bitcoin daemon.

• Download and install a client, personally I prefer the command-line daemon (bitcoind), but you can go with the graphical version as well.
  
• Compile it if you've downloaded the source.
• Launch with (add "-daemon" if you're using the daemon):

          (set username and password to your liking)

• Now you may mine against that, by using 127.0.0.1 (localhost) as your "pool URL". Like this:

(setting username and password to the values you set above)

Try passing it manually:

It's probably not even worth trying assuming Gavin's testnet difficulty calculation changes aren't live yet.

Try Testnet in a box. You can "use CPU mining to create blocks every 10 minutes as normal or a GPU miner for blocks every few seconds".

I started a fork of jgarzik's miner a few months ago. The original goal was to provide an optimized miner for Litecoin, an alternative chain that uses a completely different hashing algorithm from Bitcoin. Over time, however, I have also added a number of new features and bugfixes. You can find a complete list of all important changes in the NEWS file; they include:

• Optimized work handling, resulting in a much better getwork efficiency.
• Support for HTTP and SOCKS proxies.
• Support for many different operating systems and architectures, including big-endian ones. The miner has been reported to build successfully on Linux, FreeBSD, Solaris, Mac OS X and Windows (using mingw).
• Clear --help output. (Please read it before using the miner!)

Now for the reason I'm writing this here.
Starting with version 2.2 of this fork, I have re-included support for Bitcoin mining, writing a new implementation of the hashing algorithm. This implementation is different in that the single --algo=sha256d option should provide the best performance on all systems.
On K10-based processors (such as the Phenom) this fork is only slightly faster than the old "4way" algorithm, but on all other systems you should notice a significant increase in mining speed. The miner is also capable of using AVX and XOP instructions on CPUs that support them, resulting in an even greater speedup.

Here's a link to the git repository:
https://github.com/pooler/cpuminer
Under the "Downloads" tab you will also find a source tarball and a couple Windows binaries.

I don't know if anybody is still interested in CPU mining. The main reason why I want to maintain this miner is because I enjoy coding; also, I like jgarzik's miner because, unlike many others, it conforms to the KISS design principle.
Given that CPU mining support has been discontinued for cgminer, I hope that people will find this fork useful.

I'd say so, judging from this post:




Honestly I don't think this is necessary, since very few people still mine Bitcoin on CPU. In addition, cgminer has never been the only miner with CPU support (there's Ufasoft's miner, for instance).
I also think that, as a core Bitcoin developer, your time would probably be best spent elsewhere.
All this to say: I would be more than happy to take this project over, especially considering that I've rewritten a lot of the old code already.