The -dev ones are the headers; the regular ones are the binary libraries. You need -dev when compiling, but after your have the binary you can uninstall them and just leave the binary libraries if desired.
Topic: Using github: Specifically, Vanitygen (Read 2634 times)
No problem.
The -dev ones are the headers; the regular ones are the binary libraries. You need -dev when compiling, but after your have the binary you can uninstall them and just leave the binary libraries if desired.
The -dev ones are the headers; the regular ones are the binary libraries. You need -dev when compiling, but after your have the binary you can uninstall them and just leave the binary libraries if desired.
sudo apt-get install libpcre3-dev libssl-dev
git clone https://github.com/samr7/vanitygen.git
cd vanitygen
make
./vanitygen
It's working so far. I didn't have the dev libraries though I did have the regular libs. I guess when building from source files, dev files are needed sometimes.git clone https://github.com/samr7/vanitygen.git
cd vanitygen
make
./vanitygen
Code:
./vanitygen -r [^V]abcd[^V]efg
7 characters + 2 upper and lower. 712,000,000 and none found yet, I think.Thanks for laying it out Revalin.
Edit: 4.8 billion keys and nothing found yet.
sudo apt-get install libpcre3-dev libssl-dev
git clone https://github.com/samr7/vanitygen.git
cd vanitygen
make
./vanitygen
git clone https://github.com/samr7/vanitygen.git
cd vanitygen
make
./vanitygen
Quote
At present, vanitygen can be built on Linux, and requires the openssl and pcre libraries.
https://github.com/samr7/vanitygen/blob/master/READMEOK, so those are the dependancies for linux, I've got those. There are no build steps listed in the README, are the build steps I listed correct?
apt-get is a package manager, git is source control. The difference is that apt-get packages are usually pre-built binaries, and they are automatically installed (along with any dependencies). Git is just a place for people to keep their source code, and it tracks each change (in case you need to revert some or all of your source). Git is geared toward software development that involves more than one person (whether it is a commercial team, or random internet people contributing to an open source project).
Github doesn't own Git (many people initially assume that), they just happen to be the most prominent free Git host.
To clone a repository, you just use
If you need to update the repo, just go into its folder and hit
Github doesn't own Git (many people initially assume that), they just happen to be the most prominent free Git host.
To clone a repository, you just use
Code:
git clone
, and a new folder with all the same info and history of changes as the remote repo you are cloning will be created. You can then make changes on the source files, or build the project (how it is built depends on the project).If you need to update the repo, just go into its folder and hit
Code:
git pull
.
I'm an apt-get type of person and never have used git. Could someone explain the process?
I hacked up an example from an unrelated git tut but needs some fill in the blanks or corrections.
Are there any dependancies that need to be satisfied before running?
I don't plan on using oclvanitgen as hardware doesn't support 11.11, maybe 8 or 9.
Will I be limited to what I can look for?
I hacked up an example from an unrelated git tut but needs some fill in the blanks or corrections.
Are there any dependancies that need to be satisfied before running?
I don't plan on using oclvanitgen as hardware doesn't support 11.11, maybe 8 or 9.
Will I be limited to what I can look for?Code:
steps on how to compile under Linux:
$ git clone https://github.com/samr7/vanitygen.git
$ cd *where?*
$ git checkout -b *what is going on here?*
$ ./autogen.sh && ./configure *anyflags needed here?* && make
$ sudo make install
$ git clone https://github.com/samr7/vanitygen.git
$ cd *where?*
$ git checkout -b *what is going on here?*
$ ./autogen.sh && ./configure *anyflags needed here?* && make
$ sudo make install
Jump to: