> it's a shared system that I didn't install myself.
How are you connecting and interacting?
>
> 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
>
>
> 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 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 / 9fans / see discussions + participants + delivery options Permalink
------------------------------------------
9fans: 9fans