From: Blaisorblade <blaisorblade@yahoo.it>
To: Antoine Martin <antoine@nagafix.co.uk>
Cc: UML devel <user-mode-linux-devel@lists.sourceforge.net>
Subject: [uml-devel] Re: pcap cross-linking
Date: Mon, 19 Dec 2005 17:16:05 +0100 [thread overview]
Message-ID: <200512191716.06370.blaisorblade@yahoo.it> (raw)
In-Reply-To: <1134932624.10491.76.camel@localhost.localdomain>
On Sunday 18 December 2005 20:03, Antoine Martin wrote:
> 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
This is IMHO a Gentoo bug - it is not setup for compilation of 32-bit binaries
using anything else than glibc. I hit this problem with libncurses, when
doing make menuconfig ARCH=um (now this was solved as helper programs are
built as native again).
However, I built uml with libpcap by default for some time - possibly it was
before me switching to 64-bit linux.
> Fixing the Makefile is beyond me (probably not that hard),
it is a bit hard - in this case it probably suffices to add -L searchpath
(i.e. -L /emul/linux/x86/usr/lib/ ), but it's non-standard (aka only Gentoo
works this way) - and merging fixes for every possible distro is not a good
idea.
> 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).
Don't know what I did suggest, but using strace -e open() (or, even better,
ltrace -e dlopen ) would probably find the point where it's failing and the
failed cmd line.
> 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
Good thing, libnss_* is probably good - but don't forget /etc/nsswitch.conf
and /etc/pam.d/* - /etc/pam.conf
> (also lib/security so I can get into the chroot)
That's for su, right? There are some tools (including "compartment") to
combine chroot + su together.
> But that's not enough... and ldd didn't show me anything missing.
Ldd won't help you with dynamically loaded libraries.
Likely, a recursive "strings object|grep lib" will help - recursive means "do
that also on libraries found this way".
Also, I see you're using SeLinux. I don't know anything about its library
handling, and possibly it's going to make the story more difficult. However,
strace/ltrace as suggested above should diagnose any problem.
--
Inform me of my mistakes, so I can keep imitating Homer Simpson's "Doh!".
Paolo Giarrusso, aka Blaisorblade (Skype ID "PaoloGiarrusso", ICQ 215621894)
http://www.user-mode-linux.org/~blaisorblade
___________________________________
Yahoo! Mail: gratis 1GB per i messaggi e allegati da 10MB
http://mail.yahoo.it
-------------------------------------------------------
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 prev parent reply other threads:[~2005-12-19 16:16 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-18 19:03 [uml-devel] pcap cross-linking Antoine Martin
2005-12-19 16:16 ` Blaisorblade [this message]
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=200512191716.06370.blaisorblade@yahoo.it \
--to=blaisorblade@yahoo.it \
--cc=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