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`

[Tim Visher <tim.visher@gmail.com>]

Thanks for your response, Noam.

On Tue, Aug 14, 2018 at 9:05 PM Noam Postavsky <npostavs@gmail.com> wrote:

> 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


I've pointed the maintainers of spksrc to that page to see if they have any
insight related to their framework specifically.


> > 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).
>

"Does your libncurses only operate on the target?" I'm unsure what to even
Google for to answer this question intelligently. Can you give me some
pointers?