On Dec 24, 2013, at 9:10 AM, Akim Demaille wrote:
> Is it really useful to keep these obsolete « devel » versions
> of Emacs? emacs-app-devel, emacs-snapshot, emacs-w3m-devel
Probably not. I know originally the stable release's Cocoa support was
nonexistent. I think once the build systems chang
On Mar 25, 2011, at 6:46 PM, Ryan Schmidt wrote:
> On Mar 25, 2011, at 05:40, c...@macports.org wrote:
>
>> Revision: 77277
>>http://trac.macports.org/changeset/77277
>> -checksums md5 6cc5ad566dbec5cf843dc600b1162808 \
>> +checksums doxygen-1.7.3.src.tar.gz \
>
>
I don't think the cmake modules are tailored for systems that might contain two
different versions of Qt. Ports could specify the correct version when
configuring with -D QT_INSTALL_PREFIX. Because MacPorts has both X11 and Aqua
versions, ports need to declare which windowing system should be us
On Oct 24, 2010, at 11:00 AM, Chris Scharver wrote:
> What's the best way for me to immediately halt the current phase?
To close the look on this, I used return -code error "message".
https://trac.macports.org/changeset/72692
Chris
__
>> $ sudo port -d upgrade cmake
>> .
>> -- Java version 1.6.0.22 configured successfully!
>> CMake Error at Tests/CMakeLists.txt:1630 (FILE):
>> file Internal CMake error when trying to open file:
>> /System/Library/Frameworks/JavaVM.framework/Headers/jni.h for reading.
>
> It has already been fil
