public inbox for gentoo-soc@lists.gentoo.org
 help / color / mirror / Atom feed
From: Luca Barbato <lu_zero@gentoo.org>
To: gentoo-soc@lists.gentoo.org
Subject: Re: [gentoo-soc] Gentoo on Android, Summary for 2013.6.28-7.1
Date: Mon, 01 Jul 2013 16:59:38 +0200	[thread overview]
Message-ID: <51D1995A.8050707@gentoo.org> (raw)
In-Reply-To: <87mwq6mj4v.fsf@proton.in.awa.tohoku.ac.jp>

On 07/01/2013 04:48 PM, heroxbd wrote:
> Dear Guys and Gals,
> 
> Gentoo on Android is about running Gentoo natively in a directory prefix
> on Android devices[1] in parallel with native Android, mentored by Luca.
> 
> Progress report for the past 3 days,
> 
>      1. gcc specs hack is not that interesting as it first looks.
>         - parsing or generating specs script is no fun.
>           The best parser/generator is gcc itself
>         - appending simple specs (suches -dynamic-linker=/xx/xx.so) feel
>           not clever, appending --with-spec to configure either.
> 
>         Therefore, I decide not to use specs hack as the main building
>         block. At the same time, it can be handy to do manual tuning
>         with it.

That must be reconsidered later to understand what's the problem and if
upstream can help on that.

>         Relying on binutils wrapper is no good either. The solution
>         finally falls on a mixed one between sysroot and native paths
>         methods (ref. table in [2]). Where I make use of eprefixify of
>         prefix.eclass to modify location of dynamic linker for *run
>         time* and sysroot for *compile time*.

It isn't perfect, but as long it gives result I can live with that.

>      2. Prefix/libc armhf works rock solid. It is now being "emerge -e
>         @world" with the help of many distcc cross compilers. I have to
>         leave my cell phone home for a constant power supply and
>         ethernet connection (yes! USB ethernet adapter) though.

Make sure it is near a heatsink (AC or such).

>         The bug is related to VDSO. A full description of the problem is
>         on stackoverflow[3]. I'd be very appreciated for any hints.

uclibc or musl might or might not help?

lu



  reply	other threads:[~2013-07-01 14:59 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-01 14:48 [gentoo-soc] Gentoo on Android, Summary for 2013.6.28-7.1 heroxbd
2013-07-01 14:59 ` Luca Barbato [this message]
2013-07-01 15:18   ` heroxbd
2013-07-01 15:27     ` Luca Barbato
2013-07-22  7:19       ` Benda Xu
2013-07-22 12:01         ` Luca Barbato
2013-07-22 12:24           ` heroxbd
2013-07-22 12:32             ` Luca Barbato
2013-08-18 12:16               ` heroxbd
2013-08-18 12:29                 ` Luca Barbato
2013-08-18 13:17                   ` heroxbd

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=51D1995A.8050707@gentoo.org \
    --to=lu_zero@gentoo.org \
    --cc=gentoo-soc@lists.gentoo.org \
    /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