From: Jacob Moody <moody@posixcafe.org>
To: 9front@9front.org
Subject: Re: [9front] Error compiling rio?
Date: Tue, 16 Apr 2024 11:38:06 -0500 [thread overview]
Message-ID: <ba541e86-6380-44de-87a0-b5500f1bee2c@posixcafe.org> (raw)
In-Reply-To: <A6DC9558321AD036B073DD8A764998C4@wopr.sciops.net>
On 4/16/24 11:33, qwx@sciops.net wrote:
> On Tue Apr 16 15:24:27 +0200 2024, moody@posixcafe.org wrote:
>> On 4/16/24 06:27, Jacobo Da Riva Muñoz wrote:
>>> Hi,
>>>
>>> I've got this error updating the system this morning. I've wollowed the upgrading process ass seen in the fqa 5.2.2 point.
>>>
>>> mk rio
>>> 6c -FTVw rio.c
>>> 6c -FTVw data.c
>>> mk: no recipe to make 'menuhit.6' in directory /sys/src/cmd/rio
>>> dat.h:303 data.c:10 6c: directory entry not found: 'col.h': col.h
>>> dat.h:303 rio.c:11 6c: directory entry not found: 'col.h': col.h
>>> mk: for(i in 1a ... : exit status=rc 2205: mk 4108: error
>>> mk: mk $MKFLAGS yacc.install ... : exit status=mk 2122: error
>>> mk: date for (i ... : exit status=rc 824: mk 2105: error
>>>
>>> Best regards
>>
>> This looks like you are missing source files from the directory.
>>
>> Check your current machine diff against usptream:
>> bind -ac /dist/plan9frnont / && git/diff -s /
>> and ensure that there are only the changes you expect.
>>
>> Thanks,
>> moody
>
> There is no col.h or menuhit.c/etc in 9front's rio. You have likely
> patched it at some point with Sigrid's or someone else's theming
> changes. Use git/revert and reapply the patch if it's still current
> or use unmodified rio.
>
> Cheers,
> qwx
Oh nice catch, my bad. The patches are current as far as I know.
Thanks,
moody
next prev parent reply other threads:[~2024-04-16 16:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-16 11:27 Jacobo Da Riva Muñoz
2024-04-16 13:19 ` Jacob Moody
2024-04-16 16:33 ` qwx
2024-04-16 16:38 ` Jacob Moody [this message]
2024-04-30 4:54 ` Jacobo Da Riva Muñoz
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=ba541e86-6380-44de-87a0-b5500f1bee2c@posixcafe.org \
--to=moody@posixcafe.org \
--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).