linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Keith Owens <kaos@ocs.com.au>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: Where does ppc define __start___ksymtab?
Date: Thu, 03 Aug 2000 21:40:45 +1000	[thread overview]
Message-ID: <31440.965302845@ocs3.ocs-net> (raw)
In-Reply-To: Your message of "Wed, 02 Aug 2000 22:18:08 +0200." <Pine.LNX.4.10.10008022216520.833-100000@cassiopeia.home>


On Wed, 2 Aug 2000 22:18:08 +0200 (CEST),
Geert Uytterhoeven <geert@linux-m68k.org> wrote:
>On Tue, 1 Aug 2000, Keith Owens wrote:
>> Please cc: kaos@ocs.com.au on replies, I am not on this list.
>>
>> I have been trying to find where ppc defines __start___ksymtab and
>> __stop___ksymtab symbols.
>
>I'm no gcc linkscript expert, but doesn't the absence of __ksymtab stuff in
>vmlinux.lds simply mean that gcc can put stuff for section __ksymtab wherever
>it wants in the final object file?

Placement was not the problem.  It was the "magic" definition of
__start___ksymtab and __stop___ksymtab that had me baffled.


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

  parent reply	other threads:[~2000-08-03 11:40 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-08-01  6:40 Where does ppc define __start___ksymtab? Keith Owens
2000-08-02 20:18 ` Geert Uytterhoeven
2000-08-03 11:28   ` Gabriel Paubert
2000-08-03 11:40   ` Keith Owens [this message]
2000-08-03  6:13 ` Paul Mackerras
2000-08-03  8:03   ` Keith Owens
2000-08-03  9:58     ` Gabriel Paubert
2000-08-03 11:43       ` Keith Owens
2000-08-03 12:01         ` Gabriel Paubert
2000-08-03 12:18           ` Keith Owens
2000-08-03 12:31             ` Gabriel Paubert
2000-08-03 12:27           ` Keith Owens
2000-08-03 13:08           ` Franz Sirl

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=31440.965302845@ocs3.ocs-net \
    --to=kaos@ocs.com.au \
    --cc=geert@linux-m68k.org \
    --cc=linuxppc-dev@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).