On Wed, 2 Apr 2008, �~Xл�~L�~O wrote:
> Yep!
> ls /usr/local/lib | grep 'parrot'
> give my many targets for rm and after that parrot making very well. Thanks!
This very minimal patch at leasts gives a brief warning about the issue.
On a closely related topic, I thought about changing the default in this
case to not build a shared libparrot, but dealing with the combination of
undocumented Configure.pl variables and the inability to use command-line
overrides made that patch become too large a project for me to tackle
today.
--- 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');
+ if (-e $old_version) {
+ warn("\nWarning: Building a shared parrot library may conflict " .
+ "with your previously-installed $old_version\n");
+ }
+
if (
$conf->options->get('ask')
&&
--
Andy Dougherty [EMAIL PROTECTED]
