I wonder if anyone understands this. Earlier this year I managed to install
poplog v16 on a Stonebook mini laptop running fedora31 by
downloading and running this script
https://www.cs.bham.ac.uk/research/projects/poplog/V16/getpoplog.sh
Part of the output is this:
run first build
./build_pop0 >& buildout1
I am sure that worked earlier this year on this machine, but I now have a
later version of fedora 31 running, and the installation doesn't work, as
described below.
I had to reinstall fedora because I recently decided that Windows 10 (home)
was taking up too much space on the 500 GB drive, so I tried shrinking
windows so that I could expand linux. I ended up making the machine
unusable, so I reinstalled fedora 31 using 'live' version on a usb stick,
and leaving space for windows (less space than windows had previously
occupied). I then reinstalled windows 10 from a usb stick, and managed to
get that working, with a choice to boot into windows or linux, as
previously, but using a later version of linux:
uname -rv
shows
5.6.19-200.fc31.x86_64 #1 SMP Wed Jun 17 16:54:35 UTC 2020
After that system re-building process I tried to reinstall poplog, using
getpoplog.sh as above, which had worked earlier this year, with an earlier
verison of fedora 31 running.
But now I cannot get this portion of the installation script to work:
./build_pop0 >& buildout1
Examining the content of buildout1, shows that the process failed:
Poplog Version 16 (64 bit)
/usr/local/poplog/v16/poplog_base/pop/src
rebuilding system images
opt=-d
opt=-a=x86_64
opt=popc
IMAGE=popc
<<<<<<< Access Violation: PC = 0000000000542A94, Addr = 00000000007AD000,
Code = 2 >>>>>>>
pop_architecture = x86_64
calling pop11_compile
;;; MISHAP - serr: MEMORY ACCESS VIOLATION (attempt to alter non-writeable
;;; system structure?)
;;; FILE : /home/usr/local/poplog/v16/poplog_base/pop/src/syscomp/make_po
;;; pc.p LINE NUMBER: 12
;;; PRINT DOING
;;; DOING : inits Sys_cons_device nextitem pop_setpop_compiler
;;;
;;; <<<<<<< Access Violation: PC = 0000000000508AAC, Addr = 00000000007AD040,
;;; Code = 2 >>>>>>>
;;;
;;;
;;; MISHAP - serr: MEMORY ACCESS VIOLATION (attempt to alter non-writeable
;;; system structure?)
;;; FILE : /home/usr/local/poplog/v16/poplog_base/pop/src/syscomp/make_po
;;; pc.p LINE NUMBER: 12
;;; PRINT DOING
;;; DOING : consstring inits Sys_cons_device nextitem pop_setpop_compiler
;;;
;;;
;;; <<<<<<< Access Violation: PC = 0000000000508AAC, Addr = 00000000007AD0A8,
;;; Code = 2 >>>>>>>
... etc.
and the required new version of basepop11 does not get built.
Nothing has changed in the poplog V16 package since February, so the
problem must be a change in linux (Fedora 31).
Fortunately I can run the old prebuilt version of 32 bit poplog (poplog v15.65)
so I have a working version of ved, my favourite editor.
Does anyone have any idea what could have changed in Fedora 31 between last
February and now that stops the initial compilation working, as indicated
above?
Aaron
