supervision - discussion about system services, daemon supervision, init, runlevel management, and tools such as s6 and runit
 help / color / mirror / Atom feed
From: Jonathan de Boyne Pollard <J.deBoynePollard-newsgroups@NTLWorld.COM>
To: Supervision <supervision@list.skarnet.org>
Subject: Re: has anyone gotten nosh to build on Void Linux?
Date: Sat, 30 Jun 2018 11:18:24 +0100	[thread overview]
Message-ID: <d075a764-560c-3e28-0a8f-0c5b1af48f49@NTLWorld.COM> (raw)
In-Reply-To: <87fu14irya.fsf@prgmr.com>

[-- Attachment #1: Type: text/plain, Size: 2056 bytes --]

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.
>
You need to make your operating system POSIX-conformant.  I make fairly 
liberal use of some standard utilities in the build process including 
|pax 
<http://pubs.opengroup.org/onlinepubs/9699919799/utilities/pax.html>|, 
|uname 
<http://pubs.opengroup.org/onlinepubs/9699919799/utilities/uname.html>|, 
|mv 
<http://pubs.opengroup.org/onlinepubs/9699919799/utilities/mv.html>|, 
and |expr 
<http://pubs.opengroup.org/onlinepubs/9699919799/utilities/expr.html>| 
amongst others.  A POSIX-conformant operating system is a fairly minimal 
expectation for a build environment.  (It is not as though the build 
process is requiring, for example, the Bourne Again shell and its 
non-POSIX extensions for building from source on host operating systems; 
as some softwares do.) The source package page 
<jdebp.info./Softwares/nosh/source-package.html> notes the 
*non*-standard tools that are needed.

This information is pre-encoded in the |package/debian/control| file 
that I supply for Debian Linux, to be automatically checked by 
|dpkg-buildpackage|.  (There's no equivalent list that I supply for the 
BSDs; but it is also the case that the BSDs provide nearly all of this 
stuff, including the non-POSIX |install| tool, out of the box, in 
base.)  If you are building on a different Linux operating system, that 
is a good hint, with two caveats: Your Linux operating system won't 
necessarily package things up the same way as Debian or have the same 
package dependency tree, and Debian mandates a group of tools as 
standard without their needing to be mentioned in a 
|package/debian/control| file 
<https://debian.org/doc/debian-policy/#package-relationships>. 
Furthermore: Thomas Caravia has already worked out the build 
requirements for Arch Linux in terms of pre-requisite Arch packages, and 
the doco for Archnosh is a further source of clues for building on other 
Linux operating systems.


  parent reply	other threads:[~2018-06-30 10:18 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 [this message]
2018-06-30 18:34 ` Guillermo
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=d075a764-560c-3e28-0a8f-0c5b1af48f49@NTLWorld.COM \
    --to=j.deboynepollard-newsgroups@ntlworld.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).