Opened 12 years ago
Closed 9 years ago
#37543 closed defect (fixed)
syck: error: conflicting types for 'syckparse'
Reported by: | ryandesign (Ryan Carsten Schmidt) | Owned by: | lharple@… |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.1.2 |
Keywords: | haspatch | Cc: | kurthindenburg (Kurt Hindenburg) |
Port: | syck |
Description
gram.h:107:5: error: conflicting types for 'syckparse' int syckparse (void); ^ ./syck.h:471:5: note: previous declaration is here int syckparse( void * ); ^ 1 error generated. make[2]: *** [gram.o] Error 1
Attachments (5)
Change History (9)
Changed 12 years ago by ryandesign (Ryan Carsten Schmidt)
comment:1 follow-up: 2 Changed 12 years ago by ryandesign (Ryan Carsten Schmidt)
Keywords: | haspatch added |
---|
Changed 12 years ago by ryandesign (Ryan Carsten Schmidt)
Attachment: | syck-bison.diff added |
---|
Changed 12 years ago by ryandesign (Ryan Carsten Schmidt)
Attachment: | patch-configure.diff added |
---|
comment:2 Changed 12 years ago by ryandesign (Ryan Carsten Schmidt)
Replying to ryandesign@…:
Unless you know a way to make syck work with newer bison, which would be preferable in case future OS X includes a newer bison.
In fact here is the upstream bug report: https://github.com/indeyets/syck/issues/10
And the fix that was committed to make it build with bison 2.6 and newer: https://github.com/indeyets/syck/commit/4c0e9b5e2e9fa93f18c850f4a9c2cfe0e835b7d1
New patches attached.
Changed 12 years ago by ryandesign (Ryan Carsten Schmidt)
Attachment: | syck-bison.2.diff added |
---|
Changed 12 years ago by ryandesign (Ryan Carsten Schmidt)
Attachment: | patch-bison-2.6.diff added |
---|
comment:4 Changed 9 years ago by kurthindenburg (Kurt Hindenburg)
Resolution: | → fixed |
---|---|
Status: | new → closed |
done r144941
Note: See
TracTickets for help on using
tickets.
This happens if bison @2.7_0 is installed. Attached is a patch to fix this by forcing the use of the system's copy of bison, which on Mountain Lion is still 2.3. The configure script provides the variable "YACC" to override the automatic detection, unfortunately the configure script then checks to make sure it has not been overridden and bails out if it has, therefore the patch for the configure script is needed to remove that check. May I commit these patches? Unless you know a way to make syck work with newer bison, which would be preferable in case future OS X includes a newer bison.