[MacPorts] #21418: Tiger: unzip 6.0 fails because of lchmod?
MacPorts
noreply at macports.org
Wed Sep 16 04:57:19 PDT 2009
#21418: Tiger: unzip 6.0 fails because of lchmod?
--------------------------------------+-------------------------------------
Reporter: garribald@… | Owner: macports-tickets@…
Type: defect | Status: new
Priority: Normal | Milestone:
Component: ports | Version: 1.8.0
Keywords: unzip Tiger | Port: unzip
--------------------------------------+-------------------------------------
Comment(by garribald@…):
This might go in the right direction for a solution/patch:[[BR]]
I have changed the relevant line in the makefile (in the "unix" subfolder)
from
{{{
$(MAKE) unzips CFLAGS="-O3 -Wall -DBSD" LF2=""
}}}
to
{{{
$(MAKE) unzips CFLAGS="-O3 -Wall -DBSD -DNO_LCHMOD" LF2=""
}}}
and compiling is fine. I took that -DNO_LCHMOD flag from other
compilerflag lines from the makefile of at least as outdated systems as
Tiger is ;) :D[[BR]]
I have done the compiling outside of MacPorts, since I have not really
experiences in doing patch files, including them into MacPorts, doing all
the stuff in a local port - and I wanted to have a quick proof of the
theory right now. Maybe a more experienced user / the port maintainer
could look over it and do a Tiger specific paragraph in the portfile and
include a patch to exclude the lchmod usage for Tiger.[[BR]]
The relevant part in the /unix/makefile is in the lines 873-876
{{{
# Macintosh MacOS X (Unix-compatible enviroment), using standard compiler
macosx: unix_make
$(MAKE) unzips CFLAGS="-O3 -Wall -DBSD" LF2=""
$(STRIP) $(UNZIPS)
}}}
As said, the additional -DNO_LCHMOD in the CFLAGS seems to do the trick.
But please, test it.
--
Ticket URL: <http://trac.macports.org/ticket/21418#comment:1>
MacPorts <http://www.macports.org/>
Ports system for Mac OS
More information about the macports-tickets
mailing list