ALT Linux Team development discussions
 help / color / mirror / Atom feed
From: "Dmitry V. Levin" <ldv@altlinux.org>
To: ALT Devel discussion list <devel@lists.altlinux.org>
Subject: Re: [devel] gcl-2.6.7-alt5: rebuild failed
Date: Mon, 9 Oct 2006 01:11:20 +0400
Message-ID: <20061008211120.GA14601@basalt.office.altlinux.org> (raw)
In-Reply-To: <45296140.1010704@mail.ru>

[-- Attachment #1: Type: text/plain, Size: 1219 bytes --]

On Sun, Oct 08, 2006 at 11:36:16PM +0300, Vadim V. Zhytnikov wrote:
> > Package: gcl-2.6.7-alt5
> > Packager: Vadim V. Zhytnikov <vvzhy@altlinux>
> > Status: rebuild failed.
> > Please investigate.
> 
> > checking for sbrk... yes
> > checking for randomized sbrk... yes
> > checking for randomized brk remedy... no
> > Cannot build with randomized sbrk
> 
> На днях робот огорчил меня тем, что перестал
> пересобираться gcl (GNU Common Lisp).

gcl собирается не на всяком ядре.
У меня во время сборочного тестирования на 2.6.16-std26-smp-alt10
собрался, а на i586 2.6.16-ovz-smp-alt7 не собрался.

> Проблема gcl с randomized sbrk известна по
> Федоре.  По идее, она должна разрешаться и для Сизифа.

Должна, у нас и kernel и toolchain родственные.

> Но у меня на домашней машине randomized sbrk нет,
> что чертовски затрудняет разбирательство.
> 
> Собственно вопрос: откуда оно берётся это
> самое randomized sbrk? Нужно ставить специальную
> версию ядра? Какую?

randomized sbrk есть на i586 ovz-ядре с включённым (по умолчанию)
/proc/sys/kernel/randomize_va_space.

Самый простой способ проверить:
$ comm <(fgrep heap /proc/self/maps) <(fgrep heap /proc/self/maps)


-- 
ldv

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2006-10-08 21:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-08 20:36 ` Vadim V. Zhytnikov
2006-10-08 21:11   ` Dmitry V. Levin [this message]
2006-10-08 21:48     ` Dmitry V. Levin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20061008211120.GA14601@basalt.office.altlinux.org \
    --to=ldv@altlinux.org \
    --cc=devel@lists.altlinux.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

ALT Linux Team development discussions

This inbox may be cloned and mirrored by anyone:

	git clone --mirror http://lore.altlinux.org/devel/0 devel/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 devel devel/ http://lore.altlinux.org/devel \
		devel@altlinux.org devel@altlinux.ru devel@lists.altlinux.org devel@lists.altlinux.ru devel@linux.iplabs.ru mandrake-russian@linuxteam.iplabs.ru sisyphus@linuxteam.iplabs.ru
	public-inbox-index devel

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://lore.altlinux.org/org.altlinux.lists.devel


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git