Philippe Schaffnit schrieb:
I don't want to put any pressure on you: from a very selfish
perspective, I now know how to go around it...
You're not doing that. I want this solved so it doesn't come back later
when I understand the issue even less because I forgot all about it.
I cannot claim any deep knowledge of C, so I cannot do much to help you.
As far as I know, '-lperl' *is* a good idea, and should pick both
(though I do not know what would be the order of pre-seance if both
happened to be there, but this is not really the problem here...). To
put some assertiveness there, I've just double check, and -lsomething
does pick libsomething.a. (At least under Irix).
Also on my linux.
So I guess that doing a dirty hack around line 130 based on the absence
'$libperl' and then setting it with
finddepth ( sub { if ( $_ eq $Config::Config{libperl} ) { $libperl =
$File::Find::name } }, ( $Config::Config{installarchlib} ) );
seems realtively risk-free to me...
I am getting thoroughly confused (and I would guess this is the root of
the problem): isn't there some confusion between a dynamically linked
perl (from the OS point of view), and perl's 'Dynamic Linking': I mean I
have a static perl because the perl binary doesn't depend on a
'libperl.so', but I do use perl's "Dynamic Linking" (whatever this means
in my case...).
That might well be. :/
I don't know how often I already said this, but would you retry with a
current svn?
Puzzled,
Steffen
