I've got a workaround. Before starting maxima, run
sudo sysctl kernel.randomize_va_space=0
This turns off a security-hardening setting (see https://wiki.ubuntu.com/Security/Features#ASLR) which gcl doesn't play nice with. You may want to reset it after you're done with maxima, for me the default value is 2, you can find it out by running "sysctl kernel.randomize_va_space" prior to turning off.
So there's an underlying problem with gcl which FTBFS for me because of this problem. I think we should find a way to fix gcl first, then rebuild maxima against fixed gcl.
I've got a workaround. Before starting maxima, run
sudo sysctl kernel. randomize_ va_space= 0
This turns off a security-hardening setting (see https:/ /wiki.ubuntu. com/Security/ Features# ASLR) which gcl doesn't play nice with. You may want to reset it after you're done with maxima, for me the default value is 2, you can find it out by running "sysctl kernel. randomize_ va_space" prior to turning off.
So there's an underlying problem with gcl which FTBFS for me because of this problem. I think we should find a way to fix gcl first, then rebuild maxima against fixed gcl.