luke.leighton at gmail.com
Fri Sep 10 23:00:55 BST 2021
On Fri, Sep 10, 2021 at 10:57 PM Andrey Miroshnikov
<andrey at technepisteme.xyz> wrote:
> On 10/09/2021 22:06, lkcl wrote:
> > not at all, it's the name i gave to the gitolite3 key in the (administrative-only-accessible) gitolite3 repo.
> Apologies, just realised it's my name and first letter of the surname.
> My last job it was usually [first letter of surname|name] so I didn't
> expect it XD
> >> Shall I make the change to the third last line to cd one directory up:
> >> cd /home/$SUDO_USER/src/
> > yes please.
> > Looks like I don't have permission to push to dev-env-setup:
> "FATAL: W any dev-env-setup andreym DENIED by fallthru
> (or you mis-spelled the reponame)
> fatal: Could not read from remote repository.
> Please make sure you have the correct access rights
> and the repository exists."
> I added that repo using:
> git clone gitolite3 at git.libre-soc.org:dev-env-setup.git
> And checked the .git/config, same settings as the ones for the website repo.
> Also checked over scripts to see if there was a similar issue.
> "iverilog-install" uses "." instead of "iverilog" directory, so changing
> ownership works. "nextpnr-ecp5-install" and "verilator-install" are
> similar to "iverilog-install".
> Given that those scripts use the current dir "." instead, I figured it
> might be better for consistency to use "." in the "hdl-tools-yosys" as well.
> Also scripts "nextpnr-ecp5-install", "verilator-install",
> "iverilog-install", and "hdl-tools-yosys" specify "-j$(nproc)" in their
> make which might not be great (as you've mentioned about your laptop).
> Since you've said that scripts are automated in the dev email, I'll look
> at the environmental var conventions for this later.
> > btw i am currently (slowly) going through coriolis2-chroot, after converting it from type "plain" (which worked perfectly) to type "directory" env vars are not properly handled.
> Had a quick look at that script, what a nightmare :')
yep, i know. sigh
> I only know "chroot" in the context of "chrooting" into another instance
> of Linux (for example from a livecd usb iso to a newly installed system
> as happens in Arch Linux base install).
> From the context of the script I guess you're creating a completely
> "independent" Linux system for the coriolis program, almost like a
> FreeBSD Jail (or a virtual machine, or some other compartmentalising
> metaphor). Not sure why coriolis needs it, but I should probably RTFM
> for that.
> Also I don't know what you mean by "plain" and "directory" types. If
> there's a man entry or blog entry on this to save you time explaining,
> do point me there.
> For now I probably have enough on my plate anyway so I'll wait for you
> to work on it, but looking at the GDSII files would be pretty damn cool.
yehyeh it is :)
More information about the Libre-soc-dev