9front - general discussion about 9front
 help / color / mirror / Atom feed
From: hiro <23hiro@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] Staying up-to-date
Date: Wed, 12 Jun 2024 14:51:41 +0200	[thread overview]
Message-ID: <CAFSF3XNArhOV01zGJE+nEiXZs04A_nO=7Mdzy7L04OxMq86oPw@mail.gmail.com> (raw)
In-Reply-To: <1890322.tdWV9SEqCh@cixi>

the sequence of commands is not expected to always work, you are right
to execute the commands manually instead. so far nobody found a
generic solution to this problem.

On Tue, Jun 11, 2024 at 4:57 PM Thomas Nemeth <tnemeth@free.fr> wrote:
>
>     Hi.
>
>     I've read the FQA and some other documentation a lot and I'm amiss
>     about why my system upgrade script does not work the way I intend
>     it to work. I certainly don't know enough about the specifics and
>     peculiarities of rc.
>
>     I made a script, named sysupgrade, that does what's in dash1,
>     section 5.2.2: "Building from source".
>
> ------8<------8<------8<------8<------8<------8<------8<------
> #!/bin/rc
>
> sysupdate
>
> # create any missing directories needed for the build
> cd /
> . /sys/lib/rootstub
>
> # build everything
> cd /sys/src
> mk install
> mk clean
>
> # build manpage indices
> cd /sys/man
> mk
> ------8<------8<------8<------8<------8<------8<------8<------
>
>     But, unfortunately it fails to execute everything so I usually
>     type them one by one... (well, today the compilation fails anyway).
>
>     Can someone explain or tell me what I did wrong ?
>
> Thomas.
>
>

  parent reply	other threads:[~2024-06-12 12:55 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-11 14:57 Thomas Nemeth
2024-06-11 15:08 ` phil9
2024-06-11 15:15   ` Thomas Nemeth
2024-06-12 11:57     ` cosarara
2024-06-12 16:57       ` Thomas Nemeth
2024-06-13  0:46         ` sl
2024-06-13  1:05           ` sl
2024-06-13  6:31           ` Thomas Nemeth
2024-06-13 17:16             ` hiro
2024-06-12 12:21     ` ori
2024-06-12  2:30 ` Thaddeus Woskowiak
2024-06-12 17:10   ` Thomas Nemeth
2024-06-12 12:51 ` hiro [this message]
2024-06-12 13:04   ` ori
2024-06-12 17:10     ` Thomas Nemeth
2024-06-12 19:34       ` Ori Bernstein
2024-06-12 21:55         ` Stanley Lieber
2024-06-12 17:03   ` Thomas Nemeth
2024-06-12 17:56     ` hiro
2024-06-12 18:11       ` Thomas Nemeth
2024-06-12 19:35         ` Ori Bernstein
2024-06-13  6:38           ` Thomas Nemeth
2024-06-14 20:11             ` hiro
2024-06-16 10:01               ` Thomas Nemeth
2024-06-16 13:03                 ` Thaddeus Woskowiak
2024-06-16 14:27                   ` Thomas Nemeth
2024-06-16 18:02                     ` ori
2024-06-17 11:04                     ` hiro
2024-06-16 18:00                 ` ori
2024-06-16 20:20                   ` [9front] Out-of-date and obsolete documentation Lyndon Nerenberg (VE7TFX/VE6BBM)

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='CAFSF3XNArhOV01zGJE+nEiXZs04A_nO=7Mdzy7L04OxMq86oPw@mail.gmail.com' \
    --to=23hiro@gmail.com \
    --cc=9front@9front.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).