On Wednesday 02 April 2008 06:26:40 Andy Dougherty wrote:
> This very minimal patch at leasts gives a brief warning about the issue.
> --- parrot-svn/config/inter/libparrot.pm 2008-03-31 15:15:42.000000000
> -0400 +++ parrot-andy/config/inter/libparrot.pm 2008-04-02
> 09:20:30.000000000 -0400 @@ -20,6 +20,7 @@
> use base qw(Parrot::Configure::Step);
>
> use Parrot::Configure::Utils ':inter';
> +use File::Spec qw(catfile);
>
>
> sub _init {
> @@ -41,6 +42,17 @@
>
> $parrot_is_shared = 0 unless $conf->data->get('has_dynamic_linking');
>
> + # Parrot can't necessarily handle a pre-existing installed shared
> + # libparrot.so. At this point, we don't know the actual name
> + # of the shared parrot library. However, 'libparrot.so' will catch
> + # at least some of the problems.
> + my $old_version = File::Spec->catfile($conf->data->get('libdir'),
> + 'libparrot.so');
Would the use of $Config{so} (or the configuration system's equivalent) and
possibly DynaLoader help make this more robust?
-- c
