From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] toolchain-external: fix lib64 symlinks
Date: Thu, 22 Aug 2013 22:29:53 +0200 [thread overview]
Message-ID: <521674C1.7090304@mind.be> (raw)
In-Reply-To: <CAG2jQ8iVYt=QK9s4sKKzbCsRvp=rA4_BjPSg0DnTQtOobOtn4A@mail.gmail.com>
On 13/08/13 10:37, Markos Chandras wrote:
> Hi Samuel,
>
>> ---
>>
>> This patch needs heavy testing, especially with external non-CodeSourcery
>> toolchains, and maybe with the old CodeSourcery ones.
>>
>> Once again, it raises the question, does 64-bit toolchain need 32-bit
>> stuff?
>
> It does for MIPS/n32. n32 is a 32bit ABI for MIPS64, so a lib32->lib
> symlink is required.
>
>> ---
>> Makefile | 4 ++--
>> toolchain/helpers.mk | 23 ++++++++++++++++++-----
>> toolchain/toolchain-external/ext-tool.mk | 1 -
>> 3 files changed, 20 insertions(+), 8 deletions(-)
>>
>> diff --git a/Makefile b/Makefile
>> index fcfc0be..756d4b1 100644
>> --- a/Makefile
>> +++ b/Makefile
>> @@ -424,8 +424,8 @@ $(BUILD_DIR) $(HOST_DIR) $(BINARIES_DIR) $(STAMP_DIR) $(LEGAL_INFO_DIR) $(REDIST
>>
>> $(STAGING_DIR):
>> @mkdir -p $(STAGING_DIR)/bin
>> - @mkdir -p $(STAGING_DIR)/lib
>> - @mkdir -p $(STAGING_DIR)/usr/lib
>> + @mkdir -p $(STAGING_DIR)/lib$(if $(BR2_ARCH_IS_64),64)
>> + @mkdir -p $(STAGING_DIR)/usr/lib$(if $(BR2_ARCH_IS_64),64)
>
> Again, this should also handle the MIPS64/n32 case where lib32 is
> needed instead of lib or lib64
>
> Thomas suggested to have new symbols like ARCH_NEEDS_LIB32 or
> ARCH_NEEDS_LIB64 selected by architectures that need lib32->lib or
> lib64->lib symlinks respectively.
Can't we just unconditionally make lib64->lib or lib32->lib symlinks?
Or does MIPS64/n32 need both lib32 and lib64?
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
next prev parent reply other threads:[~2013-08-22 20:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-12 20:49 [Buildroot] [PATCH] toolchain-external: fix lib64 symlinks Samuel Martin
2013-08-13 8:37 ` Markos Chandras
2013-08-13 9:32 ` Thomas Petazzoni
2013-08-22 20:29 ` Arnout Vandecappelle [this message]
2013-08-22 20:46 ` Markos Chandras
2013-08-22 22:59 ` [Buildroot] [PATCH v3] " Arnout Vandecappelle
2013-08-23 10:47 ` Markos Chandras
2013-08-27 21:42 ` Peter Korsgaard
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=521674C1.7090304@mind.be \
--to=arnout@mind.be \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.