It sounded familiar... but:
https://www.redhat.com/archives/fedora-list/2005-July/msg02794.html
Hmmm...
"sh: no: command not found" errors sometimes occur in sloppy sh/bash based
feature check expressions (e.g. in configure scripts) when a variable is
assigned "no" or remains at a "no" default because something is
missing.
Thanks for the tip Michael!
Sadly the problem is more than two years old... :-(
Did you solved it? What can I check to find where the problem is?
Many thanks!
Simo