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, 22 Jul 2013 14:01:00 +0200	[thread overview]
Message-ID: <51ED1EFC.7070607@gentoo.org> (raw)
In-Reply-To: <CAMWv3tF2=7LWP1yjs2jfY_gBDbByLcJKqnSPGTcnk1NBET5qrA@mail.gmail.com>

On 07/22/2013 09:19 AM, Benda Xu wrote:
> Dear Luca,
> 
> On Tue, Jul 2, 2013 at 12:27 AM, Luca Barbato <lu_zero@gentoo.org> wrote:
> 
>>
>> The patch itself is partially wrong (you might want to use a totally
>> different layout) but surely looks interesting.
>>
> 
> I'd like to revisit this topic. Could you please be a bit more specific on
> where it is partially wrong?
> 
> http://gcc.gnu.org/ml/gcc-patches/2011-01/msg01904.html
> 

You have some flavours, e.g.

+#define GLIBC_DYNAMIC_LINKER32 RUNTIME_ROOT_PREFIX "/lib/ld-linux.so.2"
+#define GLIBC_DYNAMIC_LINKER64 RUNTIME_ROOT_PREFIX
"/lib64/ld-linux-x86-64.so.2"

or

+#define UCLIBC_DYNAMIC_LINKER RUNTIME_ROOT_PREFIX "/lib/ld-uClibc.so.0"
+#define UCLIBC_DYNAMIC_LINKER32 RUNTIME_ROOT_PREFIX "/lib/ld-uClibc.so.0"
+#define UCLIBC_DYNAMIC_LINKER64 RUNTIME_ROOT_PREFIX "/lib/ld64-uClibc.so.0"

And you add some prefix to it.

while the correct patch would just wipe all this cruft and have a

DYNAMIC_LINKER_{32/64/default} and a mean to set it.

Everything is still not exactly great since you could have more than 2
abis per architecture.

As said the patch is surely an improvement over the previous situation
but doesn't help solving the problem fully.

lu




  reply	other threads:[~2013-07-22 12:00 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 [this message]
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=51ED1EFC.7070607@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