All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@zip.com.au>
To: Adrian Bunk <bunk@fs.tum.de>
Cc: lkml <linux-kernel@vger.kernel.org>,
	Marcelo Tosatti <marcelo@conectiva.com.br>
Subject: Re: [patch] compile fixes
Date: Thu, 14 Feb 2002 02:01:37 -0800	[thread overview]
Message-ID: <3C6B8B01.E0A3B194@zip.com.au> (raw)
In-Reply-To: <3C6A2F86.E5C322D4@zip.com.au> <Pine.NEB.4.44.0202141036020.25879-100000@mimas.fachschaften.tu-muenchen.de>

Adrian Bunk wrote:
> 
> On Wed, 13 Feb 2002, Andrew Morton wrote:
> 
> > This patch should fix all the remaining .text.exit problems
> > which have resulted from recent binutils changes.   For all
> > files which are accessible to an x86 build.
> >...
> 
> Thanks for your work, I tried to compile non-modular 2.4.18-pre9 with this
> patch and as much as possible enabled. The .text.exit errors are now gone
> with one exception:
> 
> drivers/char/char.o(.data+0xacf4): undefined reference to `local symbols
> in discarded section .text.exit'
> 

Well that's odd.  Perhaps something is configured differently.
Please do this:

	make bzImage

Near the end of the build, see the line 

	ld -m elf_i386 -T  <lots of .o files> -o vmlinux

delete all the .o files which appear that command line.

Now, run

ld -m elf_i386 -T arch/i386/vmlinux.lds $(find . -name '*.o') 2> /tmp/1

Now, go through all the junk in /tmp/1 and search for the text "discarded".
It will mention a filename.   That's the info we want.


Thanks.


-

  reply	other threads:[~2002-02-14 10:03 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-13  9:19 [patch] compile fixes Andrew Morton
2002-02-13 14:56 ` David Woodhouse
2002-02-14  9:47 ` Adrian Bunk
2002-02-14 10:01   ` Andrew Morton [this message]
2002-02-14 14:12     ` Adrian Bunk
2002-02-14 13:58 ` Adrian Bunk
2002-02-15  3:51   ` Andrew Morton
  -- strict thread matches above, loose matches on Subject: below --
2002-06-02 14:01 [PATCH] Compile fixes Marcus Sundberg
2002-06-04  7:44 ` Harald Welte
2002-06-04 11:10   ` Marcus Sundberg

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=3C6B8B01.E0A3B194@zip.com.au \
    --to=akpm@zip.com.au \
    --cc=bunk@fs.tum.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo@conectiva.com.br \
    /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.