Re: [129391] trunk/dports/perl/p5-cgi-speedycgi/Portfile

2014-12-12 Thread Mojca Miklavec
On Fri, Dec 12, 2014 at 10:38 PM, David Evans wrote: > On 12/12/14 11:54 AM, Ryan Schmidt wrote: >>> On Dec 12, 2014, at 8:49 AM, mo...@macports.org wrote: >>> >>> @@ -1,10 +1,13 @@ >>> # -*- coding: utf-8; mode: tcl; tab-width: 4; indent-tabs-mode: nil; >>> c-basic-offset: 4 -*- vim:fenc=utf-8:f

Re: Help with elkhound port development

2014-12-12 Thread Lawrence Velázquez
On Dec 12, 2014, at 10:28 PM, Brandon Allbery wrote: > I already answered this one: the program makes an assumption about how much > of the bison header it needs to take, one which is incorrect for bison 3 as > is currently in MacPorts We currently provide Bison 2.7.1. vq

Re: port doctor patch

2014-12-12 Thread Joshua Root
On 2014-12-13 16:18 , Joshua Root wrote: > On 2014-12-13 15:36 , Kurt Hindenburg wrote: >> Hello, >> Since I have https://trac.macports.org/wiki/UsingTheRightCompiler#testing >> installed, port doctor fails one test. Attached is a quick patch to just >> ignore the cache test for this case. >

Re: port doctor patch

2014-12-12 Thread Joshua Root
On 2014-12-13 15:36 , Kurt Hindenburg wrote: > Hello, > Since I have https://trac.macports.org/wiki/UsingTheRightCompiler#testing > installed, port doctor fails one test. Attached is a quick patch to just > ignore the cache test for this case. >Comments? It would make more sense to cha

port doctor patch

2014-12-12 Thread Kurt Hindenburg
Hello, Since I have https://trac.macports.org/wiki/UsingTheRightCompiler#testing installed, port doctor fails one test. Attached is a quick patch to just ignore the cache test for this case. Comments? Kurt doctor.tcl.diff Description: Binary data

Re: Help with elkhound port development

2014-12-12 Thread Brandon Allbery
On Fri, Dec 12, 2014 at 9:59 PM, Mark Brethen wrote: > > Now, when building I had 5 errors: > > :info:build perl ../smbase/run-flex.pl > > -oagramlex.yy.cc > > agramlex.lex > :info:build flex -oagramlex.yy.cc > > agramlex.lex > :info:build modifying agramlex.yy.cc > > > :info:build c++ -c -o agram

Re: Help with elkhound port development

2014-12-12 Thread Mark Brethen
On Dec 12, 2014, at 7:38 PM, Ryan Schmidt wrote: > > On Dec 12, 2014, at 7:18 PM, Mark Brethen wrote: >> >> On Dec 12, 2014, at 1:58 PM, Ryan Schmidt wrote: >> >>> On Dec 12, 2014, at 1:26 PM, Mark Brethen wrote: >>> PortSystem 1.0 PortGroup github 1.0

Re: Help with elkhound port development

2014-12-12 Thread Ryan Schmidt
On Dec 12, 2014, at 7:18 PM, Mark Brethen wrote: > > On Dec 12, 2014, at 1:58 PM, Ryan Schmidt wrote: > >> On Dec 12, 2014, at 1:26 PM, Mark Brethen wrote: >> >>> PortSystem 1.0 >>> PortGroup github 1.0 >>> >>> github.setupWeiDUorg elkhound 2014-08-03 >> >>> distnam

Re: Help with elkhound port development

2014-12-12 Thread Mark Brethen
On Dec 12, 2014, at 1:58 PM, Ryan Schmidt wrote: > > On Dec 12, 2014, at 1:26 PM, Mark Brethen wrote: > >> PortSystem 1.0 >> PortGroup github 1.0 >> >> github.setupWeiDUorg elkhound 2014-08-03 > >> distname${version} >> master_siteshttps://githu

Re: [129391] trunk/dports/perl/p5-cgi-speedycgi/Portfile

2014-12-12 Thread David Evans
On 12/12/14 11:54 AM, Ryan Schmidt wrote: On Dec 12, 2014, at 8:49 AM, mo...@macports.org wrote: Revision 129391 Author mo...@macports.org Date 2014-12-12 06:49:41 -0800 (Fri, 12 Dec 2014) Log Message p5-cgi-speedycgi: add p5.18 5.20 to an otherwise broken port (#33479) Modified Paths

Re: Help with elkhound port development

2014-12-12 Thread Ryan Schmidt
On Dec 12, 2014, at 1:26 PM, Mark Brethen wrote: > PortSystem 1.0 > PortGroup github 1.0 > > github.setupWeiDUorg elkhound 2014-08-03 > distname${version} > master_siteshttps://github.com/${github.author}/${name}/archive/ You're usually using the

Re: [129391] trunk/dports/perl/p5-cgi-speedycgi/Portfile

2014-12-12 Thread Ryan Schmidt
> On Dec 12, 2014, at 8:49 AM, mo...@macports.org wrote: > > Revision > 129391 > Author > mo...@macports.org > Date > 2014-12-12 06:49:41 -0800 (Fri, 12 Dec 2014) > Log Message > > p5-cgi-speedycgi: add p5.18 5.20 to an otherwise broken port (#33479) > Modified Paths > > • trunk/dports/pe

Re: Help with elkhound port development

2014-12-12 Thread Brandon Allbery
On Fri, Dec 12, 2014 at 2:08 PM, Mark Brethen wrote: > > :info:build head -n 73 agrampar.tab.h > agrampar.codes.h > :info:build c++ -c -o agrampar.tab.o agrampar.tab.cc > > -g -Wall -Wno-deprecated -D__UNIX__ -O2 -DNDEBUG -I../smbase > :info:build c++ -c -o ccsstr.o ccsstr.cc -g -Wall -Wno-depreca

Re: Help with elkhound port development

2014-12-12 Thread Mark Brethen
This is a build dependency for a program I want to use (and also port). The author does provide a pre-built elkhound for mac os as a separate download. Below is the current state of my Portfile (if you want to check out the source): PortSystem 1.0 PortGroup github 1.0 github.

Re: Help with elkhound port development

2014-12-12 Thread Brandon Allbery
On Fri, Dec 12, 2014 at 2:08 PM, Mark Brethen wrote: > > :info:build bflatten.cc:35:10: warning: cast to 'const void *' from > smaller integer type 'int' [-Wint-to-void-pointer-cast] > This indicates that the port is not 64-bit clean and you may have to force the arch to i386 (32-bit) to avoid cr

Help with elkhound port development

2014-12-12 Thread Mark Brethen
I'm attempting to create a port for elkhound (a GLR Parser Generator) but running into build issues. :notice:configure ---> Configuring elkhound :debug:configure Using compiler 'Xcode Clang' :debug:configure Executing org.macports.configure (elkhound) :info:configure Testing C++ compiler ... :i

Re: Subport known but not found (was: Re: "concurrent" qt4-mac: request feedback & testing for current port phase in Portfile?)

2014-12-12 Thread René J . V . Bertin
On Friday December 12 2014 12:03:48 Ryan Schmidt wrote: > > I have yet to figure out the rules here, but one thing I tripped over when > > I was experimenting with subports is that this can be recursive. That is, > > if you select the subport, then $name is the subport name and the subport > >

Re: Subport known but not found (was: Re: "concurrent" qt4-mac: request feedback & testing for current port phase in Portfile?)

2014-12-12 Thread Ryan Schmidt
On Dec 12, 2014, at 11:08 AM, Brandon Allbery wrote: > On Fri, Dec 12, 2014 at 12:05 PM, René J.V. wrote: subport ${name}-transitional { > > I have yet to figure out the rules here, but one thing I tripped over when I > was experimenting with subports is that this can be recursive. That is, if

Re: Subport known but not found (was: Re: "concurrent" qt4-mac: request feedback & testing for current port phase in Portfile?)

2014-12-12 Thread René J . V . Bertin
On Friday December 12 2014 12:08:28 Brandon Allbery wrote: > I have yet to figure out the rules here, but one thing I tripped over when > I was experimenting with subports is that this can be recursive. That is, > if you select the subport, then $name is the subport name and the subport > declarat

Re: Subport known but not found (was: Re: "concurrent" qt4-mac: request feedback & testing for current port phase in Portfile?)

2014-12-12 Thread Lawrence Velázquez
On Dec 12, 2014, at 12:31 PM, René J.V. Bertin wrote: > On Friday December 12 2014 12:21:54 Lawrence Velázquez wrote: > >> Does the variable "qt4_is_concurrent" exist? If not, the portfile itself >> throws an error and won't index. > > Yes, it exists, and portindex doesn't throw an error... P

Re: Subport known but not found (was: Re: "concurrent" qt4-mac: request feedback & testing for current port phase in Portfile?)

2014-12-12 Thread Lawrence Velázquez
On Dec 12, 2014, at 12:05 PM, René J.V. Bertin wrote: > So I'm trying to convert my +libsymlinks convenience variant into a ditto > subport, qt4-mac-transitional (better name suggestions still welcome). > > I'm stuck at the stage where I simply have > > subport ${name}-transitional { > } > if

Re: Subport known but not found (was: Re: "concurrent" qt4-mac: request feedback & testing for current port phase in Portfile?)

2014-12-12 Thread Brandon Allbery
On Fri, Dec 12, 2014 at 12:05 PM, René J.V. wrote: > > subport ${name}-transitional { > I have yet to figure out the rules here, but one thing I tripped over when I was experimenting with subports is that this can be recursive. That is, if you select the subport, then $name is the subport name an

Subport known but not found (was: Re: "concurrent" qt4-mac: request feedback & testing for current port phase in Portfile?)

2014-12-12 Thread René J . V . Bertin
By "popular request" I'm taking this to the dev ML... So I'm trying to convert my +libsymlinks convenience variant into a ditto subport, qt4-mac-transitional (better name suggestions still welcome). I'm stuck at the stage where I simply have subport ${name}-transitional { } if { ${subport} eq "

Re: How to recover from wrong port naming at time of 1st commit?

2014-12-12 Thread Marko Käning
On 11 Dec 2014, at 09:57 , Joshua Root wrote: > To clarify: nobody would have been able to install if they ran "port > install baloo-kcm-advanced" like the buildslave does. It would work if > they used the correct name. Thanks Josh, finally I “svn mv”’ed it! :-) Greets, Marko ___