It's updated. It built on Ubuntu when I tested it locally. We'll see
how it does on the buildd's.
https://launchpad.net/ubuntu/+source/axiom/20091101-7
** Changed in: axiom (Ubuntu)
Status: In Progress => Fix Released
--
axiom version 20081101 FTBFS on all platforms
https://bugs.launchp
** Changed in: axiom (Ubuntu)
Assignee: (unassigned) => Brian Thomason (brian-thomason)
** Changed in: axiom (Ubuntu)
Status: New => In Progress
--
axiom version 20081101 FTBFS on all platforms
https://bugs.launchpad.net/bugs/387255
You received this bug notification because you are
** Changed in: axiom (Debian)
Status: New => Fix Released
** Changed in: axiom
Status: New => Fix Released
--
axiom version 20081101 FTBFS on all platforms
https://bugs.launchpad.net/bugs/387255
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
Hello daly, thanks for your work and helping the distribution! It may be best
to contact the Debian maintainer for Axiom directly:
Camm Maguire
He does not seem to be actively working on it in Debian, but he should
be the contact (and the person who can get it uploaded). If he doesn't
respond, y
** Changed in: axiom (Debian)
Status: Unknown => New
** Changed in: axiom
Status: Unknown => New
--
axiom version 20081101 FTBFS on all platforms
https://bugs.launchpad.net/bugs/387255
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
Morten Kjeldgaard wrote:
> That's what I would have done, but SELINUX does not appear to be enabled
> on Ubuntu's kernel:
>
> $ grep SELINUX /boot/config-2.6.28-11-generic
> CONFIG_SECURITY_SELINUX=y
> CONFIG_SECURITY_SELINUX_AVC_STATS=y
> CONFIG_SECURITY_SELINUX_BOOTPARAM=y
> CONFIG_SECURITY_SELIN
That's what I would have done, but SELINUX does not appear to be enabled
on Ubuntu's kernel:
$ grep SELINUX /boot/config-2.6.28-11-generic
CONFIG_SECURITY_SELINUX=y
CONFIG_SECURITY_SELINUX_AVC_STATS=y
CONFIG_SECURITY_SELINUX_BOOTPARAM=y
CONFIG_SECURITY_SELINUX_BOOTPARAM_VALUE=0
CONFIG_SECURITY_SEL
Morten Kjeldgaard wrote:
> I could get version 20090301 to compile by applying appropriate setarch
> commands as shown in the attached patch. However, after the build,
> invokes axiom and it segfaults:
>
> echo ")lisp (progn (setq compiler::*default-system-p* nil)(si::save-system
> \"foo\"))" |
>
I could get version 20090301 to compile by applying appropriate setarch
commands as shown in the attached patch. However, after the build,
invokes axiom and it segfaults:
echo ")lisp (progn (setq compiler::*default-system-p* nil)(si::save-system
\"foo\"))" |
AXIOM=/build/mok-axiom_20090301-0ubun
Trying to compile the newest version (20090301), I noticed the following
lines in the configure output:
checking for sbrk... yes
checking for ADDR_NO_RANDOMIZE constant... yes, 4
checking for personality(ADDR_NO_RANDOMIZE) support... no
checking that sbrk is (now) non-random... no
Cannot build
10 matches
Mail list logo
