Opened 13 years ago
Closed 13 years ago
#32262 closed defect (worksforme)
Cannot install Perl via MacPorts on Lion
Reported by: | jrzeznik1@… | Owned by: | ghosthound |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.0.3 |
Keywords: | Cc: | ||
Port: | perl5.12 |
Description (last modified by ryandesign (Ryan Carsten Schmidt))
No versions of Perl will compile in Lion 10.7.2 with the 4.2.1 build of Xcode. I have tried Perl 5.12, and Perl 5.14 to no avail.
Specifically, the errors I run into are as follows:
- "I can't seem to find your C library" error. I found this is alleviated somewhat by manually editing the Portfile and adding "-Dusenm=n" in the configure post-args. For what it's worth, the Darwin 11 patch alluded to in the portfile is not working and nm still throws a fit without the hack in place.
- However, Perl still does not compile even with that edit. From an earlier ticket it appears that the portfile is skipping the entire "make depend" phase, which halts the build process with errors. Trying to manually run this script (sh ./makedepend MAKE=make) also fails.
I do think this is something that really needs to be fixed asap, given that quite a few ports are directly dependent on Perl to build and run--without it, parts of the MacPorts system are literally broken and useless. As an example, I noticed this issue with Perl when trying to build dash and wget (both of which seem to demand Perl 5.12).
There have been other tickets with this issue, but yet it appears this issue has never been fully resolved.
Attachments (1)
Change History (6)
comment:1 Changed 13 years ago by jrzeznik1@…
Cc: | jrzeznik1@… added |
---|
comment:2 follow-up: 3 Changed 13 years ago by ryandesign (Ryan Carsten Schmidt)
Cc: | jrzeznik1@… removed |
---|---|
Description: | modified (diff) |
Owner: | changed from macports-tickets@… to ricci@… |
As reporter you do not need to Cc yourself. Please do however Cc the maintainer of the affected port(s).
Please supply a main.log file from the failed build. There must be something unique about your system; it appears to work fine for many other users.
comment:3 Changed 13 years ago by nbest@…
Replying to ryandesign@…:
Please supply a main.log file from the failed build. There must be something unique about your system; it appears to work fine for many other users.
I am attaching my main.log as my situation seems relevant to this ticket. It appears that perl5.12 failed while I was trying to install cdo like so:
$ sudo port install cdo +grib2 . . . ---> Fetching archive for perl5.12 ---> Attempting to fetch perl5.12-5.12.3_2.darwin_11.x86_64.tbz2 from http://packages.macports.org/perl5.12 ---> Fetching perl5.12 ---> Verifying checksum(s) for perl5.12 ---> Extracting perl5.12 ---> Applying patches to perl5.12 ---> Configuring perl5.12 ---> Building perl5.12 Error: Target org.macports.build returned: shell command failed (see log for details) Error: Failed to install perl5.12 Log for perl5.12 is at: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_perl5.12/perl5.12/main.log Error: The following dependencies were not installed: grib_api openjpeg pkgconfig glib2 perl5 perl5.12 perl5 xz netcdf curl curl-ca-bundle libidn openssl szip Error: Status 1 encountered during processing. To report a bug, see <http://guide.macports.org/#project.tickets>
I was following the procedure given at http://trac.macports.org/wiki/Migration for getting Macports going on my Lion machine, so my Macports tree was completely clean AFAIK except for hdf-18 and proj that I installed separately ahead of cdo just because I had some trouble with them before finding out what I had to do to migrate. FWIW my Lion environment was set up by bringing everything over from my Snow Leopard machine in the process of setting up my new machine, which means I had to get Xcode through the AppStore, so that's at 4.2.1. Let me know if more info is needed. Thanks.
comment:4 Changed 13 years ago by nbest@…
I can't explain this, but I seem to have gotten past this error by simply saying:
sudo port -v selfupdate sudo port upgrade outdated
Neither action did much that was obvious but it must have appeased the Macports gods somehow.
$ sudo port -v selfupdate Password: ---> Updating MacPorts base sources using rsync receiving file list ... done base.tar sent 10864 bytes received 111 bytes 7316.67 bytes/sec total size is 3226624 speedup is 294.00 receiving file list ... done base.tar.rmd160 sent 64 bytes received 116 bytes 120.00 bytes/sec total size is 512 speedup is 2.84 MacPorts base version 2.0.3 installed, MacPorts base version 2.0.3 downloaded. ---> Updating the ports tree Synchronizing local ports tree from rsync://rsync.macports.org/release/tarballs/ports.tar receiving file list ... done ports.tar sent 48638 bytes received 31761 bytes 22971.14 bytes/sec total size is 48078336 speedup is 598.00 receiving file list ... done ports.tar.rmd160 sent 64 bytes received 636 bytes 466.67 bytes/sec total size is 512 speedup is 0.73 Creating port index in /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports Adding port devel/npm Adding port devel/qbzr Adding port devel/upower Adding port editors/xemacs Adding port graphics/GraphicsMagick Adding port graphics/graphviz-devel Adding port graphics/graphviz-gui-devel Adding port graphics/gvedit-devel Adding port net/librsync Adding port net/youtube-dl Adding port python/py-celery Adding subport py26-celery Adding subport py27-celery Adding port python/py-pymongo Adding subport py25-pymongo Adding subport py26-pymongo Adding subport py27-pymongo Adding port security/policykit Adding port sysutils/beanstalkd Adding port tex/BibTool Total number of ports parsed: 20 Ports successfully parsed: 20 Ports failed: 0 Up-to-date ports skipped: 13071 ---> MacPorts base is already the latest version The ports tree has been updated. To upgrade your installed ports, you should run port upgrade outdated lep:macports nbest$ sudo port upgrade outdated Error: No ports matched the given expression
After that my original install command was able to proceed beyond perl5.12. It's still running but I'm optimistic.
comment:5 Changed 13 years ago by neverpanic (Clemens Lang)
Resolution: | → worksforme |
---|---|
Status: | new → closed |
There's been a problem regarding the gdbm port recently concerning case-sensitive vs. case-insensitive file systems. I'm just guessing, but that's what might have happened here.
Since this has been solved I'm closing this ticket.
Cc Me!