[HOWTO] compile altcoin for windows on linux using mxe and mingw

[turboblade]

I am getting a permissions error when trying to build make MXE_TARGETS="i686-w64-mingw32.static" qttools.

make[1]: *** [build-only-libmysqlclient_i686-w64-mingw32.static] Error 1

Any ideas?

[1714481817]

1714481817

[1714481817]

1714481817

[1714481817]

1714481817

[1714481817]

1714481817

[gjhiggins]

Hey @gjhiggins thanks for the reply.
How do you link to that directory?

Take a look at xtrabytes examples, compile-win.sh which shows how to cross-compile the leveldb/memenv libraries https://github.com/borzalom/XtraBYtes/blob/master/compile-win.sh#L12 and xtrabytes-qt.pro which shows how to bind the environment variables to pick up the newly cross-compiled libraries: https://github.com/borzalom/XtraBYtes/blob/master/xtrabytes-qt.pro#L113

Just follow the examples, copynpasta, swapping out leveldb for secp256k1, (dunno if you need to add secp256k1 files to SOURCES and HEADERS, depends on how the interface to the library is implemented in your specific codebase). Begin edit-compile-debug cycle, hope it terminates successfully.

Cheers

Graham

[gimsy]

Hey @gjhiggins thanks for the reply.
How do you link to that directory?

Take a look at xtrabytes examples, compile-win.sh which shows how to cross-compile the leveldb/memenv libraries https://github.com/borzalom/XtraBYtes/blob/master/compile-win.sh#L12 and xtrabytes-qt.pro which shows how to bind the environment variables to pick up the newly cross-compiled libraries: https://github.com/borzalom/XtraBYtes/blob/master/xtrabytes-qt.pro#L113

Just follow the examples, copynpasta, swapping out leveldb for secp256k1, (dunno if you need to add secp256k1 files to SOURCES and HEADERS, depends on how the interface to the library is implemented in your specific codebase). Begin edit-compile-debug cycle, hope it terminates successfully.

Cheers

Graham

Can you be more specific? I've tried working around with those files but i keep getting the same error.
Thanks

[Many Coins]

Is it working with Bitcoin Core 0.8?

[hakimcoin]

Is it working with Bitcoin Core 0.8?

Its worked with Litecoin 0.8.7.4
I think it will work

[Many Coins]

Is it working with Bitcoin Core 0.8?

Its worked with Litecoin 0.8.7.4
I think it will work

Heck!  Too late.  I've almost finished setting up the environment in Windows))

Btw, thank you! Probably useful later.

[paccoinofficial]

is there a guide to make a coin from QT4 to QT5?

[hakimcoin]

Heck!  Too late.  I've almost finished setting up the environment in Windows))

Btw, thank you! Probably useful later.

Good look. It's very hard to do.

[validsyntax1012]

Hey @gjhiggins thanks for the reply.
How do you link to that directory?

I did download the option others posted here from Windows (pre-built) and tried to copy it pretty much everywhere @_@.

I tried to copy the content of the folder secp256k1 directly to /home/zeus/Desktop/mxe/usr/i686-w64-mingw32.static and also the folder itself.
And I tried to copy the contents of the same folder to /home/zeus/Desktop/mxe/usr/i686-w64-mingw32.static/bin (as this we add it to on the PATH= as per the tutorial) and the folder itself.

I also tried to merge the contents of /home/zeus/Desktop/AltCoin/src/secp256k1 with the ones from Windows.

None of the options worked.

Am I missing something on my file /home/zeus/Desktop/AltCoin/compile-win.sh?

Code:

#!/bin/bash
MXE_INCLUDE_PATH=~/Desktop/mxe/usr/i686-w64-mingw32.static/include
MXE_LIB_PATH=~/Desktop/mxe/usr/i686-w64-mingw32.static/lib

chmod 755 src/leveldb/build_detect_platform
chmod 755 src/secp256k1/autogen.sh
cd src/leveldb
make libleveldb.a libmemenv.a
cd ../..

i686-w64-mingw32.static-qmake-qt5 \
	BOOST_LIB_SUFFIX=-mt \
	BOOST_THREAD_LIB_SUFFIX=_win32-mt \
	BOOST_INCLUDE_PATH=$MXE_INCLUDE_PATH/boost \
	BOOST_LIB_PATH=$MXE_LIB_PATH \
	OPENSSL_INCLUDE_PATH=$MXE_INCLUDE_PATH/openssl \
	OPENSSL_LIB_PATH=$MXE_LIB_PATH \
	BDB_INCLUDE_PATH=$MXE_INCLUDE_PATH \
	BDB_LIB_PATH=$MXE_LIB_PATH \
	MINIUPNPC_INCLUDE_PATH=$MXE_INCLUDE_PATH \
	MINIUPNPC_LIB_PATH=$MXE_LIB_PATH \
	QMAKE_LRELEASE=~/Desktop/mxe/usr/i686-w64-mingw32.static/qt5/bin/lrelease altcoi[Suspicious link removed]o

make -f Makefile.Release

its needs to be in you /mnt/mxe/usr/lib/gcc/i686-w64-mingw32.static/5.4.0 folder that worked past my errors now im getting this

Code:

pi32 -lwinmm -lz -lpcre2-16 build/bitcoin-qt_res.o 
build/key.o:key.cpp:(.text+0x181): undefined reference to `secp256k1_context_destroy'
build/key.o:key.cpp:(.text+0x2ee): undefined reference to `secp256k1_ec_privkey_import'
build/key.o:key.cpp:(.text+0x353): undefined reference to `secp256k1_ec_pubkey_create'
build/key.o:key.cpp:(.text+0x48f): undefined reference to `secp256k1_ec_privkey_import'
build/key.o:key.cpp:(.text+0x181b): undefined reference to `secp256k1_ec_pubkey_verify'
build/key.o:key.cpp:(.text+0x1890): undefined reference to `secp256k1_ec_pubkey_decompress'
build/key.o:key.cpp:(.text+0x1a83): undefined reference to `secp256k1_ec_pubkey_tweak_add'
build/key.o:key.cpp:(.text+0x2ad6): undefined reference to `secp256k1_ec_privkey_tweak_add'
build/key.o:key.cpp:(.text+0x32fa): undefined reference to `secp256k1_nonce_function_rfc6979'
build/key.o:key.cpp:(.text+0x3337): undefined reference to `secp256k1_ecdsa_sign'
build/key.o:key.cpp:(.text+0x39ac): undefined reference to `secp256k1_nonce_function_rfc6979'
build/key.o:key.cpp:(.text+0x39e3): undefined reference to `secp256k1_ecdsa_sign_compact'
build/key.o:key.cpp:(.text+0x3ea5): undefined reference to `secp256k1_ec_privkey_export'
build/key.o:key.cpp:(.text.startup+0x30): undefined reference to `secp256k1_context_create'
collect2: error: ld returned 1 exit status

Code:

  CC       src/libsecp256k1_la-secp256k1.lo
  CCLD     libsecp256k1.la
libtool: warning: undefined symbols not allowed in i686-w64-mingw32 shared libraries; building static only
/usr/bin/ar: `u' modifier ignored since `D' is the default (see `U')
  CC       src/tests-tests.o
  CCLD     tests

I try to compile the secp256k1 with ming and i get this

maybe should try to compile on windows like other have done? this coin has older version of the secp256k1 so i cannot use the binary that are on here it seems
didnt know if error was only refering to the test.o or the libsecp256k1.la
any help would be awesome great guide btw have successfully done other coins

[Flenger]

Change

Code:

#!/bin/bash
MXE_INCLUDE_PATH=/mnt/mxe/usr/i686-w64-mingw32.static/include
MXE_LIB_PATH=/mnt/mxe/usr/i686-w64-mingw32.static/lib

i686-w64-mingw32.static-qmake-qt5 \

Code:

#!/bin/bash
MXE_INCLUDE_PATH=/mnt/mxe/usr/i686-w64-mingw32.static/include
MXE_LIB_PATH=/mnt/mxe/usr/i686-w64-mingw32.static/lib

/mnt/mxe/usr/i686-w64-mingw32.static/qt5/bin/qmake \

Push +Merit 

[validsyntax1012]

Change

Code:

#!/bin/bash
MXE_INCLUDE_PATH=/mnt/mxe/usr/i686-w64-mingw32.static/include
MXE_LIB_PATH=/mnt/mxe/usr/i686-w64-mingw32.static/lib

i686-w64-mingw32.static-qmake-qt5 \

Code:

#!/bin/bash
MXE_INCLUDE_PATH=/mnt/mxe/usr/i686-w64-mingw32.static/include
MXE_LIB_PATH=/mnt/mxe/usr/i686-w64-mingw32.static/lib

/mnt/mxe/usr/i686-w64-mingw32.static/qt5/bin/qmake \

Push +Merit 

i was also replying to other user did you get my error any advice?

[talonpower]

How I can fix this problem. Help me please.
command: 'ranlib src/leveldb/libmemenv.a' not helped

https://duckduckgo.com/?q=%22Archive+has+no+index%3B+run+ranlib+to+add+one%22+site%3Abitcointalk.org&atb=v81-6__&ia=web

in your link they think that person dont generated libleveldb.a and libmemenv.a files, but I have the files...

/mnt/coinm# ls src/leveldb | grep lib
libleveldb.a
libmemenv.a

You might need to summon a little more persistence, then you might progress a little faster.

For people arriving later with the same problem ... from the list of search results I gave:

If you haven't got the RANLIB binding as described here:

https://bitcointalk.org/index.php?topic=912667.msg10037005#msg10037005

then try with that.

Otherwise:

https://bitcointalk.org/index.php?topic=912667.msg10037005#msg10037005

Other than that, you're on your own.

Cheers

Graham

that is only one link... and they do not give any solution

i am still having issues with this build and no matter what i do i get

Code:

make[1]: Entering directory '/mnt/*****/src/leveldb'
make[1]: 'libleveldb.a' is up to date.
make[1]: 'libmemenv.a' is up to date.
make[1]: Leaving directory '/mnt/coinm/src/leveldb'
/bin/sh: 1: i686-w64-mingw32.static-ranlib: not found
Makefile.Release:478: recipe for target '/mnt/****/src/leveldb/libleveldb.a' failed
make: *** [/mnt/*****/src/leveldb/libleveldb.a] Error 127

I see the "i686-w64-mingw32.static-ranlib"   located in its correct spot

I have also done

Code:

#!/bin/bash
MXE_PATH=/mnt/mxe
sed -i "s/WinIoCtl.h/winioctl.h/g" src/dbinc/win_db.h
mkdir build_mxe
cd build_mxe

RANLIB=$MXE_PATH/usr/bin/i686-w64-mingw32.static-ranlib \
      CC=$MXE_PATH/usr/bin/i686-w64-mingw32.static-gcc \
      CXX=$MXE_PATH/usr/bin/i686-w64-mingw32.static-g++ \
      ../dist/configure \
      --disable-replication \
      --enable-mingw \
      --enable-cxx \
      --host x86 \
      --prefix=$MXE_PATH/usr/i686-w64-mingw32.static 

make

make install

and gave this a shot too

Code:

cd %coin_folder%/src/leveldb
TARGET_OS=NATIVE_WINDOWS make libleveldb.a libmemenv.a CC=/mnt/mxe/usr/bin/i686-w64-mingw32.static-gcc CXX=/mnt/mxe/usr/bin/i686-w64-mingw32.static-g++ RANLIB=/mnt/mxe/usr/bin/i686-w64-mingw32.static-ranlib

I followed the links  but there was only one and it gave no actual solution

been stuck on this over 24+ hours  and there is just so little documentation for help.

[Stipend]

Hey @gjhiggins thanks for the reply.
How do you link to that directory?

Take a look at xtrabytes examples, compile-win.sh which shows how to cross-compile the leveldb/memenv libraries https://github.com/borzalom/XtraBYtes/blob/master/compile-win.sh#L12 and xtrabytes-qt.pro which shows how to bind the environment variables to pick up the newly cross-compiled libraries: https://github.com/borzalom/XtraBYtes/blob/master/xtrabytes-qt.pro#L113

Just follow the examples, copynpasta, swapping out leveldb for secp256k1, (dunno if you need to add secp256k1 files to SOURCES and HEADERS, depends on how the interface to the library is implemented in your specific codebase). Begin edit-compile-debug cycle, hope it terminates successfully.

Cheers

Graham

Can you be more specific? I've tried working around with those files but i keep getting the same error.
Thanks

Hey @gjhiggins thanks for the reply.
How do you link to that directory?

I did download the option others posted here from Windows (pre-built) and tried to copy it pretty much everywhere @_@.

I tried to copy the content of the folder secp256k1 directly to /home/zeus/Desktop/mxe/usr/i686-w64-mingw32.static and also the folder itself.
And I tried to copy the contents of the same folder to /home/zeus/Desktop/mxe/usr/i686-w64-mingw32.static/bin (as this we add it to on the PATH= as per the tutorial) and the folder itself.

I also tried to merge the contents of /home/zeus/Desktop/AltCoin/src/secp256k1 with the ones from Windows.

None of the options worked.

Am I missing something on my file /home/zeus/Desktop/AltCoin/compile-win.sh?

Code:

#!/bin/bash
MXE_INCLUDE_PATH=~/Desktop/mxe/usr/i686-w64-mingw32.static/include
MXE_LIB_PATH=~/Desktop/mxe/usr/i686-w64-mingw32.static/lib

chmod 755 src/leveldb/build_detect_platform
chmod 755 src/secp256k1/autogen.sh
cd src/leveldb
make libleveldb.a libmemenv.a
cd ../..

i686-w64-mingw32.static-qmake-qt5 \
	BOOST_LIB_SUFFIX=-mt \
	BOOST_THREAD_LIB_SUFFIX=_win32-mt \
	BOOST_INCLUDE_PATH=$MXE_INCLUDE_PATH/boost \
	BOOST_LIB_PATH=$MXE_LIB_PATH \
	OPENSSL_INCLUDE_PATH=$MXE_INCLUDE_PATH/openssl \
	OPENSSL_LIB_PATH=$MXE_LIB_PATH \
	BDB_INCLUDE_PATH=$MXE_INCLUDE_PATH \
	BDB_LIB_PATH=$MXE_LIB_PATH \
	MINIUPNPC_INCLUDE_PATH=$MXE_INCLUDE_PATH \
	MINIUPNPC_LIB_PATH=$MXE_LIB_PATH \
	QMAKE_LRELEASE=~/Desktop/mxe/usr/i686-w64-mingw32.static/qt5/bin/lrelease altcoi[Suspicious link removed]o

make -f Makefile.Release

its needs to be in you /mnt/mxe/usr/lib/gcc/i686-w64-mingw32.static/5.4.0 folder that worked past my errors now im getting this

Code:

pi32 -lwinmm -lz -lpcre2-16 build/bitcoin-qt_res.o 
build/key.o:key.cpp:(.text+0x181): undefined reference to `secp256k1_context_destroy'
build/key.o:key.cpp:(.text+0x2ee): undefined reference to `secp256k1_ec_privkey_import'
build/key.o:key.cpp:(.text+0x353): undefined reference to `secp256k1_ec_pubkey_create'
build/key.o:key.cpp:(.text+0x48f): undefined reference to `secp256k1_ec_privkey_import'
build/key.o:key.cpp:(.text+0x181b): undefined reference to `secp256k1_ec_pubkey_verify'
build/key.o:key.cpp:(.text+0x1890): undefined reference to `secp256k1_ec_pubkey_decompress'
build/key.o:key.cpp:(.text+0x1a83): undefined reference to `secp256k1_ec_pubkey_tweak_add'
build/key.o:key.cpp:(.text+0x2ad6): undefined reference to `secp256k1_ec_privkey_tweak_add'
build/key.o:key.cpp:(.text+0x32fa): undefined reference to `secp256k1_nonce_function_rfc6979'
build/key.o:key.cpp:(.text+0x3337): undefined reference to `secp256k1_ecdsa_sign'
build/key.o:key.cpp:(.text+0x39ac): undefined reference to `secp256k1_nonce_function_rfc6979'
build/key.o:key.cpp:(.text+0x39e3): undefined reference to `secp256k1_ecdsa_sign_compact'
build/key.o:key.cpp:(.text+0x3ea5): undefined reference to `secp256k1_ec_privkey_export'
build/key.o:key.cpp:(.text.startup+0x30): undefined reference to `secp256k1_context_create'
collect2: error: ld returned 1 exit status

Code:

  CC       src/libsecp256k1_la-secp256k1.lo
  CCLD     libsecp256k1.la
libtool: warning: undefined symbols not allowed in i686-w64-mingw32 shared libraries; building static only
/usr/bin/ar: `u' modifier ignored since `D' is the default (see `U')
  CC       src/tests-tests.o
  CCLD     tests

I try to compile the secp256k1 with ming and i get this

maybe should try to compile on windows like other have done? this coin has older version of the secp256k1 so i cannot use the binary that are on here it seems
didnt know if error was only refering to the test.o or the libsecp256k1.la
any help would be awesome great guide btw have successfully done other coins

Hey guys, if ya'll haven't found the solution to this yet, here's my code to cross compile Stipend from Ubuntu to Windows, let me know if this helps!

Code:

#!/bin/bash
MXE_PATH=$HOME/mxe
MXE_INCLUDE_PATH=$MXE_PATH/usr/i686-w64-mingw32.static/include
MXE_LIB_PATH=$MXE_PATH/usr/i686-w64-mingw32.static/lib
SECP256K1_LIB_PATH=/usr/local/lib

cd src/leveldb
TARGET_OS=NATIVE_WINDOWS make CC=i686-w64-mingw32.static-g++ CXX=i686-w64-mingw32.static-g++ libleveldb.a libmemenv.a
cd ../..

cd ./src/secp256k1
sudo ./autogen.sh
sudo ./configure --host=i686-w64-mingw32.static --with-bignum=no --enable-module-recovery
TARGET_OS=NATIVE_WINDOWS make CC=i686-w64-mingw32.static-g++ CXX=i686-w64-mingw32.static-g++ libsecp256k1.la libsecp256k1.so
sudo make install
cd ../..

$MXE_PATH/usr/bin/i686-w64-mingw32.static-qmake-qt5 \
	BOOST_LIB_SUFFIX=-mt \
	BOOST_THREAD_LIB_SUFFIX=_win32-mt \
	BOOST_INCLUDE_PATH=$MXE_INCLUDE_PATH \
	BOOST_LIB_PATH=$MXE_LIB_PATH \
	OPENSSL_INCLUDE_PATH=$MXE_INCLUDE_PATH/openssl \
	OPENSSL_LIB_PATH=$MXE_LIB_PATH \
	BDB_INCLUDE_PATH=$MXE_INCLUDE_PATH \
	BDB_LIB_PATH=$MXE_LIB_PATH \
	MINIUPNPC_INCLUDE_PATH=$MXE_INCLUDE_PATH \
	MINIUPNPC_LIB_PATH=$MXE_LIB_PATH \
	QMAKE_LRELEASE=$MXE_PATH/usr/i686-w64-mingw32.static/qt5/bin/lrelease stipend.pro

make -f Makefile.Release

[charlie-gama]

I have compiled the lb * .a in / src / leveldb
you take a look



*************************************

make -f Makefile.Release
make[1]: Entering directory `/root/mnt/scoin'
cd /root/mnt/scoin/src/leveldb && CC=i686-w64-mingw32.static-gcc CXX=i686-w64-mingw32.static-g++ TARGET_OS=OS_WINDOWSxport -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -O2" libleveldb.a libmemenv.a && i686-w64-mingw32.static-ranlib /root/mnt/suc.static-ranlib /root/mnt/scoin/src/leveldb/libmemenv.a
make[2]: Entering directory `/root/mnt/soin/src/leveldb'
make[2]: `libleveldb.a' is up to date.
make[2]: `libmemenv.a' is up to date.
make[2]: Leaving directory `/root/mnt/scoin/src/leveldb'
/bin/sh: 1: i686-w64-mingw32.static-ranlib: not found
make[1]: *** [/root/mnt/scoin/src/leveldb/libleveldb.a] Error 127
make[1]: Leaving directory `/root/mnt/scoin'
make: *** [release] Error 2

[charlie-gama]

error in route.

cd /mnt/mxe
export PATH=/mnt/mxe/usr/bin:$PATH

and Compile !!!


**************************************

I have compiled the lb * .a in / src / leveldb
you take a look



*************************************

make -f Makefile.Release
make[1]: Entering directory `/root/mnt/scoin'
cd /root/mnt/scoin/src/leveldb && CC=i686-w64-mingw32.static-gcc CXX=i686-w64-mingw32.static-g++ TARGET_OS=OS_WINDOWSxport -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -O2" libleveldb.a libmemenv.a && i686-w64-mingw32.static-ranlib /root/mnt/suc.static-ranlib /root/mnt/scoin/src/leveldb/libmemenv.a
make[2]: Entering directory `/root/mnt/soin/src/leveldb'
make[2]: `libleveldb.a' is up to date.
make[2]: `libmemenv.a' is up to date.
make[2]: Leaving directory `/root/mnt/scoin/src/leveldb'
/bin/sh: 1: i686-w64-mingw32.static-ranlib: not found
make[1]: *** [/root/mnt/scoin/src/leveldb/libleveldb.a] Error 127
make[1]: Leaving directory `/root/mnt/scoin'
make: *** [release] Error 2

[charlie-gama]

For compile wallet mac.
any opinion

In fact, thanks to mezzovide, you no longer need to build bdb separately.

https://github.com/mxe/mxe/pull/791

BitcoinDark, making it easier to build on Windows


Matthew

[BryanCatsburg]

I experience this error:

Code:

/mnt/mxe/usr/bin/i686-w64-mingw32.static-ld: cannot find -lboost_thread-mgw46-mt-sd-1_53
/mnt/mxe/usr/bin/i686-w64-mingw32.static-ld: cannot find -lboost_system-mgw46-mt-sd-1_53
/mnt/mxe/usr/bin/i686-w64-mingw32.static-ld: cannot find -lboost_filesystem-mgw46-mt-sd-1_53
/mnt/mxe/usr/bin/i686-w64-mingw32.static-ld: cannot find -lboost_program_options-mgw46-mt-sd-1_53
/mnt/mxe/usr/bin/i686-w64-mingw32.static-ld: cannot find -lboost_chrono-mgw46-mt-sd-1_53
collect2: error: ld returned 1 exit status
make: * [release/Eryllium-qt.exe] Error 1

my bash file looks like that:

Code:

#!/bin/bash
MXE_INCLUDE_PATH=/mnt/mxe/usr/i686-w64-mingw32.static/include
MXE_LIB_PATH=/mnt/mxe/usr/i686-w64-mingw32.static/lib

i686-w64-mingw32.static-qmake-qt5 \
	BOOST_LIB_SUFFIX=-mt \
	BOOST_THREAD_LIB_SUFFIX=_win32-mt \
	BOOST_INCLUDE_PATH=$MXE_INCLUDE_PATH/boost \
	BOOST_LIB_PATH=$MXE_LIB_PATH \
	OPENSSL_INCLUDE_PATH=$MXE_INCLUDE_PATH/openssl \
	OPENSSL_LIB_PATH=$MXE_LIB_PATH \
	BDB_INCLUDE_PATH=$MXE_INCLUDE_PATH \
	BDB_LIB_PATH=$MXE_LIB_PATH \
	MINIUPNPC_INCLUDE_PATH=$MXE_INCLUDE_PATH \
	MINIUPNPC_LIB_PATH=$MXE_LIB_PATH \
	QMAKE_LRELEASE=/mnt/mxe/usr/i686-w64-mingw32.static/qt5/bin/lrelease coin-qt.pro

make -f Makefile.Release

Can someone explain me how to fix that? Thanks!!

[zextherabbit]

Hello all, i have tried to compile Ignition coin https://github.com/ignitioncoin/ignitioncoin.

I am using :

https://www.amazon.com/clouddrive/share/ZhOxZQQzji8FpQvuV9b86DqJg6IGpIXmlXFyG5o2X8h?ref_=cd_ph_share_link_copy

with 4gb of ram, 4 cores of i5 processor, 40gb of hdd, swap size 10gb.
In virtual machine there is boost installed version 1.57, miniupnpc-1.6.20120509, and OpenSSL 1.0.2d 9 (/mnt/user/i686-w64-mingw32.static/include/openssl/opensslv.h).

I had an error with secp256k1, then i tried

Code:

./configure --host=i686-w64-mingw32.static
make

and now error that i have is as follows :

Code:

empty space, like full page A4

/mnt/mxe/usr/bin/i686-w64-mingw32.static-ld: cannot find -lpthread
collect2: error: ld returned 1 exit status
make: *** [release/Ignition-qt.exe] Error 1

Anyone has an idea what might be causing this error?

[darein]

hello i tried to compile but

Code:

src/bignum.h: In function 'bool operator>=(const CBigNum&, const CBigNum&)':
src/bignum.h:718:83: error: cannot convert 'const CBigNum*' to 'const BIGNUM* {aka const bignum_st*}' for argument '1' to 'int BN_cmp(const BIGNUM*, const BIGNUM*)'
 inline bool operator>=(const CBigNum& a, const CBigNum& b) { return (BN_cmp(&a, &b) >= 0); }
                                                                                   ^
src/bignum.h: In function 'bool operator<(const CBigNum&, const CBigNum&)':
src/bignum.h:719:83: error: cannot convert 'const CBigNum*' to 'const BIGNUM* {aka const bignum_st*}' for argument '1' to 'int BN_cmp(const BIGNUM*, const BIGNUM*)'
 inline bool operator<(const CBigNum& a, const CBigNum& b)  { return (BN_cmp(&a, &b) < 0); }
                                                                                   ^
src/bignum.h: In function 'bool operator>(const CBigNum&, const CBigNum&)':
src/bignum.h:720:83: error: cannot convert 'const CBigNum*' to 'const BIGNUM* {aka const bignum_st*}' for argument '1' to 'int BN_cmp(const BIGNUM*, const BIGNUM*)'
 inline bool operator>(const CBigNum& a, const CBigNum& b)  { return (BN_cmp(&a, &b) > 0); }

getting these error all over anyone know how to fix this .
tx.

[FreakCoder]

hello i tried to compile but

Code:

src/bignum.h: In function 'bool operator>=(const CBigNum&, const CBigNum&)':
src/bignum.h:718:83: error: cannot convert 'const CBigNum*' to 'const BIGNUM* {aka const bignum_st*}' for argument '1' to 'int BN_cmp(const BIGNUM*, const BIGNUM*)'
 inline bool operator>=(const CBigNum& a, const CBigNum& b) { return (BN_cmp(&a, &b) >= 0); }
                                                                                   ^
src/bignum.h: In function 'bool operator<(const CBigNum&, const CBigNum&)':
src/bignum.h:719:83: error: cannot convert 'const CBigNum*' to 'const BIGNUM* {aka const bignum_st*}' for argument '1' to 'int BN_cmp(const BIGNUM*, const BIGNUM*)'
 inline bool operator<(const CBigNum& a, const CBigNum& b)  { return (BN_cmp(&a, &b) < 0); }
                                                                                   ^
src/bignum.h: In function 'bool operator>(const CBigNum&, const CBigNum&)':
src/bignum.h:720:83: error: cannot convert 'const CBigNum*' to 'const BIGNUM* {aka const bignum_st*}' for argument '1' to 'int BN_cmp(const BIGNUM*, const BIGNUM*)'
 inline bool operator>(const CBigNum& a, const CBigNum& b)  { return (BN_cmp(&a, &b) > 0); }

getting these error all over anyone know how to fix this .
tx.

I wasn't running into if before my system restore, but setting everything back up I am getting this same error. So far, I have only found references to the ssl being an incorrect version possibly. I wish I had more details, but wanted you to know I am in the same boat.