linux-um archives
 help / color / mirror / Atom feed
From: Blaisorblade <blaisorblade@yahoo.it>
To: user-mode-linux-devel@lists.sourceforge.net
Cc: Antoine Martin <antoine@nagafix.co.uk>
Subject: Re: [uml-devel] Re: pcap cross-linking
Date: Mon, 19 Dec 2005 19:39:21 +0100	[thread overview]
Message-ID: <200512191939.22249.blaisorblade@yahoo.it> (raw)
In-Reply-To: <200512191716.06370.blaisorblade@yahoo.it>

On Monday 19 December 2005 17:16, Blaisorblade wrote:
> 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.

No, the thing works but only because I indeed symlinked 32-bit libraries 
inside /usr/lib32.
-- 
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! Messenger: chiamate gratuite in tutto il mondo 
http://it.messenger.yahoo.com



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

      parent reply	other threads:[~2005-12-19 18:39 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 ` [uml-devel] " 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   ` Blaisorblade [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=200512191939.22249.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