[MacPorts] #15455: srm-1.2.8 runtime error - cannot remove files
MacPorts
noreply at macports.org
Thu May 29 13:09:38 PDT 2008
#15455: srm-1.2.8 runtime error - cannot remove files
--------------------------------------------------+-------------------------
Reporter: vogt at cpsc.ucalgary.ca | Owner: macports-tickets at lists.macosforge.org
Type: defect | Status: new
Priority: Normal | Milestone: Port Bugs
Component: ports | Version: 1.6.0
Keywords: srm, dyld, fdatasync, flat namespace |
--------------------------------------------------+-------------------------
== The Error ==
srm-1.2.8 will compile fine via MacPorts. However, when you attempt to
use it to remove a file (the intended purpose of srm), the following error
occurs:
{{{
% srm myFile
dyld: lazy symbol binding failed: Symbol not found: _fdatasync
Referenced from: /opt/local/bin/srm
Expected in: flat namespace
dyld: Symbol not found: _fdatasync
Referenced from: /opt/local/bin/srm
Expected in: flat namespace
Trace/BPT trap
}}}
== Previous Report of this Error ==
This error was previously reported as Ticket #9899 approximately two years
ago, but no solution was posted to Ticket #9899. I have a patch for this
runtime error; however, I was unsure of whether I should reply to Ticket
#9899 with this patch or start a new ticket for the patch (the MacPorts
documentation seemed ambiguous on this matter: Section 7.2.2 of
[http://guide.macports.org/] seems to say that a new ticket should be
started, but Point 2 in [http://trac.macports.org/wiki/TracTicketing] says
that a reply is in order). I posted the patch to Ticket #9899
approximately one week ago, along with a request to inform me if this was
the correct course of action (as opposed to starting a new ticket). Since
I have not heard anything back, I decided it would be best to start a new
ticket for the patch.
== The Patch ==
The patch simply removes some unnecessary CFLAGS from the Portfile build
of srm-1.2.8. Since srm compiles and runs fine if you use the soruce
tarball directly from srm's homepage (i.e., not through MacPorts) with no
extra flags or configuration options, I'm not sure why these CFLAGS were
added to the Portfile build in the first place. If they were added for
compatibility purposes with an older OS X version (e.g., 10.3?), I would
have no way of testing that. Based on the report in Ticket #9899, as well
as my own experiences, srm-1.2.8 will not work properly on OS X 10.4 or
10.5 without a patch.
I have tested this patch on OS X 10.5, running the current version of
MacPorts (1.6.0).
--
Ticket URL: <http://trac.macports.org/ticket/15455>
MacPorts <http://www.macports.org/>
Ports system for Mac OS
More information about the macports-tickets
mailing list