From: Keith Owens <kaos@ocs.com.au>
To: Paul Gortmaker <p_gortmaker@yahoo.com>
Cc: linux-kernel list <linux-kernel@vger.kernel.org>
Subject: Re: start___kallsyms missing from i386 vmlinux.lds ?
Date: Tue, 02 Jan 2001 21:30:33 +1100 [thread overview]
Message-ID: <27530.978431433@ocs3.ocs-net> (raw)
In-Reply-To: Your message of "Tue, 02 Jan 2001 04:39:39 CDT." <3A51A1DB.74540C02@yahoo.com>
On Tue, 02 Jan 2001 04:39:39 -0500,
Paul Gortmaker <p_gortmaker@yahoo.com> wrote:
>Keith Owens wrote:
>> kernel/module.c defines
>> extern const char __start___kallsyms[] __attribute__ ((weak));
>> extern const char __stop___kallsyms[] __attribute__ ((weak));
>>
>> The symbols are weak and do not need to be defined. If gcc is not
>> honouring __attribute__ ((weak)) then you have a broken or obsolete
>> version of gcc. You need at least gcc 2.91.66 for kernel 2.4.
>
>Yep, saw the weak part - just noted while scanning test11 diff
>that they were defined like the above patch for arch/sparc* and
>wondered if the inconsistency was intentional.
Some sparc users have a slightly older version of gcc, built shortly
before 'weak' support was added, which required those symbols to be
defined. Dave Miller thought the compiler problem was widespread
enough to justify changing the source to suit the compiler instead of
forcing sparc users to upgrade. I suspect that super-h has the same
problem of old compilers, I noticed that somebody added the symbols to
sh/vmlinux.lds.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-02 11:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-02 6:56 start___kallsyms missing from i386 vmlinux.lds ? Paul Gortmaker
2001-01-02 7:43 ` Keith Owens
2001-01-02 9:39 ` Paul Gortmaker
2001-01-02 10:30 ` Keith Owens [this message]
2001-01-03 1:17 ` David Woodhouse
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=27530.978431433@ocs3.ocs-net \
--to=kaos@ocs.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=p_gortmaker@yahoo.com \
/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