Why can't I compile the bitcoin source code?

[BlackHatCoiner]

Did u Reset the Ubuntu 18.04 by clicking on Advanced Options ? If not, go ahead with that and then access the Ubuntu 18.04 LTS application, create an username again and go with the build. If you haven't done that, you might run into unknown errors/warnings/exceptions again as it might clash with the older installation.

Going by the pic which you posted, didn't you install mingw-w64 cross-compilation tool chain? Also didn't you change the default compiler option to posix? I think if you didn't change the compiler option, you will get the error which you posted in the first video : 'recursive_mutex' is not a member of 'std'

If you have an unsuccessful build, try the above 2 options which I posted.

I had an unseccussful build, I tried both options you told me, and I still have unsuccessful build.

This is what it returns me after make:

Code:

blablablablah, things after make and boom errors:
make[2]: Leaving directory '/home/angelo/bitcoin/src'
make[1]: Leaving directory '/home/angelo/bitcoin/src'
Making all in doc/man
make[1]: Entering directory '/home/angelo/bitcoin/doc/man'
make[1]: Nothing to be done for 'all'.
make[1]: Leaving directory '/home/angelo/bitcoin/doc/man'
make[1]: Entering directory '/home/angelo/bitcoin'
make[1]: Nothing to be done for 'all-am'.
make[1]: Leaving directory '/home/angelo/bitcoin'
angelo@LAPTOP-NC8MQ733:~/bitcoin$ sudo bash -c "echo 1 > /proc/sys/fs/binfmt_misc/status"
[sudo] password for angelo:
angelo@LAPTOP-NC8MQ733:~/bitcoin$ make install DESTDIR=/mnt/c/workspace/bitcoin
Making install in src
make[1]: Entering directory '/home/angelo/bitcoin/src'
make[2]: Entering directory '/home/angelo/bitcoin/src'
make[3]: Entering directory '/home/angelo/bitcoin'
make[3]: Leaving directory '/home/angelo/bitcoin'
make[3]: Entering directory '/home/angelo/bitcoin/src'
make[4]: Entering directory '/home/angelo/bitcoin'
make[4]: Leaving directory '/home/angelo/bitcoin'
 /bin/mkdir -p '/mnt/c/workspace/bitcoin//lib'
 /bin/bash ../libtool --preserve-dup-deps  --mode=install /usr/bin/install -c   libbitcoinconsensus.la '/mnt/c/workspace/bitcoin//lib'
libtool: install: /usr/bin/install -c .libs/libbitcoinconsensus.dll.a /mnt/c/workspace/bitcoin//lib/libbitcoinconsensus.dll.a
/usr/bin/install: setting permissions for '/mnt/c/workspace/bitcoin//lib/libbitcoinconsensus.dll.a': Operation not permitted
Makefile:7186: recipe for target 'install-libLTLIBRARIES' failed
make[3]: *** [install-libLTLIBRARIES] Error 1
make[3]: Leaving directory '/home/angelo/bitcoin/src'
Makefile:18478: recipe for target 'install-am' failed
make[2]: *** [install-am] Error 2
make[2]: Leaving directory '/home/angelo/bitcoin/src'
Makefile:18150: recipe for target 'install-recursive' failed
make[1]: *** [install-recursive] Error 1
make[1]: Leaving directory '/home/angelo/bitcoin/src'
Makefile:788: recipe for target 'install-recursive' failed
make: *** [install-recursive] Error 1

In workspace/bitcoin this is what I get:




I am one step before giving it up... I don't get what my computer doesn't read right...

EDIT: I MADE IT!!! I just had to add that line in the end:

Code:

sudo make install DESTDIR=/mnt/c/workspace/bitcoin

[HCP]

EDIT: I MADE IT!!! I just had to add that line in the end:

Code:

sudo make install DESTDIR=/mnt/c/workspace/bitcoin

Yeah... it seems like a simple permissions error... no doubt because Windows 10 has made "C:" somewhat protected to try and prevent malware and viruses and the like... In Linux, "sudo" == "SuperUser do", so it's basically like running things as "administrator" in Windows.

Just one of the many "gotcha's" of trying to cross-compile things... made slightly more complicated by running Linux through Windows!

Glad you managed to finally get it sorted... good luck with the altcoin experimentation

[BlackHatCoiner]

EDIT: I MADE IT!!! I just had to add that line in the end:

Code:

sudo make install DESTDIR=/mnt/c/workspace/bitcoin

Yeah... it seems like a simple permissions error... no doubt because Windows 10 has made "C:" somewhat protected to try and prevent malware and viruses and the like... In Linux, "sudo" == "SuperUser do", so it's basically like running things as "administrator" in Windows.

Just one of the many "gotcha's" of trying to cross-compile things... made slightly more complicated by running Linux through Windows!

Glad you managed to finally get it sorted... good luck with the altcoin experimentation

I am now building the altcoin. Then I will see how to mine. And if I mine a new block every 10 minutes on average of course, which is very important for me. Regtest doesn't provide me.

One question, if I install on 2 different devices the altcoin, how exactly are they gonna connect? There are no IP addresses written on a txt file. (Like on bitcoin core)

Do I have to point an IP from bitcoin core's settings? What if both devices are connected on the same IP? (same router)

[HCP]

If you're using the Bitcoin Core codebase... then the default way of getting two devices to talk to one another is by using "addnode"... either from the console or in your "bitcoin.conf" file (or whatever your altcoin .conf file is meant to be called).

2 devices on the same network cannot have the same IP... even if they're on the same router, the external IP might be shared from an external viewpoint (ie. from the internet), but on the internal network (behind the router) they will indeed have different IP addresses, and should be able to connect to each other using those.

You'd need to check the network settings on each device to see what they are... and you'd most likely want to assign static IP addresses in the router setup so you can use the "addnode" in the .conf file and not have to worry about it changing.

[BlackHatCoiner]

Can I mine directly from bitcoin core? Satoshi had designed it that way so everyone could mine without any other mining softwares.

[HCP]

I believe the mining functionality was removed a long time ago (v0.12.1 was the last version to have the setgenerate command)... so the only way to "mine" with Bitcoin Core itself is when you're running a regtest environment and you use generate command.

If you want to mine, you'll need mining software (and preferably mining hardware )

[BlackHatCoiner]

If you want to mine, you'll need mining software (and preferably mining hardware )

Lol why did they do that? Why not one program for everything? Didn't satoshi vision it like that?

------------------------------------------

Started having some problems again 

I follow that guide on how to create a new altcoin. I'm quoting a text of it:

2.1 Change RPC port:

Code:

CBaseChainParams::nRPCPort in chainparamsbase.cpp

So while I have changed the ports, it still connects with the old peers:


And of course, it downloads me the entire blockchain...

This is what I've changed:



And this comes to my head. Is there any txt files with IPs inside? So I can delete it?

[HCP]

Lol why did they do that? Why not one program for everything? Didn't satoshi vision it like that?

Because it's pointless... you will never be able to mine a block on CPU/GPU anymore... ASICs have seen to that.

Started having some problems again 

At this point... I'm going to recommend you go and seek help in https://bitcointalk.org/index.php?topic=3345808.0]that Altcoin thread] or create your own thread in Altcoin Discussion board... as this thread is starting to veer away from compiling Bitcoin Core source code, and into creating an Altcoin.

That's not what this (Bitcoin Technical Support) board is for.

[BlackHatCoiner]

3. Message signature
Choose a different message start signature:

Code:

CChainParams::pchMessageStart in chainparams.cpp

pchMessageStart[0] = 0xf0;
pchMessageStart[1] = 0xb0;
pchMessageStart[2] = 0xb0;
pchMessageStart[3] = 0xd0;

what exactly do I have to change here? On my altcoin instead of that:

pchMessageStart[0] = 0xf0;
pchMessageStart[1] = 0xb0;
pchMessageStart[2] = 0xb0;
pchMessageStart[3] = 0xd0;

I did it this way:

pchMessageStart[0] = 0xb0;
pchMessageStart[1] = 0xf0;
pchMessageStart[2] = 0xb0;
pchMessageStart[3] = 0xd0;

I just change their position. Do I have to do anything else?

[BlackHatCoiner]

I would like to ask if I can install Ubuntu 18.04 LTS on a windows 7 machine. I changed the windows 10 device and now I have a desktop running windows 7.

[HCP]

Not as far as I'm aware. The Windows Subsystem for Linux (aka WSL) which allows you to install various flavours of Unix into Windows is part of Windows 10... it's not available for Windows 7. Your only option on Windows 7 would be to install Ubuntu using Virtual Machine software like Oracle Virtual Box or VMWare or similar.

[joniboini]

-snip-

It sounds like BlackHat is trying to have a dual booting machine. That should be okay, isn't it? If Windows is already installed on the machine then the bootloader that comes with Ubuntu should be able to detect it. There should be an option to boot either to Windows 7 or Ubuntu after that. It might be different if you're starting with Ubuntu and then Windows. From my experience, the Windows bootloader will not detect the Ubuntu OS and you have to fix it by repairing the GRUB bootloader.

[Heisenberg_Hunter]

Virtual Machine is slower and uses more resources compared with WSL since WSL is hypervisor type 1, while VM is hypervistor type 2.

+1 with this. I was running Ubuntu through my VM and it was not really a good experience to say. Also Microsoft has stopped the support for Windows 7 which is another double negative to be taken into consideration. Running a Ubuntu through VM isn't good either and running Windows 7 isn't good either.

If I was in the position of OP, I would take a backup of my files and would definitely move on to Linux Mint/Ubuntu (considering OP is a new user of Linux). Why anyone should really depend upon an OS which has no support from the team?

[BlackHatCoiner]

If I install Ubuntu 18.04 on a 2TB external Maxtor disk will the OS go slower?

[HCP]

Which OS? Ubuntu run natively... or Windows with Ubuntu in a VM?

If you're running Ubuntu natively from an external disk, it'll likely run slower from an external disk than from an internal one depending on interfaces being using USB vs USB2 vs USB3 etc and also due to the fact that your 2TB drive is more than likely an HDD and not an SDD.

If it's in a VM, it'll always run slower than it would natively... having said that, if you're just wanting to use it to compile Bitcoin (as per the thread), then running Ubuntu in a VM is "OK"... I run Ubuntu with Oracle Virtual Box on an i5-3570k with only 8Gig of RAM and Windows 10... it's not the fastest config, and multitasking is painful, but it's perfectly "adequate" for single "one off" tasks like compiling Bitcoin.

I also use Ubuntu with WSL on this machine depending on what I'm trying to test.


Depending on your specs, your mileage may vary

[joniboini]

If I install Ubuntu 18.04 on a 2TB external Maxtor disk will the OS go slower?

If you compare it to runnig it from internal SSD drive with 6GB/s throughput, then it is likely going to be way slower, but still usable for mose use case. If you plan to use it to host your full node, consider buying a separate SSD for your OS and use the HDD (if you can't afford SSD) for your blockchain data.

[BlackHatCoiner]

I'm not using Ubuntu on VM. I've installed the OS with a bootable usb from a youtube tutorial. It "ate" 28GB of storage, I didn't expect so much 

Anyway, I'm going to try compile bitcoin core from there. No I don't want to be a node, I want to create an altcoin, just for fun. The problem is that it is much more complex than I thought...

[BlackHatCoiner]

https://youtu.be/cOC70UoP4v0

Am I the only one that thinks the build-unix.md is too complex? Can someone give me a hand here? What am I doing wrong?

[HCP]

For starters, you ignored the message given here:



It said that you needed to run the "export" and then then "./configure" commands to set the BDB_LIBS and BDB_CFLAGS values... you didn't. Which then meant that when you attempted to run the ./configure as part of the build process... it failed here:



With the error saying that it could not find libdb_cxx headers.


From the video, it seems that you are just copy/pasting commands from the build-unix.md instructions without fully understanding what they are meant to be used for, nor which ones you actually need to use. You're not meant to use every single command... some of them are for specific setups/configurations etc. It also seems like you're not really reading/understanding some of the output and what it means either.

How much experience have you had in the past with coding/compiling on Linux based systems?

[BlackHatCoiner]

How much experience have you had in the past with coding/compiling on Linux based systems?

0