LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: <srinivas.surabhi@wipro.com>
To: <linuxppc-embedded@ozlabs.org>
Subject: GLIBC_2.0 not defined  in libc.so.6 ---- problem
Date: Tue, 22 Feb 2005 18:57:18 +0530	[thread overview]
Message-ID: <EF9B29C78F41FA488927FCBC7750AF0E011DA6BE@hyd-mdp-msg.wipro.com> (raw)



Hi,

I am facing the following problem with kernel 2.4.20. Can any body throw
light on it?

...
Freeing unused kernel memory: 56k init
init: relocation error: init: symbol optarg, version GLIBC_2.0 not
defined in file libc.so.6 with link time reference
Kernel panic: Attempted to kill init!


My one more doubt is the file libc.so.6 is it mandatory to be linked?

Thanks in advance=0D
-SS



Confidentiality Notice=0D

The information contained in this electronic message and any attachments to=
 this message are intended
for the exclusive use of the addressee(s) and may contain confidential or=
 privileged information. If
you are not the intended recipient, please notify the sender at Wipro or=
 Mailadmin@wipro.com immediately
and destroy all copies of this message and any attachments.

                 reply	other threads:[~2005-02-22 13:27 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=EF9B29C78F41FA488927FCBC7750AF0E011DA6BE@hyd-mdp-msg.wipro.com \
    --to=srinivas.surabhi@wipro.com \
    --cc=linuxppc-embedded@ozlabs.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