From: Mario Lang <mlang@blind.guru>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] brltty: fix build on mips64el
Date: Mon, 08 Oct 2018 10:18:08 +0200 [thread overview]
Message-ID: <87bm84g8cf.fsf@home.blind.guru> (raw)
In-Reply-To: <20180930183408.4248-1-fontaine.fabrice@gmail.com> (Fabrice Fontaine's message of "Sun, 30 Sep 2018 20:34:08 +0200")
Hi.
Fabrice Fontaine <fontaine.fabrice@gmail.com> writes:
> Bump to version 5.6 has reintroduced the issue fixed by patch 854093 on
> version 5.5.
>
> Indeed, third patch was merged upstream but it was then reverted:
> https://github.com/brltty/brltty/commit/9e7d62c869d3c1cbe12dda8b0291a4692c193416
>
> Moreover, since commit 3a2e3f6fa5ef0a210ffeba5ed05c79965d0cc3c7, MKOBJ
> was renamed into MKREL. So, instead of patching again brltty, overwrite
> LD to set the correct emulation depending on MIPS architecture as
> already done in linux-tool-perf.mk.in.
Thanks Fabrice. ack and +1.
--
CYa,
?????
next prev parent reply other threads:[~2018-10-08 8:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-30 18:34 [Buildroot] [PATCH 1/1] brltty: fix build on mips64el Fabrice Fontaine
2018-10-08 8:18 ` Mario Lang [this message]
2018-10-08 8:29 ` Fabrice Fontaine
2018-10-08 10:09 ` Mario Lang
2018-10-08 16:07 ` Arnout Vandecappelle
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=87bm84g8cf.fsf@home.blind.guru \
--to=mlang@blind.guru \
--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