Opened 17 years ago

Closed 16 years ago

Last modified 16 years ago

#14498 closed defect (invalid)

mod_perl2 not building (MacOS X 10.4, 10.5)

Reported by: ajmas (Andre-John Mas) Owned by: ryan@…
Priority: Normal Milestone:
Component: ports Version: 1.6.0
Keywords: Cc: blb@…
Port: mod_perl2

Description

I am trying to install mod_perl2 on my 10.4 (server) machine and I am getting the following error:

--->  Configuring mod_perl2
Error: Target org.macports.configure returned: shell command "cd /opt/ 
local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_www_mod_perl2/work/mod_perl-2.0.3 &&  /opt/ 
local/bin/perl Makefile.PL MP_APXS=/opt/local/apache2/bin/apxs"  
returned error 133
Command output: dyld: Library not loaded: /usr/lib/libdl.0.dylib
   Referenced from: /opt/local/bin/perl
   Reason: image not found

Further analysis shows that libdl.0.dylib doesn't exist on MacOS X 10.5 (non-server) either. On the other hand libdl.dylib does exist. A temporary work-around involves making a symbolic link:

  ln -s /usr/lib/libdl.dylib /usr/lib/libdl.0.dylib

Change History (6)

comment:1 in reply to:  description Changed 17 years ago by danielluke (Daniel J. Luke)

Replying to andrejohn.mas@gmail.com:

Referenced from: /opt/local/bin/perl

Did you try rebuilding macports perl? It looks like it is what is linked to that library that doesn't exist.

comment:2 Changed 17 years ago by jmroot (Joshua Root)

Cc: ryan@… added
Milestone: Port Bugs

Cc maintainer.

comment:3 Changed 16 years ago by blb@…

Cc: blb@… added; ryan@… removed
Owner: changed from macports-tickets@… to ryan@…
Port: mod_perl2 added

It's odd that perl would ever link against a library that doesn't exist; as dluke asked, have you tried rebuilding the perl5.8 port?

comment:4 Changed 16 years ago by ajmas (Andre-John Mas)

I am wondering whether I upgraded from 10.4 to 10.5 when I got that issue.

I can't reproduce the issue any more, having done a clean install, so I would recommend closing the ticket. If someone else comes across the issue we'll just reopen as necessary.

comment:5 in reply to:  4 Changed 16 years ago by blb@…

Resolution: invalid
Status: newclosed

Replying to andrejohn.mas@…:

I am wondering whether I upgraded from 10.4 to 10.5 when I got that issue.

Reinstalling everything in that case is actually the recommended path, unfortunately, due to how many ports are built with OS-version-specific bits.

comment:6 Changed 16 years ago by (none)

Milestone: Port Bugs

Milestone Port Bugs deleted

Note: See TracTickets for help on using tickets.