You could also install J and all addons on a linux system, then copy the entire J directory over and just replace the binaries in ../bin. Most addons should work.
On Thu, Jun 7, 2018 at 6:41 AM, S H Makdisi <stepv...@bitmessage.ch> wrote: > So first, pacman will assume if you are running a unix-like, it checks for > 'Darwin' and then 'Android', and ends up defaulting with 'Linux'. (This > creates another issue as the Linux HTTPCMD involves wget, which is not in > the > base OpenBSD system, it would have to use curl(1) like 'Darwin'). > > Then, it seems, around line 260 of pacman.ijs in the jsource/jlibrary dir, > pacman chooses how to deal with the zips it gets, based on OS, this time no > case ends up true and so this is bypassed, i guess. > > On line 370 is where the tar command's options are set. This becomes tricky > because, IIRC, BSD's tar is different from GNU tar, but I don't recall > how. I > think I remember pacman attempting to download the windows zip file, not > the > linux tar however, which would create another problem, but that I can't be > sure of. > > Ultimately though, fixing the stuff in the jsource/jlibrary becomes moot. > If > you do manage to get just the base library installed, it will replace the > jsource/jlibrary/pacman.ijs with the base8/pacman version. > > Also, I have uploaded the changes I have made to github. I just tested the > compilation, and it works on my system (no stdlib issues, etc). It is > available here: https://github.com/stepvhen/jsource/tree/openbsd > > [2018-06-07 14:06] > > > > Ok. So if I understand right, while reading stdlib.ijs I encounter > > an error (either due to setlocale, trying to read /proc/cpuinfo, or > > whatever; basically because the script thinks I run linux, which I don't) > > and the whole process of 'booting' is stopped. That's why I don't have > > commands such as install, jpath, etc. > > > > By commenting out several things in stdlib.ijs, I am now a step further. > > I can issue > > install 'all' > > which starts, but ends instantaneously, due to wrong invocation of tar. > > > > The question I have is this: > > Can I do something so that upon encountering an error I also get > > the name and the line of (in) the file being read? > > So that I can easily navigate to the place instead of grepping and > > guessing? > > > > Thanks > > Ruda > > ---------------------------------------------------------------------- > > For information about J forums see http://www.jsoftware.com/forums.htm > > ---------------------------------------------------------------------- > For information about J forums see http://www.jsoftware.com/forums.htm > ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
