This bug was fixed in the package clisp -
1:2.49.20180218+really2.49.92-3ubuntu1
---
clisp (1:2.49.20180218+really2.49.92-3ubuntu1) impish; urgency=medium
* Disable PIE when building for ppc64el and s390x as PIE executables get
loaded at addresses that do not work with clisp's
Ah so the unrelated reasons would be that glibc snapshot I have in that
PPA -- clisp with PIE disabled for s390x and ppc64el built fine in a
different PPA and then xindy built with the resulting clisp too so I'll
upload that. It would be better to fix this properly by choosing better
addresses for
If I disable PIE for ppc64el it builds on my canonistack instance, but
all architectures fail to build in my PPA for what seem to be unrelated
reasons :(
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
So I think what changed to break this was this change in the kernel:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=47ebb09d54856500c5a5e14824781902b3bb738e
which I'm pretty sure got backported everywhere. But this is only the
base address for dynamic executables. I
Correction, this doesn't seem to be a change in the KASLR behavior, so
much as in the base addresses used by the kernel for mappings.
I'm not sure how to figure out a "correct" address mask to use for this
on ppc64el.
--
You received this bug notification because you are a member of Ubuntu
Looking into the build failure of clisp on Ubuntu ppc64el, it looks like
a difference in behavior of KASLR. Output from the failure log in the
bug shows:
checking for the code address range... 0x02AA3900
Successive invocations on Ubuntu with a focal kernel show:
checking for the code
I'll time-box my activity for now, since it works on other platforms
a removal might be too hard.
But if you happen to find other related issues please add them here so that
when it gets too much it can be considered to be removed.
For the sake of not fully giving up I've reported it upstream
For Reference - the failed builds that had me start to look at this:
https://launchpad.net/ubuntu/+source/clisp/1:2.49.20180218+really2.49.92-3build5
https://launchpad.net/ubuntu/+source/xindy/2.5.1.20160104-10
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
** Attachment added: "upstream tarball of clisp failing the same way"
https://bugs.launchpad.net/ubuntu/+source/xindy/+bug/1931531/+attachment/5503834/+files/clsip-clean-fail.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Good build log:
https://launchpadlibrarian.net/440395396/buildlog_ubuntu-eoan-s390x.clisp_1%3A2.49.20180218+really2.49.92-3build3_BUILDING.txt.gz
Happened mid Eoan on 2019-09-05 so final Eoan might be just as bad as
focal.
Build xindy/clisp in Disco - same fail
Build xindy/clisp in Eoan - same
As last resort I have built the latest clisp from upstream
without packaging magic just the way upstream intends to.
But since the last version from upstream is more than a decade old from
2010-07-07 maybe the time has come to ignore it.
Latest release still is that from
I've built the same in Hirsute, just as broken :-/
Last successful build was in Focal.
Note Focal has the same clisp version and only two debian packaging
versions bumped for xindy.
So I'll start at Focal trying to find a working environment.
build impish version of clisp in impish - fail
build
Note:
On Debian s390x xindy build doesn't even start to build as it has missing
build-depdencies.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1931531
Title:
clisp crashed in impish compiling
The code for the error in clisp is:
/* Verify the oint_addr_shift value w.r.t. the autoconfigured CODE_ADDRESS_RANGE
and MALLOC_ADDRESS_RANGE values. */
#if !defined(WIDE_SOFT)
/* The CODE_ADDRESS_RANGE needs to be checked because we store code
pointers in Lisp objects (cf. macro
Clisp error:
/home/ubuntu/clisp-2.49.20180218+really2.49.92/src/lispbibl.d:6673:6: error:
#error oint_addr_mask does not cover CODE_ADDRESS_RANGE !!
6673 | #error oint_addr_mask does not cover CODE_ADDRESS_RANGE !!
|
--
You received this bug notification because you are a member of
** Tags added: update-excuse
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1931531
Title:
clisp crashed in impish compiling xindy
To manage notifications about this bug go to:
Attaching a full backtrace of the fail.
** Attachment added: "Detailed backtrace of the fail (long thanks to the lisp
paradigms)"
https://bugs.launchpad.net/ubuntu/+source/xindy/+bug/1931531/+attachment/5503785/+files/clisp-xindy-fail.log
--
You received this bug notification because you
17 matches
Mail list logo
