Pages:
Author

Topic: Issues building bitcoin on Windows 7 (Read 10898 times)

newbie
Activity: 17
Merit: 0
September 05, 2011, 09:31:14 PM
#29
Are you sure the AMI builds have been updated for the latest 0.4 bitcoin release?
member
Activity: 78
Merit: 11
Twitter:@watersNYC
September 05, 2011, 03:01:11 PM
#28
It does still exist, but I am not able to connect to it when I make an instance - I get the "Remote Desktop can't connect to the remote computer for one of these reasons:"

My port is forwarded for 3389, and my remote settings allow connections from computers running any version of remote desktop.
member
Activity: 78
Merit: 11
Twitter:@watersNYC
September 05, 2011, 12:40:18 PM
#27
Does that AMI still exist, and is it compatible with the 4.0 source?
legendary
Activity: 1652
Merit: 1186
Chief Scientist
February 21, 2011, 09:26:14 AM
#26
Oops, sorry-- I forgot to change the admin password.  The correct pw for that instance is:
  penguinsrule


I change the password to match the MinGW VM and updated the AMI:
  ami-d621d2bf    982440761210/BitcoinVC10
Admin password:  bitcoin development

You should change the password as soon as you login or make sure you use a security group that only allows your IP address to access the virtual machine.

newbie
Activity: 12
Merit: 0
February 21, 2011, 05:39:08 AM
#25
Here's the public AMI for the dodgy 0.3.20 VC10 build:
  ami-78cf3c11     982440761210/BitcoinVC10

Great, thanks. I launched an instance and tried logging on as Administrator with the password you gave on this thread, but no dice. Did you set this up with a different password? Or set it up to use auto-generated passwords?
LZ
legendary
Activity: 1722
Merit: 1062
P2P Cryptocurrency
February 20, 2011, 07:34:09 PM
#24
Can I somehow use it on my local computer? Can someone download it?
legendary
Activity: 1652
Merit: 1186
Chief Scientist
February 20, 2011, 02:35:09 PM
#23
Here's the public AMI for the dodgy 0.3.20 VC10 build:
  ami-d621d2bf    982440761210/BitcoinVC10

Bitcoin source is at c:\bitcoin
(all the other dependencies are in the root c:\, too).
Administrator password is:  bitcoin development
newbie
Activity: 12
Merit: 0
February 20, 2011, 11:30:01 AM
#22
I'll uninstall it from the VM and then make the image public; you'll have to download and install (and agree to the license) Visual Studio Express yourself to get it working.

Sure, that wouldn't be a problem for me. Good idea.
legendary
Activity: 1652
Merit: 1186
Chief Scientist
February 20, 2011, 11:03:38 AM
#21
Gavin, do you have / can you make public the image for the dodgy 0.3.20 VC10 build? I'd like to have a look and compare it to my home build to see if I can reproduce that rendering artifact problem. Thanks.

Yes, I have the VC10 VM.  I am hesitant to make it publicly available because it has a copy of Visual C++ 2010 Express installed, and I don't want Microsoft to sue me for redistributing their software without permission.

I'll uninstall it from the VM and then make the image public; you'll have to download and install (and agree to the license) Visual Studio Express yourself to get it working.
hero member
Activity: 756
Merit: 500
February 20, 2011, 09:04:13 AM
#20
Is this to compile a Windows binary much faster than it would on your own PC? e.g. if I did get the compile going I may find myself sitting there for X number of hours (days?) waiting for it to compile but you smart guys do it on EC2 instead...
newbie
Activity: 12
Merit: 0
February 20, 2011, 06:04:05 AM
#19
Gavin,

I found this but I could not find the download link:

http://thecloudmarket.com/image/ami-2edd2e47--bitcoinmingw

Caston, you'll have to sign up to Amazon's EC2 services, and then you can search for the image and launch an instance of it from the online AWS management console.

Gavin, do you have / can you make public the image for the dodgy 0.3.20 VC10 build? I'd like to have a look and compare it to my home build to see if I can reproduce that rendering artifact problem. Thanks.
hero member
Activity: 756
Merit: 500
February 19, 2011, 09:44:58 PM
#18
Gavin,

I found this but I could not find the download link:

http://thecloudmarket.com/image/ami-2edd2e47--bitcoinmingw
legendary
Activity: 1652
Merit: 1186
Chief Scientist
February 19, 2011, 02:20:10 PM
#17
Gavin, is this windows/mingw build environment publicly available?

Yes, it is public Amazon ami-2edd2e47   named  982440761210/BitcoinMinGW

The linux32 and linux64 amis I used to build the linux releases are also public.
hero member
Activity: 756
Merit: 500
February 19, 2011, 11:27:00 AM
#16
I just committed (to git and svn) an updated build-msw.txt
Thanks to m0mchil for putting together a working windows/mingw build environment.

And I'll be making the 0.3.20 build environment virtual machines (for Windows, Linux32, and Linux64, in the Amazon EC2 cloud) public, hopefully, if all goes well, later today.


Gavin, is this windows/mingw build environment publicly available?
legendary
Activity: 1652
Merit: 1186
Chief Scientist
February 18, 2011, 01:50:35 PM
#15
I just committed (to git and svn) an updated build-msw.txt
Thanks to m0mchil for putting together a working windows/mingw build environment.

And I'll be making the 0.3.20 build environment virtual machines (for Windows, Linux32, and Linux64, in the Amazon EC2 cloud) public, hopefully, if all goes well, later today.
hero member
Activity: 756
Merit: 500
February 18, 2011, 11:02:25 AM
#14
Thanks  lzsaver.

I got further much than I did last time... but still so far.. might try again in a week or so.
LZ
legendary
Activity: 1722
Merit: 1062
P2P Cryptocurrency
hero member
Activity: 756
Merit: 500
February 13, 2011, 11:45:30 PM
#12
Hi,

I am trying to compile bitcoin on Windows 7 64-bit with MinGW and I have found the wx, openssl and boost sources but I am still unsure as to what db_cxx.h is and where I can find it.

Please enlighten me.

Thank you,

Chris
member
Activity: 73
Merit: 10
September 30, 2010, 08:07:38 PM
#11
You should include boost libraries via -l (lowcase L) option WITHOUT lib prefix. It's added automagically by linker I guess. For linux build I included:

 -Wl,-Bstatic \
   -l boost_system \
   -l boost_filesystem \
   -l boost_program_options \
   -l boost_thread \

...not mentioning db_cxx and some others.

(is a makefile for g++ with mingw going to be the same as one natively run on linux?)

The makefile for mingw is using -l and the included defaults in the original 0.3.12 makefile looked like:

Code:
LIBS= \
 -l libboost_system-mgw34-mt-d \
 -l libboost_filesystem-mgw34-mt-d \
 -l libboost_program_options-mgw34-mt-d \
 -l libboost_thread-mgw34-mt-d \

So I did a find in the boost directory and was presented with a lot of things that looked similar so I just modified the makefile to match what the find returned...removing the -mgw45-mt-d-1_44 part makes compilation fail. Modifying my makefile too much makes it fail as well, and I don't really want to deviate too far from from what was provided as the default makefile for mingw under windows (I think what I'm doing this far is more or less working because it makes it all the way to program_options before giving me errors).

Also please note that removing 'lib' does not seem to matter, it still gets to the program_options part and fails with the same error messages I posted earlier


For example, if I run
Code:
find . -name "libboost_program_options*" -print
in my source/libraries directory I get all of this:
(output from the mingw shell)

Code:
[username]@Desktop /c/Users/[username]/Desktop/bitcoin-CUDA-svn153-src-gpl
$ find . -name "libboost_program_options*" -print
./boost/bin.v2/libs/program_options/build/gcc-mingw-4.5.0/debug/libboost_program_options-mgw45-d-1_44.dll
./boost/bin.v2/libs/program_options/build/gcc-mingw-4.5.0/debug/libboost_program_options-mgw45-d-1_44.dll.a
./boost/bin.v2/libs/program_options/build/gcc-mingw-4.5.0/debug/link-static/libboost_program_options-mgw45-d-1_44.a
./boost/bin.v2/libs/program_options/build/gcc-mingw-4.5.0/debug/link-static/runtime-link-static/libboost_program_options-mgw45-sd-1_44.a
./boost/bin.v2/libs/program_options/build/gcc-mingw-4.5.0/debug/link-static/runtime-link-static/threading-multi/libboost_program_options-mgw45-mt-sd-1_44.a
./boost/bin.v2/libs/program_options/build/gcc-mingw-4.5.0/debug/link-static/threading-multi/libboost_program_options-mgw45-mt-d-1_44.a
./boost/bin.v2/libs/program_options/build/gcc-mingw-4.5.0/debug/threading-multi/libboost_program_options-mgw45-mt-d-1_44.dll
./boost/bin.v2/libs/program_options/build/gcc-mingw-4.5.0/debug/threading-multi/libboost_program_options-mgw45-mt-d-1_44.dll.a
./boost/bin.v2/libs/program_options/build/gcc-mingw-4.5.0/release/libboost_program_options-mgw45-1_44.dll
./boost/bin.v2/libs/program_options/build/gcc-mingw-4.5.0/release/libboost_program_options-mgw45-1_44.dll.a
./boost/bin.v2/libs/program_options/build/gcc-mingw-4.5.0/release/link-static/libboost_program_options-mgw45-1_44.a
./boost/bin.v2/libs/program_options/build/gcc-mingw-4.5.0/release/link-static/runtime-link-static/libboost_program_options-mgw45-s-1_44.a
./boost/bin.v2/libs/program_options/build/gcc-mingw-4.5.0/release/link-static/runtime-link-static/threading-multi/libboost_program_options-mgw45-mt-s-1_44.a
./boost/bin.v2/libs/program_options/build/gcc-mingw-4.5.0/release/link-static/threading-multi/libboost_program_options-mgw45-mt-1_44.a
./boost/bin.v2/libs/program_options/build/gcc-mingw-4.5.0/release/threading-multi/libboost_program_options-mgw45-mt-1_44.dll
./boost/bin.v2/libs/program_options/build/gcc-mingw-4.5.0/release/threading-multi/libboost_program_options-mgw45-mt-1_44.dll.a
./boost/stage/lib/libboost_program_options-mgw45-1_44.a
./boost/stage/lib/libboost_program_options-mgw45-1_44.dll
./boost/stage/lib/libboost_program_options-mgw45-1_44.dll.a
./boost/stage/lib/libboost_program_options-mgw45-d-1_44.a
./boost/stage/lib/libboost_program_options-mgw45-d-1_44.dll
./boost/stage/lib/libboost_program_options-mgw45-d-1_44.dll.a
./boost/stage/lib/libboost_program_options-mgw45-mt-1_44.a
./boost/stage/lib/libboost_program_options-mgw45-mt-1_44.dll
./boost/stage/lib/libboost_program_options-mgw45-mt-1_44.dll.a
./boost/stage/lib/libboost_program_options-mgw45-mt-d-1_44.a
./boost/stage/lib/libboost_program_options-mgw45-mt-d-1_44.dll
./boost/stage/lib/libboost_program_options-mgw45-mt-d-1_44.dll.a
./boost/stage/lib/libboost_program_options-mgw45-mt-s-1_44.a
./boost/stage/lib/libboost_program_options-mgw45-mt-sd-1_44.a
./boost/stage/lib/libboost_program_options-mgw45-s-1_44.a
./boost/stage/lib/libboost_program_options-mgw45-sd-1_44.a


The only other thing I can maybe think of is that I should be adding .a or .dll to the end of each line...but the ones prior to program_options seem to be doing ok with out it, so I'm still stumped  Huh


In case anyone wants to take a look at the full compilation output up until the errors:
http://pastebin.com/KwaarmD2
This was not done after a fresh make clean because it would be very long, I could however provide that if it would be helpful.
full member
Activity: 185
Merit: 100
September 30, 2010, 12:52:58 PM
#10
You should include boost libraries via -l (lowcase L) option WITHOUT lib prefix. It's added automagically by linker I guess. For linux build I included:

 -Wl,-Bstatic \
   -l boost_system \
   -l boost_filesystem \
   -l boost_program_options \
   -l boost_thread \

...not mentioning db_cxx and some others.
Pages:
Jump to: