public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@suse.de>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] That getpagesize() problem again!
Date: Thu, 25 Jan 2001 11:20:55 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590693005097@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590693005096@msgid-missing>

Francis Galiegue <fg@mandrakesoft.com> writes:

|> When trying to install only two packages via RPM in a chroot, this is what I
|> get:
|> 
|> rpm: ../sysdeps/unix/sysv/linux/ia64/getpagesize.c:36: __getpagesize: Assertion
|> `_dl_pagesize != 0'
|> failed.
|> 
|> Then, abort and core dump.
|> 
|> What I'd like to know is why, in the glibc file mentioned in the error,
|> __getpagesize is defined as such:
|> 
|> int
|> __getpagesize ()
|> {
|>   assert (_dl_pagesize != 0);
|>   return _dl_pagesize;
|> }
|> 
|> (that's glibc 2.2.1, but 2.2 exhibits the same behaviour)
|> 
|> This looks all the more strange that you can define the page size during kernel
|> compile! A sample test program which I made using the getpagesize() syscall
|> yields the correct value, though...

If the getpagesize syscall works, then your kernel is too old.

|> What should I do?

You need to run kernel 2.4.0-test9 with the 001030 patch or later.
Earlier versions didn't pass AT_PAGESZ in all cases.

Andreas.

-- 
Andreas Schwab                                  "And now for something
SuSE Labs                                        completely different."
Andreas.Schwab@suse.de
SuSE GmbH, Schanzäckerstr. 10, D-90443 Nürnberg


  reply	other threads:[~2001-01-25 11:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-25 10:26 [Linux-ia64] That getpagesize() problem again! Francis Galiegue
2001-01-25 11:20 ` Andreas Schwab [this message]
2001-01-25 14:25 ` Jes Sorensen
2001-01-25 15:34 ` Francis Galiegue

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=marc-linux-ia64-105590693005097@msgid-missing \
    --to=schwab@suse.de \
    --cc=linux-ia64@vger.kernel.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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox