Opened 14 years ago

Closed 14 years ago

#26332 closed defect (invalid)

Problem with subversion-perl-bindings

Reported by: flaviocruz@… Owned by: danielluke (Daniel J. Luke)
Priority: Normal Milestone:
Component: ports Version: 1.9.1
Keywords: Cc: flaviocruz@…
Port: subversion-perlbindings

Description

I have a problem building p5-simple-svn due to subversion perl-bindings. I'm using OS X 10.6.

--->  Configuring subversion-perlbindings
--->  Building subversion-perlbindings
--->  Staging subversion-perlbindings into destroot
--->  Installing subversion-perlbindings @1.6.12_0
--->  Activating subversion-perlbindings @1.6.12_0
--->  Cleaning subversion-perlbindings
--->  Configuring p5-svn-simple
Error: Target org.macports.configure returned: configure failure: shell command failed
Log for p5-svn-simple is at: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_perl_p5-svn-simple/main.log
Error: The following dependencies failed to build: p5-svn-simple p5-term-readkey python26
Error: Status 1 encountered during processing.
To report a bug, see <http://guide.macports.org/#project.tickets>

On the file I have this:

:info:configure ===> Warning: SVN::Core missing or outdated.
:info:configure Please manually install SVN::Core by compiling Subversion
:info:configure (version 0.31.0 or above) with SWIG/Perl bindings,
:info:configure and try this installation process again.
:info:configure Writing Makefile for SVN::Simple::Edit
:info:configure shell command " cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_perl_p5-svn-simple/work/SVN-Simple-0.28" && /opt/local/bin/perl Makefile.PL INSTALLDIRS=vendor " returned error 2

Trying to use SVN::Core I get:

# perl -e 'use SVN::Core; print "$SVN::Core::VER_MAJOR.$SVN::Core::VER_MINOR.$SVN::Core::VER_MICRO"'
Can't find 'boot_SVN___Core' symbol in /opt/local/lib/perl5/vendor_perl/5.8.9/darwin-2level/auto/SVN/_Core/_Core.bundle
 at /opt/local/lib/perl5/vendor_perl/5.8.9/darwin-2level/SVN/Base.pm line 59
BEGIN failed--compilation aborted at /opt/local/lib/perl5/vendor_perl/5.8.9/darwin-2level/SVN/Core.pm line 5.
Compilation failed in require at -e line 1.
BEGIN failed--compilation aborted at -e line 1.

Attachments (2)

build_log.txt (105.5 KB) - added by flaviocruz@… 14 years ago.
build_log.mh.txt (624.0 KB) - added by mh@… 14 years ago.
Results of running instructions for reinstall on my own Snow Leopard MacBookPro

Download all attachments as: .zip

Change History (13)

comment:1 Changed 14 years ago by flaviocruz@…

Cc: flaviocruz@… added

Cc Me!

comment:2 Changed 14 years ago by danielluke (Daniel J. Luke)

Please attach the complete build log for subversion-perlbindings and p5-svn-simple:

Uninstall and clean each:

sudo port -f uninstall p5-svn-simple subversion-perlbindings

sudo port -dv install subversion-perlbindings p5-svn-simple | tee build_log.txt

then attach the build_log.txt file to this bug.

comment:3 Changed 14 years ago by danielluke (Daniel J. Luke)

Owner: changed from macports-tickets@… to dluke@…
Status: newassigned

comment:4 Changed 14 years ago by danielluke (Daniel J. Luke)

Port: subversion-perlbindings added

Changed 14 years ago by flaviocruz@…

Attachment: build_log.txt added

Changed 14 years ago by mh@…

Attachment: build_log.mh.txt added

Results of running instructions for reinstall on my own Snow Leopard MacBookPro

comment:5 in reply to:  2 Changed 14 years ago by mh@…

FYI, I'm running into the same error about the missing 'boot_SVN_Core' symbol. For me, it came up when I was trying to run git-svn.

comment:6 Changed 14 years ago by danielluke (Daniel J. Luke)

(Sorry for the delay, trac doesn't send out notification when someone just adds an attachment).

For both of you, it looks like the problem is that your perl is trying to build the subversion-perlbindings port with the wrong architecture (subversion is built 64 bit but the bindings are being built 32 bit).

This is probably either the result of having a 32-bit install of perl, or it's a bug in the perl5.8 port.

If it's a bug in the perl5.8 port, you may be able to work around it by installing perl5.10 or perl5.12 instead (the best way would be to install perl5 with the +perl5_10 or +perl5_12 variants). If you do this, you will also have to remove and re-install your p5-* ports.

comment:7 in reply to:  6 ; Changed 14 years ago by mh@…

Replying to dluke@…:

(Sorry for the delay, trac doesn't send out notification when someone just adds an attachment).

No problem. Thanks for replying.

For both of you, it looks like the problem is that your perl is trying to build the subversion-perlbindings port with the wrong architecture (subversion is built 64 bit but the bindings are being built 32 bit).

This is probably either the result of having a 32-bit install of perl, or it's a bug in the perl5.8 port.

If it's a bug in the perl5.8 port, you may be able to work around it by installing perl5.10 or perl5.12 instead (the best way would be to install perl5 with the +perl5_10 or +perl5_12 variants). If you do this, you will also have to remove and re-install your p5-* ports.

Hmmm. I have more than one version of Perl on my Mac. I've read that this is typical: different utilities in the OS may rely on different versions. I definitely have Perl 5.10.0. It appears to be my system Perl: when I issue perl -v I get:

This is perl, v5.10.0 built for darwin-thread-multi-2level

I've had my MacBookPro for over 3 years, and I upgraded from Tiger to Snow Panther (10.4 to 10.6), and I have had a few puzzling issues since the OS upgrade. It's possible things are out of sync in Perl land.

I also notice from the build log that I sent you this line towards the beginning:

checking for perl... /opt/local/bin/perl

My system perl is /usr/bin/local/perl -- and when I ask the one in /opt/local/bin for its version:

This is perl, v5.8.9 built for darwin-2level

I'm thinking this could be a problem. I haven't installed everything on my MBP with port. Perhaps I should install Perl 5.10 via macports and then reinstall my p5 ports, including the subversion bindings?

comment:8 in reply to:  7 ; Changed 14 years ago by danielluke (Daniel J. Luke)

Replying to mh@…:

I've had my MacBookPro for over 3 years, and I upgraded from Tiger to Snow Panther (10.4 to 10.6), and I have had a few puzzling issues since the OS upgrade. It's possible things are out of sync in Perl land.

Did you follow the migration instructions (http://trac.macports.org/wiki/Migration) after you updated? If not, MacPorts will probably not work right for you until you do.

I also notice from the build log that I sent you this line towards the beginning:

checking for perl... /opt/local/bin/perl

My system perl is /usr/bin/local/perl -- and when I ask the one in /opt/local/bin for its version:

This is perl, v5.8.9 built for darwin-2level

MacPorts uses its own libraries and binaries as much as possible (http://trac.macports.org/wiki/FAQ#ownlibs)

I'm thinking this could be a problem. I haven't installed everything on my MBP with port. Perhaps I should install Perl 5.10 via macports and then reinstall my p5 ports, including the subversion bindings?

That should work - you might also just be able to rebuild the perl5 you currently have installed per the migration instructions.

comment:9 in reply to:  8 Changed 14 years ago by mh@…

Replying to dluke@…:

Did you follow the migration instructions (http://trac.macports.org/wiki/Migration) after you updated? If not, MacPorts will probably not work right for you until you do.

I did follow those instructions, and MacPorts has generally worked well since then.

MacPorts uses its own libraries and binaries as much as possible (http://trac.macports.org/wiki/FAQ#ownlibs)

OK. That makes sense.

I'm thinking this could be a problem. I haven't installed everything on my MBP with port. Perhaps I should install Perl 5.10 via macports and then reinstall my p5 ports, including the subversion bindings?

That should work - you might also just be able to rebuild the perl5 you currently have installed per the migration instructions.

Well, since I've already migrated, I suppose I'll stick to the original plan. If MacPorts has Perl 5.10 at its disposal, then I can try out your earlier suggestion about trying a higher version of Perl.

BTW, I'm fuzzy on how to tell what's 32 bit and what's 64 bit. Is there an easy way to confirm I'm using a 64-bit version of Perl?

Thanks again for your help. I really appreciate it.

comment:10 Changed 14 years ago by danielluke (Daniel J. Luke)

The 'file' command will tell you the architecture(s) of an application:

% file /bin/ls /bin/ls: Mach-O universal binary with 2 architectures /bin/ls (for architecture x86_64): Mach-O 64-bit executable x86_64 /bin/ls (for architecture i386): Mach-O executable i386

% file /opt/local/bin/perl /opt/local/bin/perl: Mach-O 64-bit executable x86_64

comment:11 Changed 14 years ago by danielluke (Daniel J. Luke)

Resolution: invalid
Status: assignedclosed
Note: See TracTickets for help on using tickets.