Topic: [ANN] ¤ DMD Diamond 3.0 | Scarce ¤ Valuable ¤ Secure | PoS 3.0 | Masternodes 65% - page 335. (Read 1260624 times)

The point is building the DMD wallet for aarch64, currently there is no support.
It all worked fine for armv6, armv7 but broke when aarch64 came along.  the reference to pooler cpuminer is because he is the author of scrypt-arm.S there is NO scrypt-aarch64.S which is required to build DMD.

I could care less about mining on an armv8 LOL.

However you do know a lot about mining and it seems also armv8

scrypt-aarch64.S is only thing holding me up from building diamond-qt and it DOES NOT exist yet ...

I am not much of a programmer (some x86 assembly years ago) and know absolutely nothing about aarch64 (armv8) or armv6 or 7.

need scrypt-aarch64.S for it to really be a solution ...

scrypt-arm.S is taken from pooler cpuminer ([email protected]) and he said:

I'm also working with OKtoshi on ROKOS for aarch64 however he does not have a board yet ...
https://bitcointalksearch.org/topic/m.14308714

I'll bet DMD foundation would post a bounty for someone to create src/srcypt-aarch64.S
here is src/srcypt-arm.S as a starting point: https://github.com/DMDcoin/Diamond/blob/master/src/scrypt-arm.S

With the release of RPi 3 out and PINE64+ imminent, there is going to be a large demand for aarch64 support.
I'm lucky to have got the Odroid C2 board, they are sold-out till mid-April.  Specs are quite similar on all Only the Odroid C2 has 2 GHZ though

I PM'ed pallas too but have not got a reply, he's into stuff like this I think ...

Should PM wolf0 too

By the way, who is DMD wallet dev nowadays ... used to be danbi but we don't hear from him much at all ...

another review:
http://www.jeffgeerling.com/blog/2016/review-odroid-c2-compared-raspberry-pi-3-and-orange-pi-plus

Thanks for bringing this up to me via PM, utahjohn.

I originally said that whatever returned after using uname -a was fine because we were talking about Raspberry Pis (1 and 2) and the makefile supports both armv6l and armv7l (which are actually identical). It's just not working with any of the previous architecture commands because of the 64-bit OS (see below).


It looks like you guys in the thread have already figured it out: someone will need to write a scrypt-aarch64.S file for everything to work smoothly.

Alternatively, I could probably have the wallet fall back to a C++ implementation on unsupported architectures. It would just need to be transparent to the users that their architecture does not perform as well as it might with its own assembly implementation. (That is to say that the performance would be really bad compared to a native solution.)

Speaking of performance hits, though, I'm pretty sure one could the ARM version of QEMU to run a 32-bit binary if you just want to run the wallet on an arm64 board. At least until a more robust solution is found. A guide for setting QEMU up on a Raspberry Pi can be found here, but I'm not sure how well that translates to ODROID's boards. You might have to set up ODROID's boards for virtualization (if they support it) and compile QEMU yourself to get things working.

Well I got firefox working (was seg faulting).
solution:
 apt-get remove firefox
 apt-get install firefox:armhf

But no luck with diamond-qt.

Now I can copy/paste from odroid command line

build/scrypt_mine.o: In function `scrypt(void const*, unsigned long, unsigned int*, void*)':
scrypt_mine.cpp:(.text+0x5c): undefined reference to `scrypt_core'
collect2: error: ld returned 1 exit status
Makefile:302: recipe for target 'diamond-qt' failed
make: *** [diamond-qt] Error 1

this is caused by scrypt_core() not being compiled.
src/scrypt-arm.S does not support aarch64 (armv8).  

From crashoverride on forum.odroid.com

I'll bet DMD foundation would post a bounty for someone to create src/srcypt-aarch64.S
here is src/srcypt-arm.S as a starting point: https://github.com/DMDcoin/Diamond/blob/master/src/scrypt-arm.S
This code is for arm 32 bit, needs to be translated to 64 bit ...

The other modifications to diamond.pro and src/makefile.unix are relativly simple just adding a few lines for aarch64 ...

If you are going to get one, they are sold-out until middle of April, however I found mine at USA distributor (may still be available there) http://ameridroid.com

Ubuntu 64 bit image for Odroid C2 is available here http://odroid.com/dokuwiki/doku.php?id=en:c2_release_linux_ubuntu

Debian 32 and 64 bit (ODROBIAN-Jessie-2.0-vanilla-s905.img.xz) image for Odroid C2 are available here http://forum.odroid.com/viewtopic.php?f=138&t=18771 (follow links to s905) http://oph.mdrjr.net/odrobian/images/s905/
For the Debian 32 version:

I think I'd prefer Debian myself as raspbian is based on it and has lots of support.  Ordered a microSD card reader/writer on e-bay so I can re-flash my card ... and run crashoveride ... see if uname -p returns armv7 ... if so at least it's a temporary solution for DMD.

If you have not ordered yet, much cheaper from manufacturer in Korea http://www.hardkernel.com/main/main.php
Shipping from Korea to Utah, USA is $16 FEDEX (I bought the 32G Ubuntu 64 eMMC 5 card, power supply, case from them).

On another subject: bitcoind 12.0 build just fine on aarch64

perhaps a scrypt-aarch64.S needs to be added or just some fixes in the #ifdef in scrypt-arm.S, this is beyond me
In any case aarch64 (armv8) fails to compile.

I'd be happy to get it running 32 bit DMD wallet for now but build scrypts fail there too (armv7l) under aarch64.

around line 73 of scrypt_mine.cpp:
insert to the #elif the following
 ||defined(__aarch64__)

this gets past the SCRYPT_BUFFER_SIZE and scrypt_core() errors
but then I get back to this one again:
src/scrypt_mine.cpp: In function 'void scrypt (const void*, size_t, uint32_t*, void*)':
src/scrypt_mine.cpp:105:21: error: 'scrypt_core' was not declared in the scope
Makefile:302: recipe for target 'diamond-qt' failed

Clearly scrypt_core() is not being generated as we are now in linking phase of build ...

There is no qt.pro file just a diamond.pro used by qmake ...
But yes it is listed in diamond.pro

This I just received in email from  [email protected]
My email:
So diamond team will have to update this for aarch64

somehow force build of scrypt-arm for aarch64 as armv7

my complete uname -a
Linux odroid64 3.14.29-37 #1 SMP PREEMPT Tue Mar 15 23:57:29 BRT 2016 aarch64 aarch64 aarch64 GNU/Linux

well this sucks, RPi3, Odroid C2, and any other aarch64 CPU out of luck

Check that scrypt-arm.S is listed under SOURCES in the qt.pro file.

perhaps a scrypt-aarch64.S needs to be added or just some fixes in the #ifdef in scrypt-arm.S, this is beyond me
In any case aarch64 (armv8) fails to compile.

I'd be happy to get it running 32 bit DMD wallet for now but build scrypts fail there too (armv7l) under aarch64.

around line 73 of scrypt_mine.cpp:
insert to the #elif the following
 ||defined(__aarch64__)

this gets past the SCRYPT_BUFFER_SIZE and scrypt_core() errors
but then I get back to this one again:
src/scrypt_mine.cpp: In function 'void scrypt (const void*, size_t, uint32_t*, void*)':
src/scrypt_mine.cpp:105:21: error: 'scrypt_core' was not declared in the scope
Makefile:302: recipe for target 'diamond-qt' failed

Clearly scrypt_core() is not being generated as we are now in linking phase of build ...

@danbi
HELP! LOL

thats not what feldenthorn said......

Ahh ... uname -p returns aarch64

did a make clean, qmake xARCHCPU=aarch64 USE_UPNP=1 and make USE_UPNP=1 xARCHCPU=aarch64

it's compiling again should take a while ... we shall see ...

src/scrypt_mine.cpp: In function 'void scrypt (const void*, size_t, uint32_t*, void*)':
src/scrypt_mine.cpp:105:21: error: 'scrypt_core' was not declared in the scope

Makefile:2203: recipe for target 'build/scrypt_mine.o' failed

around line 80 of src/scrypt_mine.cpp scrypt_core is defined as:
extern "C" void scrypt_core(uint32_t *X, uint32_t *V);

where is the code for this function i can't find it defined anywhere

Built wallet for x86-64 before and never had this problem ...

in src there is a file scrypt-arm.S, scrypt-X86.S , scrypt-X86_64.S

scrypt_core() appears to be defined in these files ...

perhaps with aarch64 no scrypt-*.S file is being selected? how do I fix this

maybe try this hint from feldenthorn:
You'd need to replace any instances of armv7l with whatever your output from the terminal command "uname -p" is.

(source: https://bit.diamonds/community/index.php/topic,85.msg510.html#msg510 )

Ran into one I cant find an answer for compiling diamond 2.0.5.7 on Ubuntu 16.04 64 bit armv8

ok another new problem: during linking:

build/scrypt_mine.o: In function 'scrypt(void const*, unsigned long, unsigned int*, void*)':
scrypt_mine.cpp: (.text+05c): undefined reference to 'scrypt_core'
collect2: error: ld returned 1 exit status
Makefile:302: recipe for target 'diamond-qt' failed

I give up for tonight, will wait for new wallet source.  diamond.pro or Makefile or src/makefile.unix needs update for armv8 I don't know why I cant figure this out ... tried qmake USE_PNP=1 xARCHCPU=armv7l ...

half way done
had a few crashes of the PI2 and lost days
i run the PI2 now without overclock and in console mode only lets see if that was the issue

My Odroid C2 is on truck for delivery, should arrive sometime this morning
Supported by several flavors of linux.  I'm gonna start with Ubuntu 64 bit (16.04 LTS).
Will also get another eMMC 5 card for Kali Linux (Penetration testing).

Interesting, FEDEX 2 day shipping from Korea (Here already) faster than US Postal service 2 day shipping (not here yet)

@cryptonit
How is your sync going?  I plan to just copy blockchain over on flash drive from windows box to save time.
Would sure like to see new wallet release soon

OK it's all here, just booted up 64 bit Ubuntu, running apt-get update upgrade right now.
This thing is really fast booting! Will build wallet next ...

Couple updates for github ... libboost1.58 and libdb5.3 are current incarnations with Ubuntu
Also libssl-dev needs to be installed, and libdb++-dev

Finally compile running ... see if it finishes

yet another required library: libminiupnpc-dev

did request ROKOS guys to have a look into it and support Qdroid C2 too

no volume .....
no interesting trading pairs....
no DMD ......

best thing is have no wallets on PC where u doing mining
basical have wallets just on PCs that do nothing else than  run staking wallets

this together with a good anti-keylogger and malware/virus defence should help a lot

Very interesting exchange https://1ex.trade/index.php ! What does a developer?

Odroid C2 vs Raspberry Pi 3
http://hackaday.com/2016/03/02/odroid-c2-bests-raspberry-pi-3-in-several-ways/

Sadly - Yes - That is the site I downloaded from.  Proceed slowly and scan the shit out of everything.  First do a virustotal url scan, then scan the zip, then scan the file.  No guarantee but at least you are taking steps.  Best thing to do is get it from the github and or compile yourself.

Yes, I remember about pokeytex...