Opened 13 years ago
Closed 13 years ago
#33413 closed defect (fixed)
yafc: --with-readline configure argument is wrong
Reported by: | gabriel.salles-loustau@… | Owned by: | ryandesign (Ryan Carsten Schmidt) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.0.4 |
Keywords: | haspatch | Cc: | |
Port: | yafc |
Description
yafc remote completion doesn't work if build with the current Portfile.
It appears that yafc can't find the readline library while compiling due to a wrong configure argument.
The attached patch fix this issue.
Attachments (1)
Change History (3)
Changed 13 years ago by gabriel.salles-loustau@…
Attachment: | Portfile-yafc.diff added |
---|
comment:1 Changed 13 years ago by ryandesign (Ryan Carsten Schmidt)
Owner: | changed from macports-tickets@… to ryandesign@… |
---|---|
Port: | yafc added |
Status: | new → assigned |
Summary: | yafc @1.1.1, Rev 2 remote completion broken - Portfile fix → yafc: --with-readline configure argument is wrong |
comment:2 Changed 13 years ago by ryandesign (Ryan Carsten Schmidt)
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
Note: See
TracTickets for help on using
tickets.
It is important to provide all the details, including your OS version, Xcode version, and a log of the failure, if applicable. In this case I believe you are only experiencing the problem because you are using Xcode 4.2 or later, with which we use the clang compiler, which does not use the CPATH/LIBRARY_PATH environment variables that gcc and llvm-gcc do. yafc built fine for me, with readline support, with Xcode 3.2.6's default gcc-4.2 compiler on Snow Leopard. It also built fine when I switched to the MacPorts clang-3.0 compiler, but readline support was then not included. This means that in order to fix the problem we need to not only change the configure arg as you indicated, but also increase the port's revision so that users will be prompted to rebuild.