linux-um archives
 help / color / mirror / Atom feed
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 00:17:11 -0700	[thread overview]
Message-ID: <LEEIJGBJEEABAGOFFGAHMEHEDGAA.brocka@sterlingcgi.com> (raw)
In-Reply-To: <20060529032647.GA4907@ccure.user-mode-linux.org>

> On Sun, May 28, 2006 at 04:50:33PM -0700, Anthony Brock wrote:
> > I just tried to compile a new guest kernel using the
> linux-2.6.17-rc5 kernel
> > source and encountered the following warnings.
> > WARNING: vmlinux - Section mismatch: reference to
> .init.setup:__setup_nosmp
> > from .bss between 'stderr@@GLIBC_2.0' (at offset 0x82607c4) and
> > 'completed.4463'
>
> These I have no clue about.  I've seen them with a native build, so
> they appear not to be UML-specific.  Looks like a broken linker.  The
> resulting UML works fine, so this is nasty-looking, but non-fatal.

Good. I'll ignore them.

> > WARNING: /mnt/lib/modules/2.6.17-rc5/kernel/net/ipv6/ipv6.ko
> needs unknown
> > symbol strcpy
>
> This is fixed in my current tree.

I actually looked through these patches before asking:

http://user-mode-linux.sourceforge.net/work/current/2.6/2.6.17-rc4/patches.t
ar

I didn't see anything that appeared to address this. However, I'll try
applying these and test from there.

Thanks!

Tony

BTW, this compile was run on Debian Testing (Etch):


# gcc -v
Using built-in specs.
Target: i486-linux-gnu
Configured with:
../src/configure -v --enable-languages=c,c++,java,f95,objc,ada,treelang --pr
efix=/usr --enable-shared --with-system-zlib --libexecdir=/usr/lib --without
-included-gettext --enable-threads=posix --enable-nls --program-suffix=-4.0 
--enable-__cxa_atexit --enable-clocale=gnu --enable-libstdcxx-debug --enable
-java-awt=gtk-default --enable-gtk-cairo --with-java-home=/usr/lib/jvm/java-
1.4.2-gcj-4.0-1.4.2.0/jre --enable-mpfr --disable-werror --with-tune=i686 --
enable-checking=release i486-linux-gnu
Thread model: posix
gcc version 4.0.4 20060507 (prerelease) (Debian 4.0.3-3)
# ld -V
GNU ld version 2.16.91 20060413 Debian GNU/Linux
  Supported emulations:
   elf_i386
   i386linux
   elf_x86_64



-------------------------------------------------------
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

  reply	other threads:[~2006-05-29  7:17 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 [this message]
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

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=LEEIJGBJEEABAGOFFGAHMEHEDGAA.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