I still haven't progressed on the "limits.h" issue. Not going to happen this side of xmas. There is https://github.com/swampdawg/go if you're desperate to get started to save time later. You need to be conversant with bash shell script. Basically, if you can't figure out what to do with the GOSUB variable then give up on it. I wrote the README and all the examples with a different purpose in mind. If the file starts with "f_" then it is code and it works and is tested. You'll not get an "xgcc" out of this. At best you'll get a test native gcc (start with go.gcc) which will attempt to install itself down /usr/local/GCC/* (which will fail) because at no point should you ever attempt to run any "go" stuff as root.So... do you have the build script? I'm in hell.
It's at this point I got stuck with the above docs. I have a lot of scripts which (a) I can't post because of f_tmp (b) takes too long to modify removing f_tmp, so I've decided to force the issue via an installer such that it'll create "/usr/local/sd/syschk/lib/" and just symlink the code to wherever the user cloned the above repo to, thus newbies won't have to be concerned about the GOSUB variable. The irony: originally there was an installer (for lots of f_* utility functions) - a story for another day.
Easiest way to get started, create folder "/usr/local/sd/syschk/lib" and make it owned by your user. Clone the repo somewhere then 'cd' to "/usr/local/sd/syschk/lib" and symlink to all the "f_*" files. Then copy "go.gcc" into a new folder, rename it "go", download gcc 14.2.0 sources and type "./go all". If you want it to install, create/chown "/usr/local/GCC/" as yourself. Repeat with CFG set properly for a full fat compiler. Again sheel script knowledge expected.
Statistics: Posted by swampdog — Wed Dec 18, 2024 7:43 pm