public inbox for gentoo-soc@lists.gentoo.org
 help / color / mirror / Atom feed
From: heroxbd <heroxbd@gmail.com>
To: gentoo-soc@lists.gentoo.org
Subject: Re: [gentoo-soc] Gentoo on Android, Summary for 2013.6.28-7.1
Date: Sun, 18 Aug 2013 22:17:09 +0900	[thread overview]
Message-ID: <87li3zyw8a.fsf@proton.in.awa.tohoku.ac.jp> (raw)
In-Reply-To: <5210BE2C.3010407@gentoo.org> (Luca Barbato's message of "Sun, 18 Aug 2013 14:29:32 +0200")

Luca Barbato <lu_zero@gentoo.org> writes:

>> 
>> econf --with-extra-specs='{ "dynamic-linker", "/opt/gentoo/lib/ld-linux.so.2" }'
>> 
>> However, GNU autoconf/automake system automatically quote this to
>> a string, while we want to pass an array of structures.
>
> There is an unquote macro and you can always use eval to expand once.

Ah, I see. 

>> Another solution is to prepend sysroot to dynamic linker, which is
>> indifferent to the runtime-prefix patch from Google, criticized by you
>> earlier.
>
> The Google patch is a step in a direction, just you could just unify
> first and make it prefix-variable later 

Not sure if I understood your words. It is nearly impossible to
prefixify the directories afterwards, as they are conditioned by
-m32/-m64/-mx32, etc.

> instead of adding a prefix to all the custom patches scattered in the
> codebase as it is now.


>> Up to this point, the solution becomes complex and artificial. I
>> would rather use the present patch'n'prefixify method, as we used
>> in many ebuild, like:
>> 
>> --- gcc/config/i386/linux.h     2011-06-04 03:30:39.000000000 +0900
>> +++ gcc/config/i386/linux.h.new 2013-07-16 19:55:09.610399047 +0900
>> @@ -21,4 +21,4 @@ along with GCC; see the file COPYING3.
>>  <http://www.gnu.org/licenses/>.  */
>>  
>>  #define GNU_USER_LINK_EMULATION "elf_i386"
>> -#define GLIBC_DYNAMIC_LINKER "/lib/ld-linux.so.2"
>> +#define GLIBC_DYNAMIC_LINKER "@GENTOO_PORTAGE_EPREFIX@/lib/ld-linux.so.2"
>
> So first you patch the paths with something you can sed fill later.

Yes.

> Works for me to get a result now. Then we can pester upstream 

Exactly, http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52556

> or just consider switching to clang (a different kind of pain to
> bootstrap).

ok, I'll get my hands dirty with it.



      reply	other threads:[~2013-08-18 13:19 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
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 [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=87li3zyw8a.fsf@proton.in.awa.tohoku.ac.jp \
    --to=heroxbd@gmail.com \
    --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