Ok, may way forward was to run Configure in interactive mode:
Some kernels have a bug that prevents setuid #! scripts from being
secure. Some sites have disabled setuid #! scripts because of this.
First let's decide if your kernel supports secure setuid #! scripts.
(If setuid #! scripts would be secure but have been disabled anyway,
don't say that they are secure if asked.)
If you are not sure if they are secure, I can check but I'll need a
username and password different from the one you are using right now.
If you don't have such a username or don't want me to test, simply
Other username to test security of setuid scripts with? [none] <my use
"su" will (probably) prompt you for <my username>'s password.
I don't think setuid scripts are secure.
Does your kernel have *secure* setuid scripts? [n]
Some systems have disabled setuid scripts, especially systems where
setuid scripts cannot be secure. On systems where setuid scripts have
been disabled, the setuid/setgid bits on scripts are currently
useless. It is possible for perl5 to detect those bits and emulate
setuid/setgid in a secure fashion. This emulation will only work if
setuid scripts have been disabled in your kernel.
Do you want to do setuid/setgid emulation? [n] y
So are there any switches I can provide to Configure or make to avoid having to use interactive setup ('make -DENABLE_SUIDPERL"TRUE" install clean' didn't work for me)