unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Tim Visher <tim.visher@gmail.com>
To: Noam Postavsky <npostavs@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: Sat, 18 Aug 2018 11:15:36 -0400	[thread overview]
Message-ID: <CAHa53uy4dpu0P7+MZK3o9Nx=6-4inReYS9Wv3X1tyBWx6Aqvpg@mail.gmail.com> (raw)
In-Reply-To: <CAM-tV-9aAf4=7G4q_ZGTkzEMKEe33nkyCB0mEMMcqnSH6r4OoQ@mail.gmail.com>

On Wed, Aug 15, 2018 at 9:53 AM Noam Postavsky <npostavs@gmail.com> wrote:

> On 15 August 2018 at 08:46, Tim Visher <tim.visher@gmail.com> wrote:
>
> > "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?
>
> Sorry, that didn't come out clearly. What I mean is, how far apart are
> your build and target machines (with respect to CPU and OS)? Can you
> execute a binary built for the target on your build machine (that's
> what the Emacs build system does)?
>
> If you can, then it might just be a matter of putting the spksrc
> libncurses directory in LD_LIBRARY_PATH (LDFLAGS only tells the linker
> where to look, it doesn't affect the runtime).
>

Ah I get it then. :)

I'm not sure whether I can or not but I can certainly try and will do so
soon. Thanks so much for your input!


  reply	other threads:[~2018-08-18 15:15 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
2018-08-15 12:46   ` Tim Visher
2018-08-15 13:53     ` Noam Postavsky
2018-08-18 15:15       ` Tim Visher [this message]
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='CAHa53uy4dpu0P7+MZK3o9Nx=6-4inReYS9Wv3X1tyBWx6Aqvpg@mail.gmail.com' \
    --to=tim.visher@gmail.com \
    --cc=help-gnu-emacs@gnu.org \
    --cc=npostavs@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).