From: Antoine Martin <antoine@nagafix.co.uk>
To: UML devel <user-mode-linux-devel@lists.sourceforge.net>,
Blaisorblade <blaisorblade@yahoo.it>
Subject: [uml-devel] pcap cross-linking
Date: Sun, 18 Dec 2005 19:03:43 +0000 [thread overview]
Message-ID: <1134932624.10491.76.camel@localhost.localdomain> (raw)
Paolo,
pcap builds and runs fine on amd64 but there is a problem when building
with SUBARCH=i386: it uses the wrong version of libpcap.a:
ld -r -dp -o arch/um/drivers/pcap.o arch/um/drivers/pcap_kern.o
arch/um/drivers/pcap_user.o -m elf_i386
-r /usr/lib/gcc/x86_64-pc-linux-gnu/3.4.4/../../../libpcap.a
Whereas the one it needs to link against is here:
/emul/linux/x86/usr/lib/libpcap.a
Fixing the Makefile is beyond me (probably not that hard), sorry - so I
link it manually. After that it works perfectly.
On the subject of pcap transport, I couldn't dig the email where you
suggested a way of figuring out which libraries should be placed in the
chroot, I tried to use the same libraries as I used on a 32-bit setup
but it fails to bring up the interface (when it works outside chroot).
I tried to guess and even added a few more, here is the chroot's /lib (I
made /lib64 a link to /lib in chroot):
ld-2.3.5.so libcrack.so.2.8.0 libm.so.6
libnss_compat-2.3.5.so libnss_hesiod-2.3.5.so libpam.so
libpamc.so libpcap.so.0.9 librt.so.1 security
ld-linux-x86-64.so.2 libcrypt-2.3.5.so libncurses.so
libnss_compat.so.2 libnss_hesiod.so.2 libpam.so.0
libpamc.so.0 libpthread-0.10.so libselinux.so.1 tls
libc-2.3.5.so libcrypt.so.1 libncurses.so.5
libnss_dns-2.3.5.so libnss_nis-2.3.5.so libpam.so.0.78
libpamc.so.0.78 libpthread.so.0 libsemanage.so.1
libc.so.6 libdl-2.3.5.so libncurses.so.5.4
libnss_dns.so.2 libnss_nis.so.2 libpam_misc.so
libpcap.a libresolv-2.3.5.so libsepol.so.1
libcrack.so libdl.so.2 libnsl-2.3.5.so
libnss_files-2.3.5.so libnss_nisplus-2.3.5.so libpam_misc.so.0
libpcap.so libresolv.so.2 libutil-2.3.5.so
libcrack.so.2 libm-2.3.5.so libnsl.so.1
libnss_files.so.2 libnss_nisplus.so.2 libpam_misc.so.0.78
libpcap.so.0 librt-2.3.5.so libutil.so.1
lib/tls:
libc-2.3.5.so libc.so.6
(also lib/security so I can get into the chroot)
But that's not enough... and ldd didn't show me anything missing.
Any ideas?
Thanks
Antoine
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
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:[~2005-12-18 19:04 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-18 19:03 Antoine Martin [this message]
2005-12-19 16:16 ` [uml-devel] Re: pcap cross-linking Blaisorblade
2005-12-19 18:33 ` [uml-devel] Re: pcap cross-linking [PATCH] Antoine Martin
2005-12-19 19:27 ` Blaisorblade
2005-12-19 21:47 ` Antoine Martin
2005-12-20 14:23 ` Blaisorblade
2005-12-20 16:25 ` Antoine Martin
2005-12-20 19:24 ` Blaisorblade
2005-12-20 20:01 ` Rob Landley
2005-12-20 20:24 ` Antoine Martin
2005-12-20 20:43 ` Blaisorblade
2005-12-21 18:13 ` Blaisorblade
2005-12-22 17:57 ` Anthony Brock
2005-12-23 16:11 ` Blaisorblade
2005-12-26 7:47 ` Anthony Brock
2005-12-29 20:12 ` Rob Landley
2006-01-01 18:51 ` Blaisorblade
2006-01-01 21:01 ` Rob Landley
2006-01-02 20:10 ` Blaisorblade
2005-12-19 18:39 ` [uml-devel] Re: pcap cross-linking Blaisorblade
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=1134932624.10491.76.camel@localhost.localdomain \
--to=antoine@nagafix.co.uk \
--cc=blaisorblade@yahoo.it \
--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