From: Noam Postavsky <npostavs@gmail.com>
To: Tim Visher <tim.visher@gmail.com>
Cc: emacs <help-gnu-emacs@gnu.org>
Subject: Re: Building emacs using the `spksrc` toolchain results in `./temacs: error while loading shared libraries: libncurses.so.6: cannot open shared object file: No such file or directory`
Date: Tue, 14 Aug 2018 21:05:16 -0400 [thread overview]
Message-ID: <CAM-tV-_cX5YwwL76PbSOK=pk5iRH7sAjzpsFapBV4G+mwQBybA@mail.gmail.com> (raw)
In-Reply-To: <CAHa53uwH_Y=KHjO67ae7+J0Vkoo7ihALr6=ydraxjjbP1TDx8g@mail.gmail.com>
On 14 August 2018 at 20:44, Tim Visher <tim.visher@gmail.com> wrote:
> I'm attempting to provide an emacs package for Synology NASes using the
> `spksrc` toolchain (PR: https://github.com/SynoCommunity/spksrc/pull/3352).
This is described as a "Cross compilation framework", I'm not sure if
this will work (see Bug#9192)
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=9192
> The build fails with the following error message:
>
> ```
> ./temacs --batch --load loadup bootstrap
> ./temacs: error while loading shared libraries: libncurses.so.6: cannot
> open shared object file: No such file or directory
> Notably LDFLAGS appears to contain a directory which contains
> libncurses.so.6
>
> ```
> vagrant@debian-8:~/spksrc/spk/emacs/work-apollolake-6.1/emacs-26.1$ ls -l
> /home/vagrant/spksrc/spk/emacs/work-apollolake-6.1/install//var/packages/emacs/target/lib/libncurses.so.6.1
Does your libncurses only operate on the target? Because the Emacs
build system needs to run Emacs on your build machine (hence the
difficulty with cross-compilation).
next prev parent reply other threads:[~2018-08-15 1:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-15 0:44 Building emacs using the `spksrc` toolchain results in `./temacs: error while loading shared libraries: libncurses.so.6: cannot open shared object file: No such file or directory` Tim Visher
2018-08-15 1:05 ` Noam Postavsky [this message]
2018-08-15 12:46 ` Tim Visher
2018-08-15 13:53 ` Noam Postavsky
2018-08-18 15:15 ` Tim Visher
2018-08-21 12:09 ` Tim Visher
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAM-tV-_cX5YwwL76PbSOK=pk5iRH7sAjzpsFapBV4G+mwQBybA@mail.gmail.com' \
--to=npostavs@gmail.com \
--cc=help-gnu-emacs@gnu.org \
--cc=tim.visher@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).