From: Chris Brannon <chris@the-brannons.com>
To: supervision@list.skarnet.org
Subject: Re: has anyone gotten nosh to build on Void Linux?
Date: Sat, 30 Jun 2018 17:27:38 -0700 [thread overview]
Message-ID: <878t6viyv9.fsf@prgmr.com> (raw)
In-Reply-To: <CADQ2Nw9io3eZpSMjNMiykdxH8YMxOoUMTuSQvLYA959b=fZKiA@mail.gmail.com> (Guillermo's message of "Sat, 30 Jun 2018 15:34:53 -0300")
Guillermo <gdiazhartusch@gmail.com> writes:
> Hi,
>
> 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.
Sorry, I didn't have time to reply, but I made a good deal of progress
earlier today, after writing to the list.
Yes that is correct; pax was one of the things I was missing. I was
also missing libuuid-devel. I needed to change the header paths for
ncurses headers in the source. I also needed to fine libtinfo, because
Void doesn't have it. Void could probably have libtinfo provided by
their curses package with a fairly straightforward change.
I figured out how to get libtinfo from ncurses by looking at the Arch
PKGBUILD for ncurses.
> 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?
That's right.
> It would be interesting to see what is needed for different OSes to
> make nosh build. If you do try again, please report :)
Indeed. Ideally, I'll eventually end up with a package script for
Void -- known as a "template" in Void parlance. I'll keep working on
that until it's written.
> Hope that helps,
Thank you.
-- Chris
next prev parent reply other threads:[~2018-07-01 0:27 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
2018-07-01 0:27 ` Chris Brannon [this message]
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=878t6viyv9.fsf@prgmr.com \
--to=chris@the-brannons.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).