public inbox for gentoo-soc@lists.gentoo.org
 help / color / mirror / Atom feed
From: heroxbd <heroxbd@gmail.com>
To: gentoo-soc@lists.gentoo.org
Cc: redlizard@redlizard.nl, abcd@gentoo.org
Subject: [gentoo-soc] Gentoo on Android, Summary for 2013.6.28-7.1
Date: Mon, 01 Jul 2013 23:48:00 +0900	[thread overview]
Message-ID: <87mwq6mj4v.fsf@proton.in.awa.tohoku.ac.jp> (raw)

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

     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.

     3. A problem on RHEL 5.6 made me question how far could I go with
        ancient GNU/Linux environments. 

        gcc bootstrap fails horribly in stage2

,----
| /dev/shm/portage/sys-devel/gcc-4.7.2-r1/work/build/gcc $ ./cc1
| cc1: internal compiler error: Segmentation fault
| Please submit a full bug report,
| with preprocessed source if appropriate.
| See <http://bugs.gentoo.org/> for instructions.
`----

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

So much for today. Cheers!
Benda

1. http://www.awa.tohoku.ac.jp/~benda/projects/android.html
2. http://wiki.gentoo.org/wiki/Prefix/libc
3. http://stackoverflow.com/questions/17406389/is-it-possible-to-turn-off-vdso-on-glibc-side


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

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-01 14:48 heroxbd [this message]
2013-07-01 14:59 ` [gentoo-soc] Gentoo on Android, Summary for 2013.6.28-7.1 Luca Barbato
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=87mwq6mj4v.fsf@proton.in.awa.tohoku.ac.jp \
    --to=heroxbd@gmail.com \
    --cc=abcd@gentoo.org \
    --cc=gentoo-soc@lists.gentoo.org \
    --cc=redlizard@redlizard.nl \
    /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