From: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] toolchain-external: fix getent installation with Codescape MIPS toolchains
Date: Tue, 29 Mar 2016 12:24:45 +0100 [thread overview]
Message-ID: <56FA65FD.7040704@imgtec.com> (raw)
In-Reply-To: <1459172255-24556-1-git-send-email-thomas.petazzoni@free-electrons.com>
Dear Thomas Petazzoni,
On 28/03/16 14:37, Thomas Petazzoni wrote:
> When a toolchain is glibc based, the getent package assumes that
> $(STAGING_DIR)/usr/bin contains the getent program. Unfortunately, the
> Codescape MIPS toolchains do not conform with this:
> $(STAGING_DIR)/usr/{bin,sbin} are empty, and instead three directories
> are provided: bin-o32, bin-n32 and bin-n64 (ditto for sbin), one for
> each supported MIPS ABI.
>
> Since this is a toolchain-specific oddity, we handle it by adding a
> post-install fixup hook that creates $(STAGING_DIR)/usr/{bin,sbin} as
> symbolic link to the appropriate directory.
>
> Fixes:
>
> http://autobuild.buildroot.org/results/9c0ee836021553319f166f9de88750535aee0a58/
>
> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Reviewed-by: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
Tested-by: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
Regards,
Vincent.
prev parent reply other threads:[~2016-03-29 11:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-28 13:37 [Buildroot] [PATCH] toolchain-external: fix getent installation with Codescape MIPS toolchains Thomas Petazzoni
2016-03-29 11:24 ` Vicente Olivert Riera [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=56FA65FD.7040704@imgtec.com \
--to=vincent.riera@imgtec.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