All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Andreas Bießmann" <andreas.devel@googlemail.com>
To: linux-mips@linux-mips.org
Subject: broken eglibc
Date: Mon, 30 Aug 2010 11:46:08 +0200	[thread overview]
Message-ID: <4C7B7DE0.9020800@googlemail.com> (raw)

Hi all,

we have a problem building eglibc-2.12 (svn 11187) with current (some
days old) head 2.6.35.3 (stable tree). Same sources for eglibc but
sysroot headers from 2.6.35-rc3 does work fine.
The problem shows up when using the built libc on target. We use n32
built and start a homebrew rootfs. The broken libc has (at least) errors
in showing directory listings. A ls shows wired output:

---8<---
/ # ls
ls: ./sr: No such file or directory
ls: ./ar: No such file or directory
ls: ./ib: No such file or directory
ls: ./oot: No such file or directory
ls: ./tc: No such file or directory
ls: ./inuxrc: No such file or directory
ls: ./ib32: No such file or directory
ls: ./ev: No such file or directory
ls: ./nit: No such file or directory
ls: ./nt: No such file or directory
ls: ./mp: No such file or directory
ls: ./in: No such file or directory
ls: ./ys: No such file or directory
ls: ./roc: No such file or directory
bin
--->8---

As you may see the first character is truncated. Only changing the
contents of /lib32 directory (libc related stuff) with working built
(sysroot include out of 2.6.35-rc3 kernel headers) the 'ls' is working.

Has anyone encountered similar behaviour?

regards

Andreas Bießmann

                 reply	other threads:[~2010-08-30  9:46 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4C7B7DE0.9020800@googlemail.com \
    --to=andreas.devel@googlemail.com \
    --cc=linux-mips@linux-mips.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.