Bitcoin Forum

Alternate cryptocurrencies => Altcoin Discussion => Topic started by: awais3344 on February 22, 2014, 12:19:57 PM



Title: compiling dogecoin on windows error
Post by: awais3344 on February 22, 2014, 12:19:57 PM
Code:
In file included from src\net.cpp:21:0:
../miniupnpc/upnpcommands.h:117:1: note: declared here
 UPNP_AddPortMapping(const char * controlURL, const char * servicetype,
 ^
In file included from ..\boost-1.50.0-mgw/boost/thread/shared_mutex.hpp:18:0,
                 from ..\boost-1.50.0-mgw/boost/thread/detail/thread_group.hpp:9
,
                 from ..\boost-1.50.0-mgw/boost/thread/thread.hpp:24,
                 from ..\boost-1.50.0-mgw/boost/thread.hpp:13,
                 from src\util.h:25,
                 from src\bignum.h:13,
                 from src\main.h:9,
                 from src\db.h:9,
                 from src\net.cpp:7:
..\boost-1.50.0-mgw/boost/thread/win32/shared_mutex.hpp: In instantiation of 'T
boost::shared_mutex::interlocked_compare_exchange(T*, T, T) [with T = boost::sha
red_mutex::state_data]':
..\boost-1.50.0-mgw/boost/thread/win32/shared_mutex.hpp:124:103:   required from
 here
..\boost-1.50.0-mgw/boost/thread/win32/shared_mutex.hpp:52:99: warning: derefere
ncing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
                                                               *reinterpret_cast
<long*>(&comparand));

                   ^
..\boost-1.50.0-mgw/boost/thread/win32/shared_mutex.hpp:52:99: warning: derefere
ncing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
..\boost-1.50.0-mgw/boost/thread/win32/shared_mutex.hpp:53:52: warning: derefere
ncing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
             return *reinterpret_cast<T const*>(&res);
                                                    ^
..\boost-1.50.0-mgw/boost/thread/win32/shared_mutex.hpp:53:52: warning: derefere
ncing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
In file included from ..\boost-1.50.0-mgw/boost/system/system_error.hpp:14:0,
                 from ..\boost-1.50.0-mgw/boost/thread/exceptions.hpp:22,
                 from ..\boost-1.50.0-mgw/boost/thread/win32/thread_primitives.h
pp:16,
                 from ..\boost-1.50.0-mgw/boost/thread/win32/thread_data.hpp:12,

                 from ..\boost-1.50.0-mgw/boost/thread/thread.hpp:15,
                 from ..\boost-1.50.0-mgw/boost/thread.hpp:13,
                 from src\util.h:25,
                 from src\bignum.h:13,
                 from src\main.h:9,
                 from src\db.h:9,
                 from src\net.cpp:7:
..\boost-1.50.0-mgw/boost/system/error_code.hpp: At global scope:
..\boost-1.50.0-mgw/boost/system/error_code.hpp:214:36: warning: 'boost::system:
:posix_category' defined but not used [-Wunused-variable]
     static const error_category &  posix_category = generic_category();
                                    ^
..\boost-1.50.0-mgw/boost/system/error_code.hpp:215:36: warning: 'boost::system:
:errno_ecat' defined but not used [-Wunused-variable]
     static const error_category &  errno_ecat     = generic_category();
                                    ^
..\boost-1.50.0-mgw/boost/system/error_code.hpp:216:36: warning: 'boost::system:
:native_ecat' defined but not used [-Wunused-variable]
     static const error_category &  native_ecat    = system_category();
                                    ^
Makefile.Release:33990: recipe for target 'build/net.o' failed
mingw32-make: *** [build/net.o] Error 1

C:\dogecoin>

Is it a problem with miniupnpc that i build?
I have already compiled dogecoind.exe from this source. And it works fine, now making qt client. And stuck. Please help me out  ;D


Title: Re: compiling dogecoin on windows error
Post by: awais3344 on February 22, 2014, 12:25:21 PM

Update: I used qmake dogecoin-qt.pro USE_UPNP=-
and removed upnp support. I think now its compiling fine. but can anyone tell me what does upnp do and what is it used for? I am kinda a noob  8)


Title: Re: compiling dogecoin on windows error
Post by: awais3344 on February 22, 2014, 12:53:42 PM
Code:
C:\dogecoin>mingw32-make -f Makefile.Release
g++ -Wl,--dynamicbase -Wl,--nxcompat -Wl,--large-address-aware -Wl,-s -mthreads
-Wl,-subsystem,windows -o release\dogecoin-qt.exe object_script.dogecoin-qt.Rele
ase  -lmingwthrd -lmingw32 -lqtmain C:/dogecoin/src/leveldb/libleveldb.a C:/doge
coin/src/leveldb/libmemenv.a -LC:/boost-1.50.0-mgw/stage/lib -LC:/db-4.8.30.NC-m
gw/build_unix -LC:/openssl-1.0.1c-mgw -lssl -lcrypto -lboost_system-mgw48-mt-s-1
_50 -lboost_filesystem-mgw48-mt-s-1_50 -lboost_program_options-mgw48-mt-s-1_50 -
lboost_thread-mgw48-mt-s-1_50 -lboost_chrono-mgw48-mt-s-1_50 -ldb_cxx -lmswsock
-LC:/Qt/5.2.0/lib -lQt5Widgets -lQt5Network -ldnsapi -LC:/Qt/5.2.0/plugins/platf
orms -lqwindows -lwinspool -lshlwapi -lQt5PlatformSupport -lQt5Gui -lgdi32 -lcom
dlg32 -loleaut32 -limm32 -lwinmm -lQt5Core -lole32 -luuid -lws2_32 -ladvapi32 -l
shell32 -luser32 -lkernel32 build\bitcoin-qt_res.o
C:/boost-1.50.0-mgw/stage/lib/libboost_thread-mgw48-mt-s-1_50.a(tss_pe.o):tss_pe
.cpp:(.rdata$T+0x0): multiple definition of `_tls_used'
c:/mingw/mingw32/bin/../lib/gcc/i686-w64-mingw32/4.8.2/../../../../i686-w64-ming
w32/lib/../lib/libmingw32.a(lib32_libmingw32_a-tlssup.o):tlssup.c:(.tls+0x0): fi
rst defined here
collect2.exe: error: ld returned 1 exit status
Makefile.Release:292: recipe for target 'release\dogecoin-qt.exe' failed
mingw32-make: *** [release\dogecoin-qt.exe] Error 1

C:\dogecoin>


I do not understand it at all

i added multiple definition to
Code:
LDFLAGS=-Wl,--dynamicbase -Wl,--nxcompat -Wl,--large-address-aware -static -Wl,--allow-multiple-definition

still same error.


Title: Re: compiling dogecoin on windows error
Post by: awais3344 on February 22, 2014, 12:59:19 PM
okay,


added -Wl,--allow-multiple-definition makefile.release as well. lol, i forgot that  ::) works fine now


Title: Re: compiling dogecoin on windows error
Post by: DogeHitman on May 12, 2014, 05:04:05 PM
When I add --allow-multiple-definition my exe will no longer open it pretends and then nothing. Otherwise I get multiple definition of '_tls_used'