From: Guillermo <gdiazhartusch@gmail.com>
To: supervision@list.skarnet.org
Subject: Re: has anyone gotten nosh to build on Void Linux?
Date: Sat, 30 Jun 2018 15:34:53 -0300 [thread overview]
Message-ID: <CADQ2Nw9io3eZpSMjNMiykdxH8YMxOoUMTuSQvLYA959b=fZKiA@mail.gmail.com> (raw)
In-Reply-To: <87fu14irya.fsf@prgmr.com>
Hi,
2018-06-30 5:44 GMT-03:00 Chris Brannon:
>
> When I run package/compile from the root of the unpacked source tree, I
> get:
> redo: ERROR: all: Cannot find .do file to use.
>
> -- Chris
The nosh-1.37 source package? If you unpacked the source tarball in a
directory named 'nosh-1.37', you have a 'source' and a 'package'
subdirectory, you ran package/compile, but it *did not* create a
subdirectory named 'build', then, as people have said, most likely you
don't have an implementation of pax(1) installed. It is a
POSIX-specified utility, but on most [GNU/]Linux distributions you
have to manually install some package to get it. I believe on Void
that would be the 'pax' package.
Not related to redo's error message, but because distributions differ
in the way they package ncurses and util-linux, you might want to
check if:
* The libtinfo, libncursesw and libuuid libraries are present in
Void's 'standard' libraries directory.
* There is a curses.h file in both Void's 'standard' headers directory
and in a subdirectory named 'ncursesw' (for the narrow character and
wide character versions of the library, respectively). Normally, that
would be /usr/include/curses.h and /usr/include/ncursesw/curses.h.
* The wall(1) program is available in Void's 'standard' executables directories.
Because that's what nosh's build system and executables are going to
expect, as far as I know. If not, patches will probably be needed. It
would also help to know what the ID and VERSION_ID fields of Void's
/etc/os-release look like. I believe the former is 'void', and the
latter is absent, correct?
It would be interesting to see what is needed for different OSes to
make nosh build. If you do try again, please report :)
Hope that helps,
G.
next prev parent reply other threads:[~2018-06-30 18:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-30 8:44 Chris Brannon
2018-06-30 9:40 ` multiplexd
2018-06-30 10:18 ` Jonathan de Boyne Pollard
2018-06-30 18:34 ` Guillermo [this message]
2018-07-01 0:27 ` Chris Brannon
2018-07-01 21:18 ` Guillermo
2018-07-01 10:37 ` Jonathan de Boyne Pollard
2018-07-01 11:38 ` Jonathan de Boyne Pollard
2018-07-01 21:19 ` Guillermo
2018-07-01 12:48 ` Jonathan de Boyne Pollard
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CADQ2Nw9io3eZpSMjNMiykdxH8YMxOoUMTuSQvLYA959b=fZKiA@mail.gmail.com' \
--to=gdiazhartusch@gmail.com \
--cc=supervision@list.skarnet.org \
/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 NNTP newsgroup(s).