From: James Courtier-Dutton <James@superbug.demon.co.uk>
To: Nicholas Wourms <dragon@gentoo.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.21-rc1-ac3: unresolved symbol only with gcc-3.3
Date: Tue, 29 Apr 2003 12:54:20 +0100 [thread overview]
Message-ID: <3EAE67EC.5060702@superbug.demon.co.uk> (raw)
In-Reply-To: <3EAE6384.3050702@gentoo.org>
Nicholas Wourms wrote:
> Axel Siebenwirth wrote:
>
>> Hi,
>>
>> today I have successfully built 2.4.21-rc1-ac3 with gcc-3.2.3.
>> Everything
>> was fine.
>> Then I built with gcc-3.3 and I encountered an error:
>>
>> net/network.o(.text+0xdcd7): In function `rtnetlink_rcv':
>> : undefined reference to `rtnetlink_rcv_skb'
>>
>> This build error only occurs with gcc-3.3.
>>
>> Can somebody who knows the kernel look whether the error is
>> legitimate or gcc is making errors.
>
>
> I'm not sure if this is necessarily the right way, but changing the
> declaration for rtnetlink_rcv_skb() in net/core/rtnetlink.c from
> "extern" to "static" seems to have fixed the problem for me. In any
> case, I couldn't find any external references to that function, so it
> seems to me that this is the way to go.
>
> Cheers,
> Nicholas
>
>
Please ignore my last email. I in fact did the same as Nicholas and it
fixed it for me.
I also had a problem in the reiserfs module, with a kprintf statement
format string spread over two lines. Removing what looked like a
misplaced newline fixed it.
Cheers
James
next prev parent reply other threads:[~2003-04-29 11:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-29 10:44 2.4.21-rc1-ac3: unresolved symbol only with gcc-3.3 Axel Siebenwirth
2003-04-29 11:35 ` Nicholas Wourms
2003-04-29 11:54 ` James Courtier-Dutton [this message]
2003-04-29 11:51 ` James Courtier-Dutton
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=3EAE67EC.5060702@superbug.demon.co.uk \
--to=james@superbug.demon.co.uk \
--cc=dragon@gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox