[MacPorts] #35695: emacs @24.1 compilation error
MacPorts
noreply at macports.org
Thu Aug 16 05:59:53 PDT 2012
#35695: emacs @24.1 compilation error
------------------------------------+---------------------------------------
Reporter: e.greenwood2@… | Owner: macports-tickets@…
Type: defect | Status: new
Priority: Normal | Milestone:
Component: ports | Version: 2.1.2
Keywords: | Port: emacs @24.1
------------------------------------+---------------------------------------
My machine is running 10.6 with Xcode 4.0.2. Whenever I attempt to build
emacs from source (for example, by choosing +gtk), the build fails with
"shell command failed." An examination of the log shows compilation
errors in dired.c.
{{{
:info:build dired.c: In function ‘directory_files_internal’:
:info:build dired.c:227: error: ‘struct dirent’ has no member named
‘d_ino’
:info:build dired.c: In function ‘file_name_completion’:
:info:build dired.c:525: error: ‘struct dirent’ has no member named
‘d_ino’
:info:build dired.c: In function ‘Ffile_attributes’:
:info:build dired.c:973: warning: comparison is always true due to limited
range of data type
:info:build dired.c:973: warning: comparison is always true due to limited
range of data type
:info:build dired.c:977: warning: comparison is always true due to limited
range of data type
:info:build dired.c:977: warning: comparison is always true due to limited
range of data type
:info:build dired.c:1005: warning: comparison is always true due to
limited range of data type
:info:build dired.c:1005: warning: comparison is always true due to
limited range of data type
:info:build dired.c:1005: warning: comparison is always true due to
limited range of data type
:info:build dired.c:1005: warning: comparison is always true due to
limited range of data type
:info:build dired.c:1005: warning: comparison is always true due to
limited range of data type
:info:build dired.c:1005: warning: comparison is always true due to
limited range of data type
:info:build make[1]: *** [dired.o] Error 1
}}}
What could be causing this to occur? I see the same problem on my other
machine running 10.7 with Xcode 4.4. I just upgraded that machine from
10.6, and have tried removing and reinstalling both Xcode and MacPorts. I
can't find a similar ticket, but it seems strange that this would be
effecting both of my machines but nobody else.
--
Ticket URL: <https://trac.macports.org/ticket/35695>
MacPorts <http://www.macports.org/>
Ports system for Mac OS
More information about the macports-tickets
mailing list