[ANN] [XMG] MAGI | CPU mining | mPoW | mPoS | [MagiPay]

[Mysteriousdewd]

So I compiled GMP using homebrew and then compiled wolf cpu miner again and it went through but it says there was an error? http://imgur.com/po6942b

Not sure what its asking for with this.

Someone suggested that re-running configure with the extra flags "-march=native -mtune=native -maes" might work if you use it along with this Makefile.am.

Code:

./configure CFLAGS="-O3" CXXFLAGS="-O3" -march=native -mtune=native -maes

It might work fine without the extra flags, so long as you use the updated Makefile.am. (The author said it was a fix for clang, which you appear to be using.)

So am I able to just copy and paste the makefile into the wolf-m7m folder and will it work? Cause I tried that and then attempted to configure only to tell me:

Mysteriousdewds-MacBook-Pro:wolf-m7m-cpuminer-V2 Cybertron$ ./configure CFLAGS="-O3" CXXFLAGS="-O3" -mtune=native -maes
configure: error: unrecognized option: `-mtune=native'
Try `./configure --help' for more information

Not sure how to reconfigure it to work with the makefile from cpuminer-multi.

[1714652866]

1714652866

[1714652866]

1714652866

[1714652866]

1714652866

[feldenthorne]

So am I able to just copy and paste the makefile into the wolf-m7m folder and will it work? Cause I tried that and then attempted to configure only to tell me:

Mysteriousdewds-MacBook-Pro:wolf-m7m-cpuminer-V2 Cybertron$ ./configure CFLAGS="-O3" CXXFLAGS="-O3" -mtune=native -maes
configure: error: unrecognized option: `-mtune=native'
Try `./configure --help' for more information

Not sure how to reconfigure it to work with the makefile from cpuminer-multi.

Copying/pasting that file was the idea, yes. Try the compile again without the -mtune=native and -maes flags, I suppose.

However - Spexx replied to you as well and his advice was probably better than mine. At the same time I recommended the fix that someone else came up with, Spexx said he just removed the fuse flag manually and everything compiled for him (on Windows).

I found the same bug when compiling for Windows i.e. -fuse-linker-plugin flag should not be there because it is not valid in the context used. I used a text editor to remove the string from the Makefiles (four files in all) manually. This was done after running configure and before running make. You should get a successful compile after that.

Edit: Once you have got a successful compile to go through, there is a lot you can do to make the minerd executable run faster. It does mean some extra work and editing makefiles directly which is not for the faint-hearted, but it is worth the effort. Let me know when you are ready

[Spexx]

Just to add another little bit there.

-mtune=native is an invalid switch. -march=native is the correct switch in that context. You do not specify it unless you are cross-compiling the code to be run on another machine or for another very specific reason. The default is to compile for the machine the compiler is running on anyway.

Run the configure script and it will create a total of four makefiles. One in the current folder, one in the m7 sub-folder, one in the compat sub-folder and one in the compat/jansson sub-sub-folder. The makefiles are all called Makefile.[nothing] so open each one in turn with an ordinary text editor and just replace all instances of the string -fuse-linker-plugin with nothing and remove one of the resulting extra spaces at the same time, then save the makefile. Then use the command make clean (to clear out any shit from a previous run) and then use make. It will compile.

Do not bother with the makefile.am file. That, the autogen script and the resulting configure script are riddled with bugs. I found that any flags you specify against the configure command are ignored (took me a while to realize that) and if you want flags to be used then you have to edit them directly into the makefiles. Nothing else works properly. It is a right bloody kerfuffle, but when you know what you are doing it can be sorted out and corrected.

So ... you have already run autogen and configure. Edit the four makefiles. Run make clean. Run make. You should now have a minerd.exe to play with.

Note: If you run configure again, you will have to edit all the makefiles again. I warned you ok?

[Mysteriousdewd]

Mysts attempt to keep a giant wall of text to a minimum.

I must have glossed over Spexx's reply after yours felden. Sorry about that.

Just to add another little bit there.

-mtune=native is an invalid switch. -march=native is the correct switch in that context. You do not specify it unless you are cross-compiling the code to be run on another machine or for another very specific reason. The default is to compile for the machine the compiler is running on anyway.

Run the configure script and it will create a total of four makefiles. One in the current folder, one in the m7 sub-folder, one in the compat sub-folder and one in the compat/jansson sub-sub-folder. The makefiles are all called Makefile.[nothing] so open each one in turn with an ordinary text editor and just replace all instances of the string -fuse-linker-plugin with nothing and remove one of the resulting extra spaces at the same time, then save the makefile. Then use the command make clean (to clear out any shit from a previous run) and then use make. It will compile.

Do not bother with the makefile.am file. That, the autogen script and the resulting configure script are riddled with bugs. I found that any flags you specify against the configure command are ignored (took me a while to realize that) and if you want flags to be used then you have to edit them directly into the makefiles. Nothing else works properly. It is a right bloody kerfuffle, but when you know what you are doing it can be sorted out and corrected.

So ... you have already run autogen and configure. Edit the four makefiles. Run make clean. Run make. You should now have a minerd.exe to play with.

Thanks Spexx and feldenthorne. You guys have been amazing in helping me out. On my mac I only had 3 makefiles to edit but once I removed the  -fuse-linker-plugin line and ran make clean the make worked perfectly. It produced one warning but minerd is now sitting there in the wolf-m7m folder.

A question for Spexx, what did you mean by the extra spaces in the makefile?

Edit: Just thought I'd throw out there also that I hit up minerd with:
minerd -a m7mhash -t 6 -s 4 -o stratum+tcp://mining.m-hash.com:3334 -u Weblogin.WorkerName -p WorkerPassword
Like what is in the coinmagi pool and this is my output: http://imgur.com/po6942b

So happy to see it say yay!! Thanks so much guys.

[feldenthorne]

Thanks Spexx and feldenthorne. You guys have been amazing in helping me out. On my mac I only had 3 makefiles to edit but once I removed the  -fuse-linker-plugin line and ran make clean the make worked perfectly. It produced one warning but minerd is now sitting there in the wolf-m7m folder.

A question for Spexx, what did you mean by the extra spaces in the makefile?

Edit: Just thought I'd throw out there also that I hit up minerd with:
minerd -a m7mhash -t 6 -s 4 -o stratum+tcp://mining.m-hash.com:3334 -u Weblogin.WorkerName -p WorkerPassword
Like what is in the coinmagi pool and this is my output: http://imgur.com/nsoxKM7

So happy to see it say yay!! Thanks so much guys.

Nah, it was mostly Spexx's advice that got you through this. Almost everything I said was what he suggested in different words... aside from when I was giving the bad advice and he was giving the correct advice.

I'm glad you got everything working, though. Congratulations and have fun mining.

As for what Spexx meant, I can only assume he was talking about the two whitespace characters surrounding the -fuse-linker-plugin flag. In the Makefiles, it was shown as "(other stuff) -fuse-linker-plugin (other stuff)", so he was telling you to remove one of the cushioning spaces on either side of the flag. (I think.)

[Spexx]

^^ yep the whitespace was what I meant.

[Spexx]

minerd -a m7mhash -t 6 -s 4 -o stratum+tcp://mining.m-hash.com:3334 -u Weblogin.WorkerName -p WorkerPassword

Just spotted this. Bad advice from the pool there

The -s 4 is not required and the -t 6 is only appropriate if you have a CPU with 6 cores. Just omit those two switches and run the minerd again. It will work out the -t thing for itself and the -s thing is irrelevant.

Happy hashing

[ljm81new_again]

Somebody has clearly got gpu miners... well unless you got nasa mining lol

[lahlor]

Somebody has clearly got gpu miners... well unless you got nasa mining lol

is that a joke? Or what exactly did you mean with gpu miner?

[Spexx]

Somebody has clearly got gpu miners... well unless you got nasa mining lol

So what?

Every time they send in the bulldozers, we close down the mine.

That's the way it was designed to work. That's the way it works.

[ljm81new_again]

Just a observation i aint sayin to do nothing i anit got a dog in this one, i will say it looks like you got a good coin tho..

kinda unfair on the rest off you tho stuck mining at 60 -70 kh on a 8core haswell earning 3 coins a day tho just cuz the bullys hit the bank.

[ljm81new_again]

Way too many "thos" in that sentence... sorry about that not long got up lol

[111magic]

No problem take some coffee first!
Notice your post here for the first time/day.
Welcome in our Magical Magi community.

[okae]

Just a observation i aint sayin to do nothing i anit got a dog in this one, i will say it looks like you got a good coin tho..

kinda unfair on the rest off you tho stuck mining at 60 -70 kh on a 8core haswell earning 3 coins a day tho just cuz the bullys hit the bank.

agree with you about it, is unfair, i just turn off my cpu minner cause of that, during last 2 weeks there is a big bulldozer trying to fu*k the block rewards, so in the end what we are doing is to wasted our time and energy because we will get nothing.

is so sad, but i will not turn my cpu again untill "he" continue doing it. i love this coin but havent sense to wasted energy for nothing.

[okae]

ohh btw dont be wrong with me, what i sayd is that someone is trying to fu*ck it or he does not understand how this good coin works, the block reward sytem is pretty fair and pretty good, so in the end "he" is doing it for "nothing"

my cpu is just in "pause", but be 100% sure i will continue here

[111magic]

ohh btw dont be wrong with me, what i sayd is that someone is trying to fu*ck it or he does not understand how this good coin works, the block reward sytem is pretty fair and pretty good, so in the end "he" is doing it for "nothing"

my cpu is just in "pause", but be 100% sure i will continue here

Thanks okae! Thats good to hear!

[Spexx]

It really is a shame that these people spoil it for everybody. Excessive hashrates like that should be pointed at the XMG multipool, not at the XMG blockchain.

XMG is the only coin that operates this block reward limiting system afaik, so it is likely that these people are simply ignorant of the facts and just think "hash harder, more beer, doh" like with most other mining paradigms.

With XMG you have to work smart, not hard. This is why we have the principle of Sweet Spot targeting. My main machines will be running at 20% speed until the bulldozers piss off cease operations and the block rewards start to rise again.

Pool operators need to wise-up to this and start imposing a) sensible limits and b) banning obvious multiple account names - yeah I see that too. Pool operator's pockets are hit just as hard as the regular miners when these knuckle-dragging boneheads come along.

[Spexx]

Additional:

I would like to point out that our latest XMG mining pool operates the same 250 Kh/s limit as the Coinmagi Proof-of-Mining pool, which is something to be admired.

Please show your support by switching away from pools that allow these bulldozers to operate unchecked. A good solid boycott might just drive the message home.

Join us at Cloud2b mining pool:-

https://xmg.cloud2b.de/index.php

point your miners at stratum+tcp://xmg.cloud2b.de:3333

You know it makes sense

[okae]

It really is a shame that these people spoil it for everybody. Excessive hashrates like that should be pointed at the XMG multipool, not at the XMG blockchain.

i think that this is the point, why pools didnt do it?, they need something really complicated to apply it or what?

i think most of us will agree if all pools do it, yes? something like put some type of khs top.

[111magic]

Additional:

I would like to point out that our latest XMG mining pool operates the same 250 Kh/s limit as the Coinmagi Proof-of-Mining pool, which is something to be admired.

Please show your support by switching away from pools that allow these bulldozers to operate unchecked. A good solid boycott might just drive the message home.

Join us at Cloud2b mining pool:-

https://xmg.cloud2b.de/index.php

point your miners at stratum+tcp://xmg.cloud2b.de:3333

You know it makes sense

Good words Spexx.
If people would like to join the Proof of Mining you can also use the new pool!!!