Opened 15 years ago
Closed 14 years ago
#23096 closed defect (fixed)
kismet 2009-11-R1 does not build on Tiger
Reported by: | ryandesign (Ryan Carsten Schmidt) | Owned by: | nerdling (Jeremy Lavergne) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 1.8.2 |
Keywords: | Cc: | ||
Port: | kismet |
Description
kismet 2009-11-R1 does not build on Tiger. See attached output. kismet 2009-06-R1 did build on Tiger.
Attachments (1)
Change History (5)
Changed 15 years ago by ryandesign (Ryan Carsten Schmidt)
Attachment: | kismet.txt added |
---|
comment:1 Changed 15 years ago by nerdling (Jeremy Lavergne)
Status: | new → assigned |
---|
comment:2 Changed 15 years ago by nerdling (Jeremy Lavergne)
comment:4 Changed 14 years ago by nerdling (Jeremy Lavergne)
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
Changed to configure.cflags in r67926.
Note: See
TracTickets for help on using
tickets.
I don't have a tiger box for testing. Do you know if adding
configure.env CFLAGS=-fnested-functions
is all that is needed?Most of the code, including the chunk that caused the Tiger error, appears to be run with c++ and not c, so I'm unsure how to properly deal with this. c++ doesn't need the flag, and gives warnings for it. Do you have any insight?