From: Greg KH <greg@kroah.com>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: 2.6.25-git16 fails with "undefined reference to `compat_mc_getsockopt'"
Date: Wed, 30 Apr 2008 15:03:15 -0700 [thread overview]
Message-ID: <20080430220315.GA11136@kroah.com> (raw)
In-Reply-To: <20080430.144906.105396672.davem@davemloft.net>
On Wed, Apr 30, 2008 at 02:49:06PM -0700, David Miller wrote:
> From: Greg KH <greg@kroah.com>
> Date: Wed, 30 Apr 2008 13:46:22 -0700
>
> > Don't know if you have seen this or not, but 2.6.25-gi16 seems to fail
> > with:
> > net/built-in.o: In function `ipv6_getsockopt':
> > (.text+0x6829c): undefined reference to `compat_mc_getsockopt'
> >
> > I've attached my .config below if that helps any.
>
> Known problem and there is a fix pending, sit tight.
Great, thanks for letting me know and sending the patch to Linus, I
appreciate it.
greg k-h
prev parent reply other threads:[~2008-04-30 22:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-30 20:46 2.6.25-git16 fails with "undefined reference to `compat_mc_getsockopt'" Greg KH
2008-04-30 21:11 ` Oliver Hartkopp
2008-04-30 21:49 ` David Miller
2008-04-30 22:03 ` Greg KH [this message]
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=20080430220315.GA11136@kroah.com \
--to=greg@kroah.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).