From: Luca Barbato <lu_zero@gentoo.org>
To: Jing Huang <jing.huang.pku@gmail.com>
Cc: gentoo-soc@lists.gentoo.org
Subject: Re: [gentoo-soc] cross_container_support - progress report #7
Date: Tue, 10 Jul 2012 16:12:41 +0200 [thread overview]
Message-ID: <4FFC3859.8040702@gentoo.org> (raw)
In-Reply-To: <CAK8mDgrKjP_GUttkoy3_78gZC4=DFMAiGgPyO9nq9L8c6hnR=w@mail.gmail.com>
On 07/10/2012 03:31 PM, Jing Huang wrote:
> First, I try to fix the ping issues in qemu-user of arm-gentoo
> container. The patch is attached.
Try to propose it to the qemu ml.
> * The do_setsockopts function in qemu-user does not support SOL_RAW
> socket which is used in ping program.
>
> * The recvmsg in main_loop of ping_common.c could not fetch
> sockaddr_in struct. That is because do_sendrecvmsg in qemu-user does
> not pass the msg->msg_name to the target.
> So the ping will show "64 bytes from 0.0.0.0: icmp_req=1 ttl=64 time=1.16 ms".
Good investigation =)
> Second, I am investigating how to execute local gcc toolchain in
> arm-gentoo container.
>
> At begging, I want to use ldd to parse each cross-gcc toolchain
> executable in arm container. Then copy the related libraries to
> gentoo-arm rootfs and config the ld.so.conf to make cross-gcc running
> locally.
You could also investigate mount --bind over files, that's how I'm doing
it currently and works up to a point =)
> Now, I think I could modify the crossdev script and build cross-gcc
> with LDFLAGS="-static". So the cross-gcc can be executed locally in
> arm-gentoo container.
Seems an interesting approach as well. Less fun manging with runtime
paths and runtime linkers.
lu
--
Luca Barbato
Gentoo/linux
http://dev.gentoo.org/~lu_zero
prev parent reply other threads:[~2012-07-10 15:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-10 13:31 [gentoo-soc] cross_container_support - progress report #7 Jing Huang
2012-07-10 14:12 ` Luca Barbato [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=4FFC3859.8040702@gentoo.org \
--to=lu_zero@gentoo.org \
--cc=gentoo-soc@lists.gentoo.org \
--cc=jing.huang.pku@gmail.com \
/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