From: "Anthony Brock" <brocka@sterlingcgi.com>
To: UML Developer's List <user-mode-linux-devel@lists.sourceforge.net>
Subject: RE: [uml-devel] Warnings compiling linux-2.6.17-rc5
Date: Mon, 29 May 2006 01:44:40 -0700 [thread overview]
Message-ID: <LEEIJGBJEEABAGOFFGAHKEHGDGAA.brocka@sterlingcgi.com> (raw)
In-Reply-To: <20060529032647.GA4907@ccure.user-mode-linux.org>
> -----Original Message-----
> On Sun, May 28, 2006 at 04:50:33PM -0700, Anthony Brock wrote:
> > WARNING: /mnt/lib/modules/2.6.17-rc5/kernel/net/ipv6/ipv6.ko
> needs unknown
> > symbol strcpy
>
> This is fixed in my current tree.
Before I forget, this warning is still occurring even after applying the
patches mentioned in my previous post. Is there a different tree I should be
patching from? Or is this tree the correct one for testing your patches? Or
does this lag your "current" tree by some time period?
Thanks,
Tony
-------------------------------------------------------
All the advantages of Linux Managed Hosting--Without the Cost and Risk!
Fully trained technicians. The highest number of Red Hat certifications in
the hosting industry. Fanatical Support. Click to learn more
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=107521&bid=248729&dat=121642
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
prev parent reply other threads:[~2006-05-29 8:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-28 23:50 [uml-devel] Warnings compiling linux-2.6.17-rc5 Anthony Brock
2006-05-29 3:26 ` Jeff Dike
2006-05-29 7:17 ` Anthony Brock
2006-05-29 7:47 ` Anthony Brock
2006-05-29 8:28 ` Anthony Brock
2006-05-29 14:57 ` Jeff Dike
2006-05-29 8:44 ` Anthony Brock [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=LEEIJGBJEEABAGOFFGAHKEHGDGAA.brocka@sterlingcgi.com \
--to=brocka@sterlingcgi.com \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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