Re: binary incompatibility among mipsel buildds
Greetings! This is still an issue on phrixos alone, it appears. As a
reminder, this buildd alone disables sbrk address unrandomization at the
user level (using the personality syscall). Could you please change the
setting (kernel.randomize_va_space I think) responsible for this?
Andreas Barth <email@example.com> writes:
> * Camm Maguire (firstname.lastname@example.org) [101031 20:30]:
>> Thanks so much! Any idea on what might have caused this recent
>> failure on phrixos:
>> checking for sbrk... yes
>> checking for ADDR_NO_RANDOMIZE constant... yes, 40000
>> checking for personality(ADDR_NO_RANDOMIZE) support... yes
>> 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)
> The output seems to indicate that ADDR_NO_RANDOMIZE is available?
>> - recompile your kernel with CONFIG_COMPAT_BRK (if it has that option)
>> - run sysctl kernel.randomize_va_space=0 before using gcl
>> gcl and dependencies re-exec with ADDR_NO_RANDOMIZE set to get
>> traditional sbrk contiguous to the .data segment end.
> I upgraded to the Debian 2.6.36-rc6-loongson-2f kernel (the machine
> runs now for the first time an default distribution kernel). That
> might have some impact - I don't know.
> Also, kernel.randomize_va_space=2 currently.
Camm Maguire email@example.com
"The earth is but one country, and mankind its citizens." -- Baha'u'llah