Probably related to Bug 457530 zsh will not compile since configure can not find the function tgetent and assumes there is no curses library. I 'fixed' this by setting 'LDCONFIG=""' in 'make.conf'.
*** This bug has been marked as a duplicate of bug 461636 ***
*** Bug 461636 has been marked as a duplicate of this bug. ***
I hacked the ebuild to include -ltinfo if USE=tinfo is present (I believe that it has to be globally enabled, and not just for ncurses). If someone is interested: http://digamma.cs.unm.edu/~dmohr/zsh-5.0.2-r1.ebuild
This bug is still here with app-shells/zsh-5.0.2-r3. Is there something missing for the bug to be fixed ?
(In reply to Nicolas Martyanoff from comment #4) > This bug is still here with app-shells/zsh-5.0.2-r3. > > Is there something missing for the bug to be fixed ? A patch against the build system that will be accepted upstream.
(In reply to Tim Harder from comment #5) > A patch against the build system that will be accepted upstream. Actually I'm not sure this true. It builds fine if you don't explicitly set '--with-term-lib="ncursesw ncurses"' (line 79 in the 5.0.4 ebuld). Without it the build system picks up the right library and adds the necessary flags. So the solution is to either delete this line or add a patch similar to the one I attached.
Created attachment 366058 [details, diff] patch to support tinfo with explicit USE flag
(In reply to Marcus Spading from comment #6) > (In reply to Tim Harder from comment #5) > > A patch against the build system that will be accepted upstream. > > Actually I'm not sure this true. It builds fine if you don't explicitly set > '--with-term-lib="ncursesw ncurses"' (line 79 in the 5.0.4 ebuld). Without > it the build system picks up the right library and adds the necessary flags. > > So the solution is to either delete this line or add a patch similar to the > one I attached. Agreed. The ebuild is failing to pass the correct value for --with-term-lib in all situations. IMHO its better to let the build system pick up the proper values unless there's a use case that requires explicitly setting them.
Fixed in 5.0.5 by dropping the explicit setting.