Bitcoin Forum

Alternate cryptocurrencies => Altcoin Discussion => Topic started by: hipsterzipster69 on April 09, 2014, 05:51:09 PM



Title: Trouble creating Altcoin clone
Post by: hipsterzipster69 on April 09, 2014, 05:51:09 PM
Hey everybody, recently I got extremely interested in the realm of crypto-currencies. My interest has really developed and now I'm trying to make my own crypto-currency for a school project. Yes, I am 14, and am still in school. So far, I've used this guide: https://andarazoroflove.org/how-to-create-alt-coin-scrypt-clones-for-fun-and-profit-bitcoin-litecoin-secrets-exposed/ and I get to the part where I make the first build and I get a bunch of compile errors. It looks like this:
Zipper:src jacob.zipper$ make -f makefile.osx USE_UPNP=-
/bin/sh ../share/genbuild.sh obj/build.h
llvm-g++ -c -g -Wall -Wextra -Wformat -Wformat-security -Wno-unused-parameter  -DMAC_OSX -DMSG_NOSIGNAL=0 -DBOOST_SPIRIT_THREADSAFE -DUSE_IPV6 -DUSE_UPNP=- -DHAVE_BUILD_INFO -I"/Users/jacob.zipper/WackyBucks/src" -I"/Users/jacob.zipper/WackyBucks/src"/obj -I"/opt/local/include" -I"/opt/local/include/db48" -MMD -MF obj/version.d -o obj/version.o version.cpp
llvm-g++ -c -g -Wall -Wextra -Wformat -Wformat-security -Wno-unused-parameter  -DMAC_OSX -DMSG_NOSIGNAL=0 -DBOOST_SPIRIT_THREADSAFE -DUSE_IPV6 -DUSE_UPNP=- -DHAVE_BUILD_INFO -I"/Users/jacob.zipper/WackyBucks/src" -I"/Users/jacob.zipper/WackyBucks/src"/obj -I"/opt/local/include" -I"/opt/local/include/db48" -MMD -MF obj/checkpoints.d -o obj/checkpoints.o checkpoints.cpp
In file included from checkpoints.cpp:11:
In file included from /Users/jacob.zipper/WackyBucks/src/main.h:9:
In file included from /Users/jacob.zipper/WackyBucks/src/bignum.h:13:
In file included from /Users/jacob.zipper/WackyBucks/src/util.h:22:
In file included from /opt/local/include/boost/thread.hpp:17:
In file included from /opt/local/include/boost/thread/once.hpp:20:
In file included from /opt/local/include/boost/thread/pthread/once_atomic.hpp:20:
In file included from /opt/local/include/boost/atomic.hpp:12:
In file included from /opt/local/include/boost/atomic/atomic.hpp:17:
In file included from /opt/local/include/boost/atomic/detail/platform.hpp:22:
/opt/local/include/boost/atomic/detail/gcc-atomic.hpp:961:64: error: no matching
      constructor for initialization of 'storage_type' (aka
      'boost::atomics::detail::storage128_type')
    explicit base_atomic(value_type const& v) BOOST_NOEXCEPT : v_(0)
                                                               ^  ~
/opt/local/include/boost/atomic/detail/gcc-atomic.hpp:932:28: note: candidate
      constructor (the implicit copy constructor) not viable: no known
      conversion from 'int' to 'const boost::atomics::detail::storage128_type'
      for 1st argument
struct BOOST_ALIGNMENT(16) storage128_type
                           ^
/opt/local/include/boost/atomic/detail/gcc-atomic.hpp:932:28: note: candidate
      constructor (the implicit default constructor) not viable: requires 0
      arguments, but 1 was provided
/opt/local/include/boost/atomic/detail/gcc-atomic.hpp:968:22: error: no viable
      conversion from 'int' to 'storage_type' (aka
      'boost::atomics::detail::storage128_type')
        storage_type tmp = 0;
                     ^     ~
/opt/local/include/boost/atomic/detail/gcc-atomic.hpp:932:28: note: candidate
      constructor (the implicit copy constructor) not viable: no known
      conversion from 'int' to 'const boost::atomics::detail::storage128_type &'
      for 1st argument
struct BOOST_ALIGNMENT(16) storage128_type
                           ^
/opt/local/include/boost/atomic/detail/gcc-atomic.hpp:983:22: error: no viable
      conversion from 'int' to 'storage_type' (aka
      'boost::atomics::detail::storage128_type')
        storage_type tmp = 0;
                     ^     ~
/opt/local/include/boost/atomic/detail/gcc-atomic.hpp:932:28: note: candidate
      constructor (the implicit copy constructor) not viable: no known
      conversion from 'int' to 'const boost::atomics::detail::storage128_type &'
      for 1st argument
struct BOOST_ALIGNMENT(16) storage128_type
                           ^
/opt/local/include/boost/atomic/detail/gcc-atomic.hpp:997:22: error: no viable
      conversion from 'int' to 'storage_type' (aka
      'boost::atomics::detail::storage128_type')
        storage_type expected_s = 0, desired_s = 0;
                     ^            ~
/opt/local/include/boost/atomic/detail/gcc-atomic.hpp:932:28: note: candidate
      constructor (the implicit copy constructor) not viable: no known
      conversion from 'int' to 'const boost::atomics::detail::storage128_type &'
      for 1st argument
struct BOOST_ALIGNMENT(16) storage128_type
                           ^
/opt/local/include/boost/atomic/detail/gcc-atomic.hpp:997:38: error: no viable
      conversion from 'int' to 'storage_type' (aka
      'boost::atomics::detail::storage128_type')
        storage_type expected_s = 0, desired_s = 0;
                                     ^           ~
/opt/local/include/boost/atomic/detail/gcc-atomic.hpp:932:28: note: candidate
      constructor (the implicit copy constructor) not viable: no known
      conversion from 'int' to 'const boost::atomics::detail::storage128_type &'
      for 1st argument
struct BOOST_ALIGNMENT(16) storage128_type
                           ^
/opt/local/include/boost/atomic/detail/gcc-atomic.hpp:1013:22: error: no viable
      conversion from 'int' to 'storage_type' (aka
      'boost::atomics::detail::storage128_type')
        storage_type expected_s = 0, desired_s = 0;
                     ^            ~
/opt/local/include/boost/atomic/detail/gcc-atomic.hpp:932:28: note: candidate
      constructor (the implicit copy constructor) not viable: no known
      conversion from 'int' to 'const boost::atomics::detail::storage128_type &'
      for 1st argument
struct BOOST_ALIGNMENT(16) storage128_type
                           ^
/opt/local/include/boost/atomic/detail/gcc-atomic.hpp:1013:38: error: no viable
      conversion from 'int' to 'storage_type' (aka
      'boost::atomics::detail::storage128_type')
        storage_type expected_s = 0, desired_s = 0;
                                     ^           ~
/opt/local/include/boost/atomic/detail/gcc-atomic.hpp:932:28: note: candidate
      constructor (the implicit copy constructor) not viable: no known
      conversion from 'int' to 'const boost::atomics::detail::storage128_type &'
      for 1st argument
struct BOOST_ALIGNMENT(16) storage128_type
                           ^
In file included from checkpoints.cpp:11:
In file included from /Users/jacob.zipper/WackyBucks/src/main.h:9:
In file included from /Users/jacob.zipper/WackyBucks/src/bignum.h:13:
In file included from /Users/jacob.zipper/WackyBucks/src/util.h:31:
In file included from /Users/jacob.zipper/WackyBucks/src/netbase.h:11:
/Users/jacob.zipper/WackyBucks/src/serialize.h:824:10: error: class member
      cannot be redeclared
    void insert(iterator it, std::vector<char>::const_iterator first, st...
         ^
/Users/jacob.zipper/WackyBucks/src/serialize.h:811:10: note: previous
      declaration is here
    void insert(iterator it, const_iterator first, const_iterator last)
         ^
/Users/jacob.zipper/WackyBucks/src/serialize.h:824:10: error: redefinition of
      'insert'
    void insert(iterator it, std::vector<char>::const_iterator first, st...
         ^
/Users/jacob.zipper/WackyBucks/src/serialize.h:811:10: note: previous definition
      is here
    void insert(iterator it, const_iterator first, const_iterator last)
         ^
In file included from checkpoints.cpp:11:
/Users/jacob.zipper/WackyBucks/src/main.h:43:46: warning: overflow in
      expression; result is 2426047410323587072 with type 'long long'
      [-Winteger-overflow]
static const int64 MAX_MONEY = 1500000000000 * COIN; // maximum number of coins
                                             ^
1 warning and 9 errors generated.
make: *** [obj/checkpoints.o] Error 1

If I could have some help it would be great. Just saying I used Foocoin's source code. If you help it would be so great. I'm doing this project as a community service project for my school and I really want it to work out. Thank you so much.


Title: Re: Trouble creating Altcoin clone
Post by: audcoindev on April 10, 2014, 07:01:12 AM
Trying to build you test coin on mac is not the easiest.


Title: Re: Trouble creating Altcoin clone
Post by: GTO911 on April 10, 2014, 07:22:16 AM
Try this - http://dogecoin.ga/how_to_create_scrypt_based_altcoins.html


Title: Re: Trouble creating Altcoin clone
Post by: Sharrow on April 10, 2014, 09:14:12 AM
Looks like a Boost issue. It might be worthwhile doing this to reinstall boost:

Code:
sudo port uninstall boost

Code:
sudo port install boost +universal

Also, are you sure that you have installed xcode command line terminal (not just the native OSX terminal)!

It might be worth doing bearing this fix for serialize.h if it still won't compile with updated Boost libraries: https://github.com/bitcoin/bitcoin/pull/3162/files  (https://github.com/bitcoin/bitcoin/pull/3162/files)

Like GTO911 said, you would be much better follow the guidance in the dogecoin cloning tutorial as it's Linux based and the dependencies are much, much easier to get to grips with at first.


Title: Re: Trouble creating Altcoin clone
Post by: Acidyo on April 10, 2014, 09:21:43 AM
Try this - http://dogecoin.ga/how_to_create_scrypt_based_altcoins.html

Shit just got real.


Title: Re: Trouble creating Altcoin clone
Post by: templar77 on April 10, 2014, 12:05:19 PM
Try this - http://dogecoin.ga/how_to_create_scrypt_based_altcoins.html

Shit just got real.

Welcome to free market.


Title: Re: Trouble creating Altcoin clone
Post by: YarkoL on April 10, 2014, 12:50:08 PM
Try this - http://dogecoin.ga/how_to_create_scrypt_based_altcoins.html

It's the exact same guide that OP is using. The only difference is a cloaked affiliate link to Digital Ocean.


Title: Re: Trouble creating Altcoin clone
Post by: hipsterzipster69 on April 10, 2014, 04:23:54 PM
I have an Ubuntu virtual machine. Would you recommend creating it on there?


Title: Re: Trouble creating Altcoin clone
Post by: Sharrow on April 10, 2014, 06:57:16 PM
You can do it that way if you've got a decent worksation with plenty of RAM otherwise the routine compiling will take up a lot of your time. It will also completely fail if you can't spare about 2GB RAM to the virtual build.

The Linux VPSs are easy to set up and they are really quick. You're gonna need them at some point anyway unless you're planning to run nodes off your Mac :)