Re: Bison 3

Hi! Le 4 févr. 2014 à 22:41, Eric Gallager a écrit : > You might want to add yourself on CC on http://trac.macports.org/ticket/39910 > as I added some patches that allow all 3 versions of bison to be installed in > parallel to that ticket I did that, thanks. But Bison 1 is really dead, and I

Re: Bison 3

Le 26 janv. 2014 à 16:24, Akim Demaille a écrit : > What is holding the inclusion of Bison 3 in the ports? > http://trac.macports.org/ticket/41600 was opened two > months ago. Helloo! Anybody out there? How can I help? ___ macports-de

Re: Bison 3

What is holding the inclusion of Bison 3 in the ports? http://trac.macports.org/ticket/41600 was opened two months ago. Thanks! ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: Bison 3

Le 24 déc. 2013 à 22:37, Ryan Schmidt a écrit : > > On Dec 24, 2013, at 07:47, Akim Demaille wrote: > >> I do have seen that there were issues the first time Bison was >> introduced, but it is my understanding that these issues have >> been addressed. And if some

Oldish devel versions of Emacs

Is it really useful to keep these obsolete « devel » versions of Emacs? emacs-app-devel, emacs-snapshot, emacs-w3m-devel emacs @24.3_1 (editors) The GNU Emacs text editor emacs-app @24.3_1 (aqua, editors) The GNU Emacs text editor (Cocoa version) emacs-app-devel @20091101 (aqua, editors

Bison 3

Hi all, I do have seen that there were issues the first time Bison was introduced, but it is my understanding that these issues have been addressed. And if some remaining, I’d be happy to help addressing them. So how about moving forward? I don’t think forking a Bison 2 and 3 would be useful.

Re: What should be done about tickets that seem to be forgotten?

Ping! I have submitted a proposal to support qcachegrind in replacement of kcachegrind, but so far nothing happened. Cheers! ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev

What should be done about tickets that seem to be forgotten?

For instance https://trac.macports.org/ticket/34225 Cheers! ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: failing configure => dump config.log in the log

Hi all, Is there any plan to do something about this? Should I create a ticket? I don't want to stay a member of this list, I'm flooded. Cheers, Akim ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.or

failing configure => dump config.log in the log

Hi! For some reason, the configure step of Vaucanson fails on SnowLeopard; this log: > https://build.macports.org/builders/buildports-snowleopard-x86_64/builds/22196/steps/compile/logs/stdio ends with: > checking boost/regex.hpp usability... no > checking boost/regex.hpp presence... yes > confi