You could try to change this line in Makefile:
ifeq ($(COMP),clang)
CXX=clang++
CXXFLAGS += -pedantic -Wextra -Wshadow
-- LDFLAGS=-lpthread -fuse-ld=lld
++ LDFLAGS=-lpthread
profile_make = clang-profile-make
endif
RubiChess wrote: ↑Sun Nov 01, 2020 9:19 pm
You could try to change this line in Makefile:
ifeq ($(COMP),clang)
CXX=clang++
CXXFLAGS += -pedantic -Wextra -Wshadow
-- LDFLAGS=-lpthread -fuse-ld=lld
++ LDFLAGS=-lpthread
profile_make = clang-profile-make
endif
Andreas
After pathing the makefile, unfortunately other errors appear (some of them equal to just "make":
Unclear is the Minic configuration (NNUE file or not for engine tournaments).
And so one!
Better is if programmers give a clear announcement what they like to see in chess tournaments.
To test all the available NNUE files for so many available engines isn't possible.
As a summary, MinicNNUE based on SF code merge is (was?) a fun experiment, not official version of Minic.
As a side note, Werner tested it (http://www.cegt.net/40_40%20Rating%20Li ... s/126.html) in a rating list but accepting to give a specific name to it to clarify situation.
But, I'm now working on another implementation, please be patient
The current Minic version with or without NNUE.
If NNUE ... which of the NN files you would like to see and is most important for your own development.
I think the RubiChess solution is very good (own NNUE).
For the moment I have no idea what I have to added in my next tourney.
Minic with or without NNUE.
It would be great if you can give me a hint before the next tournament will be start ... start of January 2021.
The current Minic version with or without NNUE.
If NNUE ... which of the NN files you would like to see and is most important for your own development.
I think the RubiChess solution is very good (own NNUE).
For the moment I have no idea what I have to added in my next tourney.
Minic with or without NNUE.
It would be great if you can give me a hint before the next tournament will be start ... start of January 2021.
Best
Frank
Minic author has been very clear. Did you read the links he posted??
for that reason I have listed the program on my Tourney-2021 page without NNUE.
Yes, I read the messages.
A lot of Minic version are available since I started the tourney 2020 for around 5 months. I believe 8 versions.
2.37, 2.40, 2.45, 2.46, 2.47, 2.48, 2.52, 2.53 ... maybe others I don't saw.
Keep track of things are often complicated if I have no time to deal with something.
For the moment I am looking in Minic 2.33 for an example.
After all:
It's more interesting if programmers are very activ but for an user it's impossible to look in detail in all the available versions.
What I not understand is the own network file:
nascent nutrient = the own!
Again:
For me it's unclear to test the current Minic version with "nascent nutrient" or without the network file.
After all I understand the programmer give us the own NN file but he like more to see his program in a rating list or tourneys without network files. He like it to see that both versions are available in a rating list.
So, I can't other things do if I start to test Minic.
Same for other programs often updated ...
1-2x Wasp in the year is more as enough.
I am happy that John give me the time to test a new version before he send the next one (for an example).
Werner wrote: ↑Sat Nov 07, 2020 7:00 pm
Can we expect an official release of Rubichess 1.9 with the new network nn-803c91ad5c-20201107.nnue ?
Yes, good question. I would like to test RubiChess 1.9 with it's own nnue-net for my ratinglist, but for my machine, I need a AVX or a popcount compile!
pohl4711 wrote: ↑Sun Nov 08, 2020 10:28 am
Yes, good question. I would like to test RubiChess 1.9 with it's own nnue-net for my ratinglist, but for my machine, I need a AVX or a popcount compile!
Stefan (SPCC)
And where can you download versions of 1.9 from nnue from AVX or a popcount compile.