[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Gcl-devel] Re: Bug#474909: New build log

From: Camm Maguire
Subject: [Gcl-devel] Re: Bug#474909: New build log
Date: 01 Aug 2008 10:09:21 -0400
User-agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2

Greetings, and thanks for the feedback!  WOuld you mind excerpting the
C routines corresponding to the two 'no' results below, compile with
-g and run under gdb to let me know where they fail?  I am surprised
at the failure.  

Specifically, what is wrong with

void gprof_cleanup() {};
int main(int argc,char *argv[],char *envp[]) {
#include "h/unrandomize.h"
return 0;}

when compiled and run in the topdir of gcl source?

Separately, I've found that Debian is not passing personality changes
across execve, unlike Fedora.  Sure wish someone could explain the
variants out there to me.

Take care,

David Bremner <address@hidden> writes:

> Intially on debian kernel 2.6.25-7, configuration of gcl 2.6.7-38
> failed (log on http://www.cs.unb.ca/~bremner/logs/2008/07/31/gcl.log
> but I think there is nothing too surprising there) with the message
> checking for ADDR_NO_RANDOMIZE constant... yes, 40000
> checking for personality(ADDR_NO_RANDOMIZE) support... no
> checking that sbrk is (now) non-random... no
> Cannot build with randomized sbrk. Your options:
>  - upgrade to a kernel/libc that knows about personality(ADDR_NO_RANDOMIZE)
>  - recompile your kernel with CONFIG_COMPAT_BRK (if it has that option)
>  - run sysctl kernel.randomize_va_space=0 before using gcl
> Following this advice, I ran
>  sysctl kernel.randomize_va_space=0
> After this I was able to successfuly build gcl and then use that gcl to 
> build maxima-5.15.0-2.  This build of maxima seems OK; run_testsuite() 
> produces no unexpected errors.
> David

Camm Maguire                                            address@hidden
"The earth is but one country, and mankind its citizens."  --  Baha'u'llah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]