I’ve had this issue last week in Big Sur, indeed appending the && false to that line in configure.in helped fix it 
This thread describes how to deal with it in the context of asdf builds:
https://github.com/asdf-vm/asdf-erlang/issues/161#issuecomment-731477842
