nano 3.2 always compiles without nls
I'm running macOS 10.14 and zsh.
I noticed that nano 2.0 is installed by default and is missing some features. So, I tried to compile and install the latest version (3.2).
This work fine, except for 2 things:
- it always compiles without nls .
- it always compiles without utf-8 support.
nano --version
GNU nano, version 3.2
(C) 1999-2011, 2013-2018 Free Software Foundation, Inc.
(C) 2014-2018 the contributors to nano
Email: nano@nano-editor.org Web: https://nano-editor.org/
Compiled options: --disable-libmagic --disable-nls --disable-utf8
During the configure it did gave a warning about utf-8 so it does make sense that is disables utf-8 support.
configure: WARNING:
*** Insufficient UTF-8 support was detected in your curses and/or C
*** libraries. If you want UTF-8 support, please verify that your slang
*** was built with UTF-8 support or your curses was built with wide
*** character support, and that your C library was built with wide
*** character support.
What is the proper way to fix this? I would really like the nls support to work.
zsh nano macos-mojave
asked Dec 31 '18 at 13:41
WouleiWoulei
11
add a comment |
I'm running macOS 10.14 and zsh.
I noticed that nano 2.0 is installed by default and is missing some features. So, I tried to compile and install the latest version (3.2).
This work fine, except for 2 things:
- it always compiles without nls .
- it always compiles without utf-8 support.
nano --version
GNU nano, version 3.2
(C) 1999-2011, 2013-2018 Free Software Foundation, Inc.
(C) 2014-2018 the contributors to nano
Email: nano@nano-editor.org Web: https://nano-editor.org/
Compiled options: --disable-libmagic --disable-nls --disable-utf8
During the configure it did gave a warning about utf-8 so it does make sense that is disables utf-8 support.
configure: WARNING:
*** Insufficient UTF-8 support was detected in your curses and/or C
*** libraries. If you want UTF-8 support, please verify that your slang
*** was built with UTF-8 support or your curses was built with wide
*** character support, and that your C library was built with wide
*** character support.
What is the proper way to fix this? I would really like the nls support to work.
zsh nano macos-mojave
asked Dec 31 '18 at 13:41
WouleiWoulei
11
add a comment |
I'm running macOS 10.14 and zsh.
I noticed that nano 2.0 is installed by default and is missing some features. So, I tried to compile and install the latest version (3.2).
This work fine, except for 2 things:
- it always compiles without nls .
- it always compiles without utf-8 support.
nano --version
GNU nano, version 3.2
(C) 1999-2011, 2013-2018 Free Software Foundation, Inc.
(C) 2014-2018 the contributors to nano
Email: nano@nano-editor.org Web: https://nano-editor.org/
Compiled options: --disable-libmagic --disable-nls --disable-utf8
During the configure it did gave a warning about utf-8 so it does make sense that is disables utf-8 support.
configure: WARNING:
*** Insufficient UTF-8 support was detected in your curses and/or C
*** libraries. If you want UTF-8 support, please verify that your slang
*** was built with UTF-8 support or your curses was built with wide
*** character support, and that your C library was built with wide
*** character support.
What is the proper way to fix this? I would really like the nls support to work.
zsh nano macos-mojave
asked Dec 31 '18 at 13:41
WouleiWoulei
11
I'm running macOS 10.14 and zsh.
I noticed that nano 2.0 is installed by default and is missing some features. So, I tried to compile and install the latest version (3.2).
This work fine, except for 2 things:
- it always compiles without nls .
- it always compiles without utf-8 support.
nano --version
GNU nano, version 3.2
(C) 1999-2011, 2013-2018 Free Software Foundation, Inc.
(C) 2014-2018 the contributors to nano
Email: nano@nano-editor.org Web: https://nano-editor.org/
Compiled options: --disable-libmagic --disable-nls --disable-utf8
During the configure it did gave a warning about utf-8 so it does make sense that is disables utf-8 support.
configure: WARNING:
*** Insufficient UTF-8 support was detected in your curses and/or C
*** libraries. If you want UTF-8 support, please verify that your slang
*** was built with UTF-8 support or your curses was built with wide
*** character support, and that your C library was built with wide
*** character support.
What is the proper way to fix this? I would really like the nls support to work.
zsh nano macos-mojave
zsh nano macos-mojave
asked Dec 31 '18 at 13:41
WouleiWoulei
11
asked Dec 31 '18 at 13:41
WouleiWoulei
11
asked Dec 31 '18 at 13:41
WouleiWoulei
11
asked Dec 31 '18 at 13:41
WouleiWoulei
11
asked Dec 31 '18 at 13:41
WouleiWoulei
11
11
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
I've had the same problem and this Japanese article helped me.
Although I couldn't understand anything I at least was able to follow the steps needed. Basically, you are missing a library called ncurses. So, before compiling nano you should install it:
wget http://ftp.gnu.org/gnu/ncurses/ncurses-6.0.tar.gz
tar -xzvf ncurses-6.0.tar.gz
cd ./ncurses-6.0
./configure --with-shared --enable-widec
make
make install
and afterwards you configure and install nano as before:
cd ../nano-3.2
./configure --enable-all --enable-utf8
make
make install
answered Jan 9 at 15:57
Nikita KaramovNikita Karamov
114
Thnx for the reply. I'll try tomorrow and see if it works.
– Woulei
Jan 11 at 21:56
Just tried, didn't seem to work.
– Woulei
Jan 14 at 13:00
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1389260%2fnano-3-2-always-compiles-without-nls%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
I've had the same problem and this Japanese article helped me.
Although I couldn't understand anything I at least was able to follow the steps needed. Basically, you are missing a library called ncurses. So, before compiling nano you should install it:
wget http://ftp.gnu.org/gnu/ncurses/ncurses-6.0.tar.gz
tar -xzvf ncurses-6.0.tar.gz
cd ./ncurses-6.0
./configure --with-shared --enable-widec
make
make install
and afterwards you configure and install nano as before:
cd ../nano-3.2
./configure --enable-all --enable-utf8
make
make install
answered Jan 9 at 15:57
Nikita KaramovNikita Karamov
114
Thnx for the reply. I'll try tomorrow and see if it works.
– Woulei
Jan 11 at 21:56
Just tried, didn't seem to work.
– Woulei
Jan 14 at 13:00
add a comment |
I've had the same problem and this Japanese article helped me.
Although I couldn't understand anything I at least was able to follow the steps needed. Basically, you are missing a library called ncurses. So, before compiling nano you should install it:
wget http://ftp.gnu.org/gnu/ncurses/ncurses-6.0.tar.gz
tar -xzvf ncurses-6.0.tar.gz
cd ./ncurses-6.0
./configure --with-shared --enable-widec
make
make install
and afterwards you configure and install nano as before:
cd ../nano-3.2
./configure --enable-all --enable-utf8
make
make install
answered Jan 9 at 15:57
Nikita KaramovNikita Karamov
114
Thnx for the reply. I'll try tomorrow and see if it works.
– Woulei
Jan 11 at 21:56
Just tried, didn't seem to work.
– Woulei
Jan 14 at 13:00
add a comment |
I've had the same problem and this Japanese article helped me.
Although I couldn't understand anything I at least was able to follow the steps needed. Basically, you are missing a library called ncurses. So, before compiling nano you should install it:
wget http://ftp.gnu.org/gnu/ncurses/ncurses-6.0.tar.gz
tar -xzvf ncurses-6.0.tar.gz
cd ./ncurses-6.0
./configure --with-shared --enable-widec
make
make install
and afterwards you configure and install nano as before:
cd ../nano-3.2
./configure --enable-all --enable-utf8
make
make install
answered Jan 9 at 15:57
Nikita KaramovNikita Karamov
114
I've had the same problem and this Japanese article helped me.
Although I couldn't understand anything I at least was able to follow the steps needed. Basically, you are missing a library called ncurses. So, before compiling nano you should install it:
wget http://ftp.gnu.org/gnu/ncurses/ncurses-6.0.tar.gz
tar -xzvf ncurses-6.0.tar.gz
cd ./ncurses-6.0
./configure --with-shared --enable-widec
make
make install
and afterwards you configure and install nano as before:
cd ../nano-3.2
./configure --enable-all --enable-utf8
make
make install
answered Jan 9 at 15:57
Nikita KaramovNikita Karamov
114
answered Jan 9 at 15:57
Nikita KaramovNikita Karamov
114
answered Jan 9 at 15:57
Nikita KaramovNikita Karamov
114
answered Jan 9 at 15:57
Nikita KaramovNikita Karamov
114
114
Thnx for the reply. I'll try tomorrow and see if it works.
– Woulei
Jan 11 at 21:56
Just tried, didn't seem to work.
– Woulei
Jan 14 at 13:00
add a comment |
Thnx for the reply. I'll try tomorrow and see if it works.
– Woulei
Jan 11 at 21:56
Just tried, didn't seem to work.
– Woulei
Jan 14 at 13:00
Thnx for the reply. I'll try tomorrow and see if it works.
– Woulei
Jan 11 at 21:56
Thnx for the reply. I'll try tomorrow and see if it works.
– Woulei
Jan 11 at 21:56
Just tried, didn't seem to work.
– Woulei
Jan 14 at 13:00
Just tried, didn't seem to work.
– Woulei
Jan 14 at 13:00
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1389260%2fnano-3-2-always-compiles-without-nls%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
