Pages:
Author

Topic: Building headless Bitcoin and Bitcoin-qt on Windows - page 58. (Read 419389 times)

member
Activity: 112
Merit: 10
thanks, I'll play with that, I want to get gitian builder setup in my VMbox but I'm not sure how to install it from the source (I assume you compile, but as you can see I'm learning about compiling at the moment making it hard for me to install gitian)
gitian is pretty easy. it sets up the vm, installs all the packages needed for compilation, and compiles it. It's all done inside a vm with scripts (included with bitcoin), so it's actually easier than compiling using your own tools.

agreed, my issue is more getting gitian setup, the link I find is source code from github but what to do with it after I download it I'm kind of at a loss
1. open up terminal in ubuntu
2. sudo apt-get install git apache2 apt-cacher-ng python-vm-builder ruby qemu-kvm
3. git clone https://github.com/devrandom/gitian-builder.git
4. cd gitian-builder
5. bin/make-base-vm
6. bin/make-base-vm --arch i386
7. follow the instructions in the script i linked earlier.

after step 5:
Code:
alexander@vurtual-ubuntu-x64:~/Downloads/gitian-builder$ bin/make-base-vm
2013-06-07 04:46:31,692 INFO    : Calling hook: preflight_check
2013-06-07 04:46:31,695 INFO    : Calling hook: set_defaults
2013-06-07 04:46:31,695 INFO    : Calling hook: bootstrap

infinite waiting.
press Ctrl+c, see next:
Code:
^CTraceback (most recent call last):
  File "/usr/bin/vmbuilder", line 24, in
    cli.main()
  File "/usr/lib/python2.7/dist-packages/VMBuilder/contrib/cli.py", line 218, in main
    distro.build_chroot()
  File "/usr/lib/python2.7/dist-packages/VMBuilder/distro.py", line 83, in build_chroot
    self.call_hooks('bootstrap')
  File "/usr/lib/python2.7/dist-packages/VMBuilder/distro.py", line 67, in call_hooks
    call_hooks(self, *args, **kwargs)
  File "/usr/lib/python2.7/dist-packages/VMBuilder/util.py", line 165, in call_hooks
    getattr(context, func, log_no_such_method)(*args, **kwargs)
  File "/usr/lib/python2.7/dist-packages/VMBuilder/plugins/ubuntu/distro.py", line 136, in bootstrap
    self.suite.debootstrap()
  File "/usr/lib/python2.7/dist-packages/VMBuilder/plugins/ubuntu/dapper.py", line 269, in debootstrap
    run_cmd(*cmd, **kwargs)
  File "/usr/lib/python2.7/dist-packages/VMBuilder/util.py", line 113, in run_cmd
    fds = select.select([x.file for x in [mystdout, mystderr] if not x.closed], [], [])[0]
KeyboardInterrupt

how to step 6,7?
sr. member
Activity: 260
Merit: 251
is it possible to expand your guide to include building the qt client?

Bitcoin-qt build instrunctions added Smiley

Hello nitrogenetics

Finally, after two months of studying and testing, on and off in spare moments, I have found what was keeping me from compiling bitcoin-qt on windows, for windows!
...
So I added a piece to the LIBS directive at line 18 of Makefile.Release:
it was
LIBS        =      -L"c:\Qt\4.8.4\lib" -lmingwthrd -lmingw32 -lqtmain ...

and it becomes
LIBS        =        -L"c:\Qt\4.8.4\bin" -L"c:\Qt\4.8.4\lib" -lmingwthrd -lmingw32 -lqtmain ...

Then it links, and bitcoin-qt.exe works so far, in the various tests I have given it.
...
I think there is a boatload of good programmers out there that are on the windows platform, that can improve the UI of bitcoin-qt and the internals too, and make it so tempting that many more (non technical) people will jump on the Bitcoin bandwagon...

All windows VC6, VC++Express 2005, 2008, 2010, 2012 (all free IDE BTW) users, let's contribute.

Getting off soapbox now Lips sealed

Ron

If this is of any help, small fragments may be donated to my profile btc $, 1DPvP6WoZzaNQ9Nxzd64hjYad1kyQzTTbx, thereby rounding up your wallet  Wink


I don't think people reading this understood me? When I said:
"All windows VC6, VC++Express 2005, 2008, 2010, 2012 (all free IDE BTW) users, let's contribute."

What I was implying is that there are IDE's in windows, that don't cost big bucks! I for one, having seen microsoft's business practices since their 8bit MSDOS days, am somewhat loathe to spend money on an IDE of theirs! I never said I compiled the bitcoind/qt 0.8.1 code with any version of MSC++. I only use it as a free tool.

And one can use VC6 to just gang edit, refactor, etc. the bitcoind & bitcoin-qt projects and compile them as above with command lines:
mingw32-make -f makefile.mingw
and
mingw32-make -f Makefile.Release

One could even create a VC or VS to do it for you. It may even be able to catch the warnings and errors and throw you to those lines in the editor. The only thing it couldn't do is gdb, and it may even be able to do that, I don't know? One can tailor the editor to one's pleasure, Brief in my case. One can use other products (in windows), I believe, like notepad++, etc.

I say this because I used to one keystroke compile (command line) from inside of Brief (when Underware owned it) back in the 1980s and it had no trouble with over 80 sources files, about 2 MB of source, etc. etc. In the 1990s I did the same thing targeting a Fujitsu handheld, wireless, keyboard-less (yes w/ handwriting recognition) application.

So what do all the Linux users develop bitcoind/qt with? Is it Eclipse, Qt Creator, KDevelop, MonoDevelop, CodeLite, ...?

BTW, I downloaded the only creator for windows that I saw, QT 5.0.2 Do people run that QT, compiling bitcoin-qt with the QT 4.8.4 libraries and using mingw32 4.6.2?

I just use VC6 and VC++Express2005, so far, to hold the project, edit, refactor, test, etc. But do the command line compile from another window very easily. I did do some command line gdb (with a gcc of -O0) on bitcoind and it was not bad at all!

It seems that QT Creator does "strain" my 2Ghz, 3GB AMD Athlon XP system a little, and VS is a much lighter load. But then I am wearing many hats at all times:)

I hope this makes things clearer.

Ron

legendary
Activity: 2058
Merit: 1452
All windows VC6, VC++Express 2005, 2008, 2010, 2012 (all free IDE BTW) users, let's contribute.
FYI building with VC6 is not possible. It does not support modern versions of boost (compiler lacks some perfectly standard C++ syntax) and has buggy C++ standard library. What do you expect of a 15+ year old compiler...

Newer MSVC should work with the headless version, but getting Qt to work with Express versions is very tricky, as it doesn't support add-ins you need custom build defines and steps for moc/qrc/etc. With the retail version you can install https://qt-project.org/wiki/QtVSAddin and have those handled automatically.


how exactly do you get bitcoind working with visual studio 2012?
full member
Activity: 131
Merit: 108
I did everything exactly as the guide said, it did compile... however the qt client just run for a few seconds (without any interface shown) and disappear silently from the process list. Any idea what went wrong?

I confirm bitcoin-qt crashes when compiled with gcc 4.7.2 (bitcoind seems to be working). Which version did you compile with?
hero member
Activity: 812
Merit: 1022
No Maps for These Territories
All windows VC6, VC++Express 2005, 2008, 2010, 2012 (all free IDE BTW) users, let's contribute.
FYI building with VC6 is not possible. It does not support modern versions of boost (compiler lacks some perfectly standard C++ syntax) and has buggy C++ standard library. What do you expect of a 15+ year old compiler...

Newer MSVC should work with the headless version, but getting Qt to work with Express versions is very tricky, as it doesn't support add-ins you need custom build defines and steps for moc/qrc/etc. With the retail version you can install https://qt-project.org/wiki/QtVSAddin and have those handled automatically.

sr. member
Activity: 260
Merit: 251
is it possible to expand your guide to include building the qt client?

Bitcoin-qt build instrunctions added Smiley

Hello nitrogenetics

Finally, after two months of studying and testing, on and off in spare moments, I have found what was keeping me from compiling bitcoin-qt on windows, for windows!

What I discovered was, was that in step 4.3 of your wonderful guide,
qmake "USE_UPNP=-" bitcoin-qt.pro
creates the Makefile.Release for the next step, and it makes an (at least one) error in doing it! What I found was that when the next step is run
mingw32-make -f Makefile.Release
the linker loader part (looking at Makefile.Release) at the end of the process, attempts to link
QtGui4  and QtCore4, which are .dll's in the bin directory, not the lib directory!

So I added a piece to the LIBS directive at line 18 of Makefile.Release:
it was
LIBS        =      -L"c:\Qt\4.8.4\lib" -lmingwthrd -lmingw32 -lqtmain build\bitcoin-qt_res.o D:/BTCversions/version_0_8_1/src/src/leveldb/libleveldb.a D:/BTCversions/version_0_8_1/src/src/leveldb/libmemenv.a -lshlwapi -LC:\boost_1_53_0\stage\lib -Lc:/db-4.8.30.NC/build_unix -Lc:/openssl-1.0.1e -lssl -lcrypto -ldb_cxx -lws2_32 -lshlwapi -lmswsock -lole32 -loleaut32 -luuid -lgdi32 -lboost_system-mgw46-mt-sd-1_53 -lboost_filesystem-mgw46-mt-sd-1_53 -lboost_program_options-mgw46-mt-sd-1_53 -lboost_thread-mgw46-mt-sd-1_53 -lboost_chrono-mgw46-mt-sd-1_53 -lQtGui4 -lQtCore4

and it becomes
LIBS        =        -L"c:\Qt\4.8.4\bin" -L"c:\Qt\4.8.4\lib" -lmingwthrd -lmingw32 -lqtmain build\bitcoin-qt_res.o D:/BTCversions/version_0_8_1/src/src/leveldb/libleveldb.a D:/BTCversions/version_0_8_1/src/src/leveldb/libmemenv.a -lshlwapi -LC:\boost_1_53_0\stage\lib -Lc:/db-4.8.30.NC/build_unix -Lc:/openssl-1.0.1e -lssl -lcrypto -ldb_cxx -lws2_32 -lshlwapi -lmswsock -lole32 -loleaut32 -luuid -lgdi32 -lboost_system-mgw46-mt-sd-1_53 -lboost_filesystem-mgw46-mt-sd-1_53 -lboost_program_options-mgw46-mt-sd-1_53 -lboost_thread-mgw46-mt-sd-1_53 -lboost_chrono-mgw46-mt-sd-1_53 -lQtGui4 -lQtCore4

Then it links, and bitcoin-qt.exe works so far, in the various tests I have given it.

Interestingly, the messages referred to that are emitted when qmake creates Makefile.Release from bitcoin-qt.pro suggest that it is turning uPnP back on and off and on, even with the flag saying no, off.  I think the QtGui4 & QtCore dlls are that uPnp part which somehow crept into the link from bitcoin-qt.pro

Perhaps the .pro file can be "fixed" but I think the problem may be more in the "less than robust" parser in qmake?

I am now off to giving the wallet.dat its own path, like bitcoin.conf can have. The only tricky code is at startup in AppInit2(), step 5, where the "Verifying wallet integrity..." code is, covering -salvagewallet and bitdb.Verify(...)

But I don't think it is too difficult.

I think there is a boatload of good programmers out there that are on the windows platform, that can improve the UI of bitcoin-qt and the internals too, and make it so tempting that many more (non technical) people will jump on the Bitcoin bandwagon...

All windows VC6, VC++Express 2005, 2008, 2010, 2012 (all free IDE BTW) users, let's contribute.

Getting off soapbox now Lips sealed

Ron

If this is of any help, small fragments may be donated to my profile btc $, 1DPvP6WoZzaNQ9Nxzd64hjYad1kyQzTTbx, thereby rounding up your wallet  Wink
sr. member
Activity: 260
Merit: 251
I did everything exactly as the guide said, it did compile... however the qt client just run for a few seconds (without any interface shown) and disappear silently from the process list. Any idea what went wrong?

maybe you have another version of bitcoind running? Or it thinks you do, via the .lock file, etc.
Ron
hero member
Activity: 781
Merit: 501
I did everything exactly as the guide said, it did compile... however the qt client just run for a few seconds (without any interface shown) and disappear silently from the process list. Any idea what went wrong?

i got same issue  Huh
member
Activity: 112
Merit: 10
I did everything exactly as the guide said, it did compile... however the qt client just run for a few seconds (without any interface shown) and disappear silently from the process list. Any idea what went wrong?
hero member
Activity: 781
Merit: 501
No idea with the qt. I can't figure out why I can't compile it myself. Wink

Peter, thanks anyway
hero member
Activity: 630
Merit: 502
No idea with the qt. I can't figure out why I can't compile it myself. Wink
hero member
Activity: 781
Merit: 501
thanks peter, that's work for me now.
successful compile the deamon, but still getting some errors when compiling the qt part "undefine d reference to `shutdown@8'"

do you have any idea with this?
Thanks for any help
hero member
Activity: 630
Merit: 502
trying to compile the litecoin as a practice, got this error

Quote
util.h:555:16: error: 'pthread_t' has a previous declaration as 'typedef void* p
thread_t'

any help would be appreciated.
Thanks

In src/makefile.mingw find this:
Code:
DEFS=-DWIN32 -D_WINDOWS -DBOOST_THREAD_USE_LIB -DBOOST_SPIRIT_THREADSAFE -DUSE_IPV6

Add this to the line:
Code:
-D__NO_SYSTEM_INCLUDES
hero member
Activity: 781
Merit: 501
trying to compile the litecoin as a practice, got this error

Quote
util.h:555:16: error: 'pthread_t' has a previous declaration as 'typedef void* p
thread_t'

any help would be appreciated.
Thanks
sr. member
Activity: 260
Merit: 251
OK I'm totally stumped. Building the daemon works fine but I can't for the life of me get the wallet to compile with Litecoin no matter what I try. Upon using this command:

Code:
qmake "USE_UPNP=-" bitcoin-qt.pro

I get the following output:
Code:
Project MESSAGE: Building without UPNP support
The directory name is invalid.
Could not find qmake configuration fileProject MESSAGE: Building with UPNP suppo
rtRemoved plural forms as the target language has less forms.
If this sounds wrong, possibly the target language is not set or recognized.
Project MESSAGE: Building without UPNP support
The directory name is invalid.
Could not find qmake configuration fileProject MESSAGE: Building with UPNP suppo
rtRemoved plural forms as the target language has less forms.
If this sounds wrong, possibly the target language is not set or recognized.
Project MESSAGE: Building without UPNP support
The directory name is invalid.
Could not find qmake configuration fileProject MESSAGE: Building with UPNP suppo
rtRemoved plural forms as the target language has less forms.
If this sounds wrong, possibly the target language is not set or recognized.

If I then attempt to use the makefile that was generated with this command:
...

Anyone have any ideas.

Hello

Perhaps you meant "... the wallet to compile with bitcoin-qt..." not litecoin? Anyway, I believe I installed Qt 4.8.4 correctly, according to step 4 from nitrogenetics from March 05, 2013, 06:26:41 PM post
   
And I get a very similar set of messages to yours! It seems that qmake is sensitive to the formatting of the layout in bitcoin-qt.pro since I reformatted it a little and was able to get other error messages.

And I did run qtvars.bat to set up qt environment variables, ran configure, chose open source all seemed OK. Assistant, designer and demo run OK on my win XT Pro SP2 system.

Ron

I can’t say I was ever lost, but I was bewildered once for three days.
Daniel Boone (1734-1820)
hero member
Activity: 781
Merit: 501
fixed myself by change the BOOST_SUFFIX?=-mgw47-mt-sd-1_53

thanks anyway
hero member
Activity: 781
Merit: 501
hi nitro,

Thanks for great tutorial and it help me alot.
When trying to build latest bitcoind, i got some error at step 3.3 when run

Quote
mingw32-make -f makefile.mingw


it run in couple minutes and throw this error

Quote
c:/mingw/bin/../lib/gcc/mingw32/4.7.2/../../../../mingw32/bin/ld.exe: cannot fin
d -lboost_system-mgw46-mt-sd-1_53
c:/mingw/bin/../lib/gcc/mingw32/4.7.2/../../../../mingw32/bin/ld.exe: cannot fin
d -lboost_filesystem-mgw46-mt-sd-1_53
c:/mingw/bin/../lib/gcc/mingw32/4.7.2/../../../../mingw32/bin/ld.exe: cannot fin
d -lboost_program_options-mgw46-mt-sd-1_53
c:/mingw/bin/../lib/gcc/mingw32/4.7.2/../../../../mingw32/bin/ld.exe: cannot fin
d -lboost_thread-mgw46-mt-sd-1_53
c:/mingw/bin/../lib/gcc/mingw32/4.7.2/../../../../mingw32/bin/ld.exe: cannot fin
d -lboost_chrono-mgw46-mt-sd-1_53
collect2.exe: error: ld returned 1 exit status
makefile.mingw:127: recipe for target 'bitcoind.exe' failed
mingw32-make: *** [bitcoind.exe] Error 1

Any suggestions?
legendary
Activity: 2058
Merit: 1452
I followed these instruction, not sure where to find the software after it's installed, where did gitian go, I tried putt gitian-builder into the run box but it didn't work.
if the build succeeds, the files are in bitcoin-release
hero member
Activity: 630
Merit: 502
OK I'm totally stumped. Building the daemon works fine but I can't for the life of me get the wallet to compile with Litecoin no matter what I try. Upon using this command:

Code:
qmake "USE_UPNP=-" bitcoin-qt.pro

I get the following output:
Code:
Project MESSAGE: Building without UPNP support
The directory name is invalid.
Could not find qmake configuration fileProject MESSAGE: Building with UPNP suppo
rtRemoved plural forms as the target language has less forms.
If this sounds wrong, possibly the target language is not set or recognized.
Project MESSAGE: Building without UPNP support
The directory name is invalid.
Could not find qmake configuration fileProject MESSAGE: Building with UPNP suppo
rtRemoved plural forms as the target language has less forms.
If this sounds wrong, possibly the target language is not set or recognized.
Project MESSAGE: Building without UPNP support
The directory name is invalid.
Could not find qmake configuration fileProject MESSAGE: Building with UPNP suppo
rtRemoved plural forms as the target language has less forms.
If this sounds wrong, possibly the target language is not set or recognized.

If I then attempt to use the makefile that was generated with this command:

Code:
mingw32-make -f Makefile.Release

I get this output:
Code:
g++ -c -pipe -O2 -frtti -fexceptions -mthreads -fdiagnostics-show-option -Wall -
Wextra -Wformat -Wformat-security -Wno-unused-parameter -DUNICODE -DQT_LARGEFILE
_SUPPORT -DQT_GUI -DBOOST_THREAD_USE_LIB -DBOOST_SPIRIT_THREADSAFE -DUSE_IPV6 -D
WIN32 -D_MT -DQT_DLL -DQT_NO_DEBUG -DQT_GUI_LIB -DQT_CORE_LIB -DQT_HAVE_MMX -DQT
_HAVE_3DNOW -DQT_HAVE_SSE -DQT_HAVE_MMXEXT -DQT_HAVE_SSE2 -DQT_THREAD_SUPPORT -D
QT_NEEDS_QMAIN -I"..\Qt\4.8.4\include\QtCore" -I"..\Qt\4.8.4\include\QtGui" -I".
.\Qt\4.8.4\include" -I"src" -I"src\json" -I"src\qt" -I"..\deps\boost_1_53_0" -I"
..\deps\db-4.8.30.NC\build_unix" -I"..\deps\openssl-1.0.1e\include" -I"..\Qt\4.8
.4\include\ActiveQt" -I"build" -I"build" -I"..\Qt\4.8.4\mkspecs\win32-g++" -o bu
ild\bitcoin.o src\qt\bitcoin.cpp
In file included from ..\deps\boost_1_53_0/boost/thread/shared_mutex.hpp:18:0,
                 from ..\deps\boost_1_53_0/boost/thread/detail/thread_group.hpp:
9,
                 from ..\deps\boost_1_53_0/boost/thread/thread.hpp:26,
                 from ..\deps\boost_1_53_0/boost/thread.hpp:13,
                 from src/util.h:22,
                 from src/bignum.h:13,
                 from src/main.h:10,
                 from src/wallet.h:9,
                 from src/init.h:9,
                 from src\qt\bitcoin.cpp:11:
..\deps\boost_1_53_0/boost/thread/win32/shared_mutex.hpp: In constructor 'boost:
:shared_mutex::shared_mutex()':
..\deps\boost_1_53_0/boost/thread/win32/shared_mutex.hpp:98:33: warning: missing
 initializer for member 'boost::shared_mutex::state_data::shared_waiting' [-Wmis
sing-field-initializers]
..\deps\boost_1_53_0/boost/thread/win32/shared_mutex.hpp:98:33: warning: missing
 initializer for member 'boost::shared_mutex::state_data::exclusive' [-Wmissing-
field-initializers]
..\deps\boost_1_53_0/boost/thread/win32/shared_mutex.hpp:98:33: warning: missing
 initializer for member 'boost::shared_mutex::state_data::upgrade' [-Wmissing-fi
eld-initializers]
..\deps\boost_1_53_0/boost/thread/win32/shared_mutex.hpp:98:33: warning: missing
 initializer for member 'boost::shared_mutex::state_data::exclusive_waiting' [-W
missing-field-initializers]
..\deps\boost_1_53_0/boost/thread/win32/shared_mutex.hpp:98:33: warning: missing
 initializer for member 'boost::shared_mutex::state_data::exclusive_waiting_bloc
ked' [-Wmissing-field-initializers]
In file included from ..\deps\db-4.8.30.NC\build_unix/db.h:30:0,
                 from ..\deps\db-4.8.30.NC\build_unix/db_cxx.h:64,
                 from src/db.h:15,
                 from src/main.h:14,
                 from src/wallet.h:9,
                 from src/init.h:9,
                 from src\qt\bitcoin.cpp:11:
c:\mingw\bin\../lib/gcc/mingw32/4.6.2/../../../../include/pthread.h: At global s
cope:
c:\mingw\bin\../lib/gcc/mingw32/4.6.2/../../../../include/pthread.h:585:24: erro
r: conflicting declaration 'typedef struct ptw32_handle_t pthread_t'
src/util.h:555:16: error: 'pthread_t' has a previous declaration as 'typedef voi
d* pthread_t'
In file included from ..\deps\boost_1_53_0/boost/interprocess/errors.hpp:37:0,
                 from ..\deps\boost_1_53_0/boost/interprocess/exceptions.hpp:20,

                 from ..\deps\boost_1_53_0/boost/interprocess/shared_memory_obje
ct.hpp:17,
                 from ..\deps\boost_1_53_0/boost/interprocess/ipc/message_queue.
hpp:17,
                 from src\qt\bitcoin.cpp:23:
..\deps\boost_1_53_0/boost/interprocess/detail/win32_api.hpp:861:116: warning: d
eclaration of 'void* boost::interprocess::winapi::CreateMutexA(boost::interproce
ss::winapi::interprocess_security_attributes*, int, const char*)' with C languag
e linkage [enabled by default]
..\deps\boost_1_53_0/boost/thread/win32/thread_primitives.hpp:119:55: warning: c
onflicts with previous declaration 'void* boost::detail::win32::CreateMutexA(boo
st::detail::win32::_SECURITY_ATTRIBUTES*, int, const char*)' [enabled by default
]
..\deps\boost_1_53_0/boost/interprocess/detail/win32_api.hpp:866:127: warning: d
eclaration of 'void* boost::interprocess::winapi::CreateSemaphoreA(boost::interp
rocess::winapi::interprocess_security_attributes*, long int, long int, const cha
r*)' with C language linkage [enabled by default]
..\deps\boost_1_53_0/boost/thread/win32/thread_primitives.hpp:120:55: warning: c
onflicts with previous declaration 'void* boost::detail::win32::CreateSemaphoreA
(boost::detail::win32::_SECURITY_ATTRIBUTES*, long int, long int, const char*)'
[enabled by default]
In file included from ..\deps\boost_1_53_0/boost/thread/shared_mutex.hpp:18:0,
                 from ..\deps\boost_1_53_0/boost/thread/detail/thread_group.hpp:
9,
                 from ..\deps\boost_1_53_0/boost/thread/thread.hpp:26,
                 from ..\deps\boost_1_53_0/boost/thread.hpp:13,
                 from src/util.h:22,
                 from src/bignum.h:13,
                 from src/main.h:10,
                 from src/wallet.h:9,
                 from src/init.h:9,
                 from src\qt\bitcoin.cpp:11:
..\deps\boost_1_53_0/boost/thread/win32/shared_mutex.hpp: In member function 'T
boost::shared_mutex::interlocked_compare_exchange(T*, T, T) [with T = boost::sha
red_mutex::state_data]':
..\deps\boost_1_53_0/boost/thread/win32/shared_mutex.hpp:124:103:   instantiated
 from here
..\deps\boost_1_53_0/boost/thread/win32/shared_mutex.hpp:52:99: warning: derefer
encing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
..\deps\boost_1_53_0/boost/thread/win32/shared_mutex.hpp:52:99: warning: derefer
encing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
..\deps\boost_1_53_0/boost/thread/win32/shared_mutex.hpp:53:52: warning: derefer
encing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
..\deps\boost_1_53_0/boost/thread/win32/shared_mutex.hpp:53:52: warning: derefer
encing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
In file included from ..\deps\boost_1_53_0/boost/interprocess/detail/windows_int
ermodule_singleton.hpp:26:0,
                 from ..\deps\boost_1_53_0/boost/interprocess/detail/tmp_dir_hel
pers.hpp:22,
                 from ..\deps\boost_1_53_0/boost/interprocess/shared_memory_obje
ct.hpp:22,
                 from ..\deps\boost_1_53_0/boost/interprocess/ipc/message_queue.
hpp:17,
                 from src\qt\bitcoin.cpp:23:
..\deps\boost_1_53_0/boost/interprocess/detail/intermodule_singleton_common.hpp:
 In static member function 'static ThreadSafeGlobalMap& boost::interprocess::ipc
detail::intermodule_singleton_common::get_map() [with Threa
dSafeGlobalMap = boost::interprocess::ipcdetail::intermodule_singleton_helpers::
windows_semaphore_based_map]':
..\deps\boost_1_53_0/boost/interprocess/detail/intermodule_singleton_common.hpp:
125:49:   instantiated from 'static void boost::interprocess::ipcdetail::intermo
dule_singleton_common::initialize_singleton_logic(void*&, v
olatile uint32_t&, void* (*)(ThreadSafeGlobalMap&), bool) [with ThreadSafeGlobal
Map = boost::interprocess::ipcdetail::intermodule_singleton_helpers::windows_sem
aphore_based_map, uint32_t = unsigned int, boost::interprocess::ipcdetail::inter
module_singleton_common::singleton_constructor_t = void*(bo
ost::interprocess::ipcdetail::intermodule_singleton_helpers::windows_semaphore_b
ased_map&)]'
..\deps\boost_1_53_0/boost/interprocess/detail/intermodule_singleton_common.hpp:
333:7:   instantiated from 'static void boost::interprocess::ipcdetail::intermod
ule_singleton_impl::atentry_work() [w
ith C = boost::interprocess::ipcdetail::windows_bootstamp, bool LazyInit = true,
 bool Phoenix = true, ThreadSafeGlobalMap = boost::interprocess::ipcdetail::inte
rmodule_singleton_helpers::windows_semaphore_based_map]'
..\deps\boost_1_53_0/boost/interprocess/detail/intermodule_singleton_common.hpp:
323:13:   instantiated from 'static C& boost::interprocess::ipcdetail::intermodu
le_singleton_impl::get() [with C = bo
ost::interprocess::ipcdetail::windows_bootstamp, bool LazyInit = true, bool Phoe
nix = true, ThreadSafeGlobalMap = boost::interprocess::ipcdetail::intermodule_si
ngleton_helpers::windows_semaphore_based_map]'
..\deps\boost_1_53_0/boost/interprocess/detail/tmp_dir_helpers.hpp:45:97:   inst
antiated from here
..\deps\boost_1_53_0/boost/interprocess/detail/intermodule_singleton_common.hpp:
203:93: warning: dereferencing type-punned pointer will break strict-aliasing ru
les [-Wstrict-aliasing]
..\deps\boost_1_53_0/boost/system/error_code.hpp: At global scope:
..\deps\boost_1_53_0/boost/system/error_code.hpp:214:36: warning: 'boost::system
::posix_category' defined but not used [-Wunused-variable]
..\deps\boost_1_53_0/boost/system/error_code.hpp:215:36: warning: 'boost::system
::errno_ecat' defined but not used [-Wunused-variable]
..\deps\boost_1_53_0/boost/system/error_code.hpp:216:36: warning: 'boost::system
::native_ecat' defined but not used [-Wunused-variable]
mingw32-make: *** [build/bitcoin.o] Error 1

Anyone have any ideas.
member
Activity: 84
Merit: 10
if anyone runs into problems compiling the boost library, here's probably why:
https://bitcointalksearch.org/topic/help-compiling-the-boost-libraries-195157
Pages:
Jump to: