Opened 13 years ago

Closed 13 years ago

Last modified 13 years ago

#33384 closed defect (invalid)

subversion-perlbindings not building with Xcode 4.3

Reported by: hyrum@… Owned by: macports-tickets@…
Priority: Normal Milestone:
Component: ports Version: 2.0.3
Keywords: Cc:
Port: subversion-perlbindings

Description

I'm attempting to install the subversion-perlbindings port, but to no avail. The error log has been attached to this ticket.

A couple of notes:

  • I'm running Macports 2.0.4
  • I'm running Xcode 4.3

As you well know, Xcode 4.3 changed the location of some of the developer tools, but from the error log, it appears the the subversion-perlbindings port is still looking for clang in /Developer. I've already forcibly rebuilt apr, as suggested here <http://www.mail-archive.com/macports-users@lists.macosforge.org/msg26667.html>, and that fixed problems with serf1 and subversion, but subversion-perlbindings still stubbornly refuse to build.

[ Meta-note: there isn't a 2.0.4 option in the Version field, yet. ]

Attachments (1)

main.log (6.4 KB) - added by hyrum@… 13 years ago.
Error log

Download all attachments as: .zip

Change History (6)

Changed 13 years ago by hyrum@…

Attachment: main.log added

Error log

comment:1 Changed 13 years ago by danielluke (Daniel J. Luke)

If you continue looking at the same thread, you'll see the solution there:

http://www.mail-archive.com/macports-users@lists.macosforge.org/msg26678.html

:)

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

Resolution: invalid
Status: newclosed

comment:3 Changed 13 years ago by hyrum@…

Resolution: invalid
Status: closedreopened

Sorry, I should have been a bit more explicit. I did follow the instructions in that thread, but it does not fix the problem:

$ sudo port -n upgrade --force perl5
--->  Computing dependencies for perl5
--->  Cleaning perl5
--->  Unable to uninstall perl5 @5.12.3_1+perl5_12, the following ports depend on it:
--->  	latexdiff @0.5_1
--->  	autoconf @2.68_2
--->  	glib2 @2.30.2_2
--->  	gtk-doc @1.18_0+python27
--->  	automake @1.11.3_0
--->  	ghostscript @9.05_0
Warning: Uninstall forced.  Proceeding despite dependencies.
--->  Deactivating perl5 @5.12.3_1+perl5_12
--->  Unable to deactivate perl5 @5.12.3_1+perl5_12, the following ports depend on it:
--->  	latexdiff @0.5_1
--->  	autoconf @2.68_2
--->  	glib2 @2.30.2_2
--->  	gtk-doc @1.18_0+python27
--->  	automake @1.11.3_0
--->  	ghostscript @9.05_0
Warning: Deactivate forced.  Proceeding despite dependencies.
--->  Cleaning perl5
--->  Uninstalling perl5 @5.12.3_1+perl5_12
--->  Cleaning perl5
--->  Computing dependencies for perl5
--->  Fetching archive for perl5
--->  Attempting to fetch perl5-5.12.3_1+perl5_12.darwin_11.noarch.tbz2 from http://packages.macports.org/perl5
--->  Fetching perl5
--->  Verifying checksum(s) for perl5
--->  Extracting perl5
--->  Configuring perl5
--->  Building perl5
--->  Staging perl5 into destroot
--->  Installing perl5 @5.12.3_1+perl5_12
--->  Activating perl5 @5.12.3_1+perl5_12
--->  Cleaning perl5
$ sudo port install subversion-perlbindings
--->  Computing dependencies for subversion-perlbindings
--->  Building subversion-perlbindings
Error: Target org.macports.build returned: shell command failed (see log for details)
Log for subversion-perlbindings is at: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_subversion-perlbindings/subversion-perlbindings/main.log
Error: Status 1 encountered during processing.
To report a bug, see <http://guide.macports.org/#project.tickets>
$ 

I'll also note that the message you reference said that somebody could "probably rebuild your perl like you rebuilt apr to get it to work," but there wasn't any followup message to indicate success or failure. In my case, the result is failure.

comment:4 Changed 13 years ago by neverpanic (Clemens Lang)

Resolution: invalid
Status: reopenedclosed

You're not rebuilding the correct port; perl5 is only a meta-port installing a couple of symlinks to your actual perl installation. Rebuild the perl5.12 port to fix the problem.

Although there was no follow-up to the mail on -users, I can confirm rebuilding your perl fixes the problem (at least it did for me).

comment:5 Changed 13 years ago by hyrum@…

Thanks for he comment about perl5 being a metaport; that wasn't immediately obvious from the mailing list thread referenced. I was able to force the rebuild of perl5.12, clean subversion-perlbindings, and then install subversion-perlbindings and everything then worked as expected.

Note: See TracTickets for help on using tickets.