[MacPorts] #40125: 'grok' does not build
#40125: 'grok' does not build ----------------------------+-------------------------------- Reporter: kurt.pfeifle@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.2.0 Keywords: | Port: ----------------------------+-------------------------------- My attempt to run 'port -p upgrade grok' failed. The following lines are in the log: {{{ cc -c -I/opt/local/include -I/opt/local/include/db46 conf.tab.c -o conf.tab.o In file included from conf.y:5: conf.tab.h:112:21: warning: declaration of 'struct config' will not be visible outside of this function [-Wvisibility] int yyparse (struct config *conf); ^ predicates.c:108:5: error: non-void function 'grok_predicate_regexp_init' should return a value [-Wreturn-type] return; ^ predicates.c:132:5: error: non-void function 'grok_predicate_regexp_init' should return a value [-Wreturn-type] return; ^ 2 errors generated. gnumake: *** [predicates.o] Error 1 }}} -- Ticket URL: <https://trac.macports.org/ticket/40125> MacPorts <http://www.macports.org/> Ports system for OS X
#40125: grok: error: non-void function 'grok_predicate_regexp_init' should return a value [-Wreturn-type] -----------------------------+------------------- Reporter: kurt.pfeifle@… | Owner: jim@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.2.0 Resolution: | Keywords: Port: grok | -----------------------------+------------------- Changes (by ryandesign@…): * cc: ryandesign@… (added) * owner: macports-tickets@… => jim@… * port: => grok Comment: Remember to fill in the Port field and to Cc that port's maintainer. This is a common problem when using clang, because clang is pickier about programming errors like this. Ordinarily you could fix it by blacklisting clang, however this port is not UsingTheRightCompiler so that won't help. We should fix these problems but possibly a [ticket:30868 newer version of grok] has already corrected these errors. -- Ticket URL: <https://trac.macports.org/ticket/40125#comment:1> MacPorts <http://www.macports.org/> Ports system for OS X
#40125: grok: error: non-void function 'grok_predicate_regexp_init' should return a value [-Wreturn-type] -----------------------------+------------------- Reporter: kurt.pfeifle@… | Owner: jim@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.2.0 Resolution: | Keywords: Port: grok | -----------------------------+------------------- Comment (by kurt.pfeifle@…): Replying to [comment:1 ryandesign@…]:
Remember to fill in the Port field and to Cc that port's maintainer.
Mea culpa! I forgot to fill in the Port field... Sorry! However, (a) I don't see a Cc field for the port's maintainer and (b) couldn't you do this on the web interface automatically for whenever the port field *IS* filled in? -- Ticket URL: <https://trac.macports.org/ticket/40125#comment:2> MacPorts <http://www.macports.org/> Ports system for OS X
#40125: grok: error: non-void function 'grok_predicate_regexp_init' should return a value [-Wreturn-type] -----------------------------+------------------- Reporter: kurt.pfeifle@… | Owner: jim@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.2.0 Resolution: | Keywords: Port: grok | -----------------------------+------------------- Comment (by ryandesign@…): Replying to [comment:2 kurt.pfeifle@…]:
(a) I don't see a Cc field for the port's maintainer and
It might not be shown to non project members except on the new ticket form, I'm not sure.
(b) couldn't you do this on the web interface automatically for whenever the port field *IS* filled in?
That would involve writing a Trac plugin to somehow integrate it with our ports database. Nobody has thus far investigated how this might be accomplished. -- Ticket URL: <https://trac.macports.org/ticket/40125#comment:3> MacPorts <http://www.macports.org/> Ports system for OS X
participants (1)
-
MacPorts