linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Mark Pilon <mark.pilon@minolta-qms.com>
To: linuxppc-embedded@lists.linuxppc.org
Subject: init fails w/ new build of gcc & glibc
Date: Fri, 17 Aug 2001 14:47:17 -0600	[thread overview]
Message-ID: <3B7D82D5.DD98A109@minolta-qms.com> (raw)


Hi,

I'm attempting to build gcc for powerPC as well as new binutils &
glibc, -- all in an attempt to support a new 4xx chip w/ floating
point.

I'm using HHL 1.2 for the 405 & walnut as my base and am attempting
to start using the new compiler and libraries:

I've recompiled the kernel w/ the new compiler (albeit -msoft-float)
and it boots fine;

running w/ the hhl 1.2 libraries the whole system runs fine;

supplying all of the libraries built under the new glibc causes the
following when init is spawned:

Kernel panic: Attempted to kill init!
init: error while loading shared libraries: cannot open sh ared object file:
cannot load shared object file: No such file or directory

-- there is no comment as to what's missing ...

I can spawn sash in place of 'init' and that runs (no surprise ...)
-- I realize I've probably screwed up something pretty basic --
I'm probably out of synch somewhere in the libraries but don't
know how to debug this further.

under sash, when I try to -exec /bin/ldd /bin/busybox all I get
is a file-not-found for ldd ...

thanks in advance,

Mark

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

             reply	other threads:[~2001-08-17 20:47 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-17 20:47 Mark Pilon [this message]
2001-08-17 21:48 ` init fails w/ new build of gcc & glibc Mark Hatle
2001-08-17 22:16   ` Dr. Craig Hollabaugh
2001-08-17 22:22     ` Mark Hatle
2001-08-17 22:28       ` Joe Green
2001-08-17 22:54       ` Dr. Craig Hollabaugh
2001-08-17 23:15         ` Mark Hatle
2001-08-17 23:29           ` Dr. Craig Hollabaugh
2001-08-17 21:50 ` Joe Green
2001-08-17 22:07 ` Dr. Craig Hollabaugh

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=3B7D82D5.DD98A109@minolta-qms.com \
    --to=mark.pilon@minolta-qms.com \
    --cc=linuxppc-embedded@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).