From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] Makefile: Symlink lib32 to lib for MIPS64/n32
Date: Fri, 12 Jul 2013 10:10:57 +0200 [thread overview]
Message-ID: <20130712101057.35cf1751@skate> (raw)
In-Reply-To: <CAAXf6LUxijfeiv7mrMKNbq64nOXDgzTfY7d0Ri7Kp=LSTG=7nw@mail.gmail.com>
Dear Thomas De Schampheleire,
On Thu, 11 Jul 2013 16:19:31 +0200, Thomas De Schampheleire wrote:
> It's not even uClibc-specific, same holds for glibc-based toolchains.
> From gcc/config/mips/linux64.h:
>
> #define GLIBC_DYNAMIC_LINKER32 "/lib/ld.so.1"
> #define GLIBC_DYNAMIC_LINKER64 "/lib64/ld.so.1"
> #define GLIBC_DYNAMIC_LINKERN32 "/lib32/ld.so.1"
> #define UCLIBC_DYNAMIC_LINKERN32 "/lib32/ld-uClibc.so.0"
Ok, I was mistaken by http://patchwork.ozlabs.org/patch/256596/. But
this patch is the one that makes uClibc actually match the program
interpreter path with the one used by gcc. So yeah, those symbolic
links are also needed.
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2013-07-12 8:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-03 13:06 [Buildroot] [PATCH v2] Makefile: Symlink lib32 to lib for MIPS64/n32 Markos Chandras
2013-07-09 10:26 ` Markos Chandras
2013-07-11 9:24 ` Thomas De Schampheleire
2013-07-11 10:59 ` Thomas Petazzoni
2013-07-11 11:08 ` Markos Chandras
2013-07-11 11:18 ` Thomas De Schampheleire
2013-07-11 11:22 ` Markos Chandras
2013-07-11 13:40 ` Thomas Petazzoni
2013-07-11 14:00 ` Markos Chandras
2013-07-11 14:07 ` Thomas Petazzoni
2013-07-11 14:30 ` Markos Chandras
2013-07-11 14:19 ` Thomas De Schampheleire
2013-07-11 14:31 ` Markos Chandras
2013-07-12 8:10 ` Thomas Petazzoni [this message]
2013-07-14 22:07 ` Markos Chandras
2013-07-20 10:27 ` Markos Chandras
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=20130712101057.35cf1751@skate \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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