Tiny Core Linux
Tiny Core Extensions => TCE Bugs => Topic started by: TaoTePuh on August 21, 2010, 02:57:51 AM
-
Building ncmpcpp against the new ncurses, I get the following error message :
checking for ncurses5-config... /usr/local/bin/ncurses5-config
checking for initscr in -lncursesw... no
checking for initscr in -lncurses... no
configure: error: ncurses library is required
-
Did you install ncurses-dev.tcz ?
-
yes.
-
Will check it later today.
-
Another note: Starting mc fails with:
mc: symbol lookup error: /usr/local/lib/libncurses.so.5: undefined symbol: newscr
In addition, the extension fuse in the repo seems to be broken. Message on update :
Error occurred. fuse.tcz Not updated!
-
Yes there is a problem with the latest upgrade. I'm just making a new version. Sorry for the issue. Wait a bit for the new one.
-
Bug fix version sent for submission. It is tested with current application and also compiled applications against it, looks OK. Hope it will solve your compilation problem.
-
@bela: congrats to your 1500th post... always good to see when it's a problem solver :D
submission is hopefully soon available, since every extension with ncurses as dep seems to be broken atm (tested with apache2 too, same error) ;)
-
@bela: congrats to your 1500th post... always good to see when it's a problem solver :D
submission is hopefully soon available, since every extension with ncurses as dep seems to be broken atm (tested with apache2 too, same error) ;)
Thanks! For sure it will be available soon. It is interesting why apache need ncurses....
-
I am getting ready to upload the latest ncurses sent in, but I am not seeing those issues with mc and apache. None of my apps are having problems, some of them include bash, pidgin, xine-ui, zsnes, siag, joe, etc, and all depend on libncurses.so.5. Runtime seems fine here for my installation, though I have not tried to compile against the new ncurses.
Make sure you remove the old ncurses-lib, ncurses-utils, ncurses-lib-dev extensions or you will run into issues when the updated ncurses.tcz is installed.
Uploading the newly sent one now.
-
@Jason: I booted with base norestore, loaded apache2 from repo and tried apachectl -k start, there again symbol lookup error newscr for /usr/local/lib/libncurses.so.5. When I manually remove ncurses and use the /lib/libncurses.so.5 from base, apache works.
Maybe you're using an "older" version, which worked? ;-)
-
Here is my output, I ran a tce-update yesterday and have not updated to the newly uploaded ncurses yet - I just uploaded it now:
tc@box:~$ apachectl -k start
httpd: Could not reliably determine the server's fully qualified domain name, using 127.0.0.1 for ServerName
(13)Permission denied: make_sock: could not bind to address 0.0.0.0:80
no listening sockets available, shutting down
Unable to open logs
tc@box:~$
Of course, I don't have apache set up but there is no lib issues.
Also, booting "base norestore" and downloading and running apache also works as above after the new extension has been uploaded, but it also works with first loading the previous ncurses extension.
I am not sure what the explanation is, but try again now that the new ncurses has been uploaded.
-
I could replicate the error on my system and it was related to the upgrade. To be honest do not know the root cause of the issue but a new compilation on a clean system resulted a working extension, at least here it works fine.
Please let me know if there is still a problem or confirm that it's back to normal operation.
-
I'll do when the new ncurses is available in the repo.
-
The latest version is in the repo, uploaded about 30min ago.
-
Okay, after fetching the new ncurses* :
1.) mc works again
2.) compiling ncmpcpp against ncurses works too.
Good boys do good jobs. Thank you!
-
Thanks :)
-
ncursesw, ncurses compiled with widec option enabling UTF-8 is posted. Look for ncursesw.tcz, ncursesw-utils.tcz and ncursesw-dev.tcz in the repo. These can be installed alongside with their normal ncurses counterpart. ncurses-doc.tcz and ncurses-terminfo.tcz are common for both versions.
ncurses-common.tcz which is a set of mandatory components for both versions loaded automatically by the main extension.
ncurses-utils.tcz and ncursesw-utils.tcz installing applications with the same name but linked against different libs, do not mix them.
-
Cool!
I will try to build new ncmpcpp with the option "--enable-unicode".
-
I will get in around 8pm EST and upload it then.
-
I have rebuilt ncmpcpp with UTF-8 support (--enable-unicode) against the new ncursesw*, then tested :
Terminal/locale UTF-8 ISO-8859-15 C
--------------------------------------------
aterm 2) 3) 1)
LXTerminal OK 4) 1)
Terminal (Xfce) OK 3) 1)
1) non-ISO-8859-1 chars are not displayed correctly
search for special characters only with ".." and regex-mode
2) non-ISO-8859-1 chars are not displayed correctly
search for special characters works but they are not
displayed correctly
3) characters are displayed correctly
search for special characters only with ".." and regex-mode
4) characters are displayed correctly
search for special characters only with ".." and regex-mode
borders and lines are not displayed correctly
As expected, it works only in an UTF-8 environment really well.
-
Might be of potential interest if behaviour on a VT would be included in comparison.
-
Both lxterminal and Xfce4's terminal is using the same terminal engine, vte therefore their main behavior expected to be the same.
-
Might be of potential interest if behaviour on a VT would be included in comparison.
I have no experience with VT's. Please teach me.
-
The console font is even more limited than the bitmap one used by X and aterm, so not too good results would be expected. For special characters it's best to use a TTF-supporting terminal with a good truetype font.
-
Ok, if so, then I guess what i suggested is futile, disregard please.