All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Curbo <jcurbo@acm.org>
To: linux-kernel@vger.kernel.org
Subject: (2.5.5-dj2) still getting .text.exit linker errors
Date: Wed, 27 Feb 2002 16:01:38 -0600	[thread overview]
Message-ID: <20020227220138.GA5644@carthage> (raw)

[note: I am not subscribed, please cc: me in replies]

When compiling 2.5.5-dj2, I am still getting a .text.exit linker error:

drivers/net/net.o(.data+0x1274): undefined reference to `local symbols 
in discarded section .text.exit'

I am using Debian unstable, binutils 2.11.93.0.2:

ii  binutils       2.11.93.0.2-2

I can get it to link if I follow the directions that the Debian
maintainer has been giving out (deleting the .text.exit line from
vmlinux.lds) but that isn't the right solution, and I don't have the
abilities to actually fix it. My ver_linux output is appeneded at the
end. Thanks in advance.

James

Linux carthage 2.5.5-dj2 #1 Wed Feb 27 01:08:00 CST 2002 i686 unknown

Gnu C                  2.95.4
Gnu make               3.79.1
util-linux             2.11n
mount                  2.11n
modutils               2.4.13
e2fsprogs              1.26
Linux C Library        2.2.5
Dynamic linker (ldd)   2.2.5
Procps                 2.0.7
Net-tools              1.60
Console-tools          0.2.3
Sh-utils               2.0.11
Modules Loaded         emu10k1 ac97_codec sound

-- 
James Curbo <jcurbo@acm.org> <jc108788@rc.hsu.edu>
Undergraduate Computer Science, Henderson State University
PGP Keys at <http://reddie.henderson.edu/~curboj/>
Public Keys: PGP - 1024/0x76E2061B GNUPG - 1024D/0x3EEA7288

             reply	other threads:[~2002-02-27 22:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-27 22:01 James Curbo [this message]
2002-02-27 22:41 ` (2.5.5-dj2) still getting .text.exit linker errors Dave Jones
2002-02-28  0:41   ` James Curbo
2002-02-27 22:52 ` Keith Owens

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=20020227220138.GA5644@carthage \
    --to=jcurbo@acm.org \
    --cc=linux-kernel@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 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.