From: Ralf Baechle <ralf@oss.sgi.com>
To: Karsten Merker <karsten@excalibur.cologne.de>
Cc: linux-mips@oss.sgi.com
Subject: Re: build-problems: GNU fileutils 4.01 on mipsel with glibc 2.2.2
Date: Sun, 4 Mar 2001 23:15:34 +0100 [thread overview]
Message-ID: <20010304231534.B17775@bacchus.dhis.org> (raw)
In-Reply-To: <20010304213609.B25825@linuxtag.org>; from karsten@excalibur.cologne.de on Sun, Mar 04, 2001 at 09:36:09PM +0100
On Sun, Mar 04, 2001 at 09:36:09PM +0100, Karsten Merker wrote:
> I am trying to get the components for a Debian mipsel-base.tgz built,
> based on glibc-2.2.2. I am working in a chroot()-environment, where I have
> installed glibc 2.2.2, binutils 2.10.91 and gcc 2.95.3 as precompiled
> binaries, all from Maciej's packages (glibc-2.2.2-2.mipsel.rpm,
> gcc-2.95.3-14.mipsel.rpm, binutils-2.10.91-1.mipsel.rpm plus devel and
> dependency packages). Gawk and perl are self-compiled inside the
> chroot()-environment. When trying to compile fileutils, the ./configure
> starts ok, but when coming to "checking for working mktime..." the script
> just hangs forever, and according to top there is nothing consuming CPU
> time (except for top itself). Compiling the fileutils on the "host
> system", i.e. outside the chroot()-environment using egcs-1.0.3a and
> glibc-2.0.6 the problem does not appear. Can anybody confirm this on
> another system? Any ideas what can be the reason for this?
Does you chroot environment have a mounted /proc filesystem? In the past
we had obscure libc bugs which were triggered when /proc were not
mounted.
Ralf
next prev parent reply other threads:[~2001-03-04 22:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-04 20:36 build-problems: GNU fileutils 4.01 on mipsel with glibc 2.2.2 Karsten Merker
2001-03-04 22:15 ` Ralf Baechle [this message]
2001-03-05 18:59 ` Karsten Merker
2001-03-06 6:32 ` Keith M Wesolowski
2001-03-06 13:59 ` Ralf Baechle
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=20010304231534.B17775@bacchus.dhis.org \
--to=ralf@oss.sgi.com \
--cc=karsten@excalibur.cologne.de \
--cc=linux-mips@oss.sgi.com \
/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