Bug: Error build with cmd "make -jX nimbus_beacon_node" about nimbus-eth2 HOT 11 OPEN

Related issues:

• status-im/nim-secp256k1#56
• waku-org/nwaku#2560
• status-im/nimbus-eth1#2127

from nimbus-eth2.

@tranphuocanh0207 if you run gcc -march=native -Q --help=target and look for march, mcpu, and mtune values, what does it show in your case? e.g.

$ gcc -march=native -Q --help=target | grep -E '(march|mcpu|mtune)='
  -march=                     		znver3
  -mcpu=                      		
  -mtune=                     		znver3

Testing gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0 it does not support znver4; this must come in gcc 12/13/14:

cc1: note: valid arguments to '-march=' switch are: nocona core2 nehalem corei7 westmere sandybridge corei7-avx ivybridge core-avx-i haswell core-avx2 broadwell skylake skylake-avx512 cannonlake icelake-client rocketlake icelake-server cascadelake tigerlake cooperlake sapphirerapids alderlake bonnell atom silvermont slm goldmont goldmont-plus tremont knl knm x86-64 x86-64-v2 x86-64-v3 x86-64-v4 eden-x2 nano nano-1000 nano-2000 nano-3000 nano-x2 eden-x4 nano-x4 k8 k8-sse3 opteron opteron-sse3 athlon64 athlon64-sse3 athlon-fx amdfam10 barcelona bdver1 bdver2 bdver3 bdver4 znver1 znver2 znver3 btver1 btver2 native

it should be one of those listed valid arguments in each case.

Furthermore, if you then substitute in place of native in:

 switch("passC", "-march=znver3") 
 switch("passL", "-march=znver3") 

(or whatever it shows)

does it still reproduce this issue?

from nimbus-eth2.

Oh, command "gcc -march=native -Q --help=target" is the same as your e.g.
And the solution of replacing "native" with "znver3" in config.nims worked. Thanks for your help.

from nimbus-eth2.

That's strange, but, glad you were able to built it by specifying -march=znver3 directly. It should work regardless, but this is a potential workaround until a root cause is discovered.

from nimbus-eth2.

Yes, I hope it doesn't encounter any unexpected errors. Thanks you!!!

from nimbus-eth2.

@tersec It's working, but it's not stable because of this error.

from nimbus-eth2.

That stack trace looks like the symbol non-demangling one gets using Nim 2.0. What version of Nim is being used to compile this?

from nimbus-eth2.

@tersec I'm not sure, but with these errors it's quite dangerous during validator operation. I decided to switch to another device with an Intel CPU, hopefully it will be more stable.

from nimbus-eth2.

Nim 2.0

it's also backported to 1.6.20

from nimbus-eth2.