The ncurses link script in Fedora for a long time now seems not to work with ld.gold. $ cat /usr/lib64/libncursesw.so INPUT(libncursesw.so.5 -ltinfo) From building less with ld.gold: configure:3697: checking for initscr in -lncursesw configure:3722: gcc -o conftest -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic conftest.c -lncursesw >&5 /usr/bin/ld: error: cannot open : No such file or directory /usr/bin/ld: /tmp/ccVkMvCS.o: in function main:conftest.c:20: error: undefined reference to 'initscr' collect2: ld returned 1 exit status configure:3722: $? = 1 configure: failed program was: | /* confdefs.h */ | #define PACKAGE_NAME "less" | #define PACKAGE_TARNAME "less" | #define PACKAGE_VERSION "1" | #define PACKAGE_STRING "less 1" | #define PACKAGE_BUGREPORT "" | #define PACKAGE_URL "" | /* end confdefs.h. */ | | /* Override any GCC internal prototype to avoid an error. | Use char because int might match the return type of a GCC | builtin and then its argument prototype would still apply. */ | #ifdef __cplusplus | extern "C" | #endif | char initscr (); | int | main () | { | return initscr (); | ; | return 0; | } +++ This bug was initially created as a clone of Bug #635581 +++ --- Additional comment from petersen on 2010-09-21 13:21:28 EST --- Ah I reproduced the ncurses problem with binutils-2.20.51.0.11-1.fc15. Interesting that binutils-2.20.51.0.7-5.fc14 is ok. That is known issue with the libncurses*.so link script "hacks" in Fedora. I already have a workaround patch for ghc-terminfo (in package review) which could be applied to ghc's internal copy of terminfo too. --- Additional comment from petersen on 2010-09-21 17:20:39 EST --- Note that the ncurses issue is not ghc specific: I tested less and w3m for example and they also fail to configure ncurses. less builds with ncurses, but w3m fails to link. I guess ld.gold is not compatible with current ld.scripts.
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle. Changing version to '19'. (As we did not run this process for some time, it could affect also pre-Fedora 19 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.