All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Khem Raj <raj.khem@gmail.com>
Cc: openembeded-devel <openembedded-devel@lists.openembedded.org>
Subject: Re: [meta-oe][PATCH] ltrace: Fix build on mips
Date: Sun, 8 Sep 2019 16:08:38 +0300	[thread overview]
Message-ID: <20190908130838.GA17080@localhost> (raw)
In-Reply-To: <CAMKF1soYXXaF6GacgUJn0HQyYDgiY_QShxbN3RB6z0OWS2xgTg@mail.gmail.com>

On Sat, Sep 07, 2019 at 07:36:04AM -0700, Khem Raj wrote:
> On Sat, Sep 7, 2019 at 3:21 AM Adrian Bunk <bunk@stusta.de> wrote:
> >
> > On Fri, Sep 06, 2019 at 05:12:24PM -0700, akuster808 wrote:
> > > On 9/6/19 2:25 PM, Khem Raj wrote:
> > > > Newer kernel UAPI headers for mips have moved these needed defines
> > > > around
> > > >
> > > > Signed-off-by: Khem Raj <raj.khem@gmail.com>
> > >
> > > warrior too?
> > >...
> >
> > No, this is not a problem with the UAPI headers in warrior.
> 
> anything that's using kernel 5.0+ UAPI headers has this problem and
> warrior is using 5.0
> for linux-libc headers. see [1]
> 
> [1] https://github.com/torvalds/linux/commit/9bcbf97c62931f27ab2c52f0848dec0cd48aee78

Thanks for correcting me, I was looking at the wrong commit.

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed



      reply	other threads:[~2019-09-08 13:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-06 21:25 [meta-oe][PATCH] ltrace: Fix build on mips Khem Raj
2019-09-07  0:12 ` akuster808
2019-09-07  0:17   ` Khem Raj
2019-09-07 10:21   ` Adrian Bunk
2019-09-07 14:36     ` Khem Raj
2019-09-08 13:08       ` Adrian Bunk [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=20190908130838.GA17080@localhost \
    --to=bunk@stusta.de \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=raj.khem@gmail.com \
    /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.