From: Antoine Martin <antoine@nagafix.co.uk>
To: UML devel <user-mode-linux-devel@lists.sourceforge.net>
Subject: [uml-devel] 2.6.23 linkage error with ipv6 enabled
Date: Wed, 10 Oct 2007 01:10:01 +0100 [thread overview]
Message-ID: <470C1859.5090809@nagafix.co.uk> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
I remember something similar ages ago with another IPv6 symbol no being
pulled in - can't remember how to fix it.
(.text+0x116b9): warning: Using 'getservbyname' in statically linked
applications requires at runtime the shared libraries from the glibc
version used for linking
/usr/lib/gcc/x86_64-pc-linux-gnu/4.1.2/../../../../lib64/libc.a(in6_addr.o):(.rodata+0x0):
multiple definition of `in6addr_any'
net/built-in.o:(.rodata+0x5680): first defined here
collect2: ld returned 1 exit status
KSYM .tmp_kallsyms1.S
nm: '.tmp_vmlinux1': No such file
No valid symbol.
make: *** [.tmp_kallsyms1.S] Error 1
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFHDBhZGK2zHPGK1rsRCpnOAJ9RqsCYLu2z6/5Vv0oxviCimKjy7wCfTaGl
O4jpUIpd9WuqRLwX6zablDI=
=4uon
-----END PGP SIGNATURE-----
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next reply other threads:[~2007-10-10 0:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-10 0:10 Antoine Martin [this message]
2007-10-10 2:00 ` [uml-devel] 2.6.23 linkage error with ipv6 enabled Jeff Dike
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=470C1859.5090809@nagafix.co.uk \
--to=antoine@nagafix.co.uk \
--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