9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Jag Talon" <jag@jagtalon.com>
To: 9fans@9fans.net
Subject: Re: [9fans] Trouble compiling "Hello, world"
Date: Mon, 01 Aug 2022 19:44:50 -0400	[thread overview]
Message-ID: <5c567a3f-c27b-4ad3-89ae-62265a850f1c@www.fastmail.com> (raw)
In-Reply-To: <CAJSxfmLDEVCgHvkXA3bgbVftqkx+yNR+oYPAHFDZ_FjeqwamdQ@mail.gmail.com>

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

Thank you Skip and Jacob I'm running a Plan 9 instance through the SDF Bootcamp so it's a shared system that I didn't install myself. I'll make sure to reach out to the admins because trying to run `mk install` in /sys/src/libc is giving me permission errors. 

On Mon, Aug 1, 2022, at 6:53 PM, Skip Tavakkolian wrote:
> in /sys/src
> 
> On Mon, Aug 1, 2022 at 3:51 PM Skip Tavakkolian <skip.tavakkolian@gmail.com> wrote:
>> generally it's a good idea to rebuild and install changes for all architectures in your network.
>> something like:
>> for (i in (386 arm amd64 riscv mips)) {
>>  objtype=$i mk install
>> }
>> 
>> 
>> On Mon, Aug 1, 2022 at 2:50 PM Jacob Moody <moody@posixcafe.org> wrote:
>>> On 8/1/22 15:18, Jag Talon wrote:
>>> > Ah thanks for the tip. I ran `echo $objtype` and it says amd64. I believe 6c is the compiler that I need but it seems to say another error: `??none??: cannot open file: /amd64/lib/libc.a`
>>> 
>>> It's telling you exactly what is wrong, you are missing an amd64 libc archive.
>>> I am not sure how you wound up with running an amd64 kernel with an incomplete
>>> amd64 install. For building libc again:
>>> 
>>> cd /sys/src/libc/ && mk install && mk clean
>>> 
>>> However, you may be missing more then just libc, in that case may just be best to rebuild
>>> the whole system as a second resort.
>>> 
>>> cd /sys/src/ && mk install && mk clean
>>> 
>>> How did you install this system? Did you bootstrap yourself
>>> up from 386?
>>> 
>>> --
>>> moody
> *9fans <https://9fans.topicbox.com/latest>* / 9fans / see discussions <https://9fans.topicbox.com/groups/9fans> + participants <https://9fans.topicbox.com/groups/9fans/members> + delivery options <https://9fans.topicbox.com/groups/9fans/subscription> Permalink <https://9fans.topicbox.com/groups/9fans/Te178b97d94173ff8-Me22000ce2ef1c56d4f614ba0>

------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/Te178b97d94173ff8-Mac8d6220dad4f005c1d17561
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription

[-- Attachment #2: Type: text/html, Size: 4185 bytes --]

  reply	other threads:[~2022-08-01 23:45 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-01 20:41 Jag Talon
2022-08-01 21:02 ` Jacob Moody
2022-08-01 21:18   ` Jag Talon
2022-08-01 21:48     ` Jacob Moody
2022-08-01 22:51       ` Skip Tavakkolian
2022-08-01 22:53         ` Skip Tavakkolian
2022-08-01 23:44           ` Jag Talon [this message]
2022-08-02  1:11             ` LdBeth
2022-08-02  1:32             ` Thaddeus Woskowiak
2022-08-02  2:16               ` Jag Talon
2022-08-02  3:38                 ` Lucio De Re
2022-08-02  3:44                   ` Kurt H Maier via 9fans
2022-08-02  3:56                     ` Lucio De Re
2022-08-02  5:45                       ` Clout Tolstoy
2022-08-02  9:05                         ` Lucio De Re
2022-08-02  5:40                   ` sirjofri

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=5c567a3f-c27b-4ad3-89ae-62265a850f1c@www.fastmail.com \
    --to=jag@jagtalon.com \
    --cc=9fans@9fans.net \
    /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).