Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Romain Naour <romain.naour@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 1/1] package/glibc: fix include of syscalls.h for RISC-V architecture
Date: Thu, 3 Jan 2019 22:47:18 +0100	[thread overview]
Message-ID: <54bea197-dd49-4590-40bd-a8852a4dbc4c@gmail.com> (raw)
In-Reply-To: <04e0d061-1929-ab39-d29b-865268b41aa9@embecosm.com>

Hi Mark,

Le 03/01/2019 ? 21:16, Mark Corbin a ?crit?:
> Hello
> 
> On 02/01/2019 21:18, Yann E. MORIN wrote:
>> Romain, All,
>>
>> On 2019-01-02 20:51 +0100, Romain Naour spake thusly:
>>> Le 02/01/2019 ? 16:15, Mark Corbin a ?crit?:
>>>> UAPI header file asm/syscalls.h has been merged into the UAPI
>>>> asm/unistd.h header file for the RISC-V architecture in the
>>>> 4.20 kernel. This causes the glibc 2.28 build to break.
>>>>
>>>> This commit applies the upstream glibc patch for this issue.
>>> Can you ask upstream to backport this patch to the glibc 2.28 stable branch?
>>> When it's done you can just bump the glibc version up to the backported patch.
>> Well, we already have another patch that we backported from master, but
>> that upstream has not backported. Sigh...
>>
>> So, even if updating would solve Mark's case, we'd still be missing a
>> fix we'd stil have to carry.
> I managed to persuade the glibc developers to backport both fixes today :-)
> 
> I've just posted a new patch to bump the glibc version accordingly.

Great, thanks!

Best regards,
Romain

> 
> Kind regards
> 
> Mark
> 

      reply	other threads:[~2019-01-03 21:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-02 15:15 [Buildroot] [PATCH v2 1/1] package/glibc: fix include of syscalls.h for RISC-V architecture Mark Corbin
2019-01-02 15:15 ` Mark Corbin
2019-01-02 15:21   ` Mark Corbin
2019-01-02 19:51   ` Romain Naour
2019-01-02 21:18     ` Yann E. MORIN
2019-01-03 20:16       ` Mark Corbin
2019-01-03 21:47         ` Romain Naour [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=54bea197-dd49-4590-40bd-a8852a4dbc4c@gmail.com \
    --to=romain.naour@gmail.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