Summary: | sys-process/htop-1.0.3 - ld: htop-CRT.o: undefined reference to symbol 'cbreak' | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | PM <mitaspiotr> |
Component: | [OLD] Core system | Assignee: | Christian Ruppert (idl0r) <idl0r> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | even.more.spam.for.me, g.livid, gentoo-bugs, kavafree, kentnl |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 457530 | ||
Attachments: |
Fix configure.ac to use pkg-config
Fix configure.ac to use pkg-config v2 Fix configure.ac to use pkg-config v3 |
Description
PM
2014-05-03 11:36:26 UTC
Created attachment 382424 [details, diff]
Fix configure.ac to use pkg-config
Here is a quick-and-dirty patch until upstream does something about it. I should probably note that I am not autoconf expert by any means, so any suggestions are welcome.
Created attachment 382430 [details]
Fix configure.ac to use pkg-config v2
Sorry, this is corrected version. I forgot to remove function argument.
Created attachment 382432 [details, diff]
Fix configure.ac to use pkg-config v3
Gosh, can't do anything right today. Now correctly reported as patch. Sorry about all the fuss.
(In reply to Livid from comment #3) > Created attachment 382432 [details, diff] [details, diff] > Fix configure.ac to use pkg-config v3 > > Gosh, can't do anything right today. Now correctly reported as patch. Sorry > about all the fuss. Hi Livid, I just added the old Patch[1] back. Can you please verify whether it works correctly? 1. http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/sys-process/htop/files/htop-1.0.2-tinfo.patch?hideattic=0&view=markup Yes, this patch works on my system where htop failed to build previously. -ltinfo/tinfow is correctly appended to libtool arguments. -lncurses[w] is appended twice however (first from pkg_config, second from ac_check_lib), not that it breaks anything really. Anyway, I think we may safely close this as resolved fixed. Alright. Thanks! |