Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] strace on xtensa/uclibc
Date: Tue, 11 Dec 2018 13:50:24 +0100	[thread overview]
Message-ID: <20181211135024.3e80c5db@windsurf> (raw)
In-Reply-To: <20181207091356.605a9c69@windsurf>

Hello,

Waldemar, Max, any input on the below issue ?

Thanks,

Thomas

On Fri, 7 Dec 2018 09:13:56 +0100, Thomas Petazzoni wrote:
> Hello,
> 
> +Baruch, Max Filipov for Xtensa and Waldemar for uClibc-ng.
> 
> On Fri,  7 Dec 2018 08:00:29 +0100 (CET), Thomas Petazzoni wrote:
> 
> >       xtensa |                    strace-4.25 | NOK | http://autobuild.buildroot.net/results/5a0112b7a2c81fa5253c9adc93efe415256cd811 |       
> 
> I had a look at those failures of strace on xtensa:
> 
>   http://autobuild.buildroot.net/?reason=strace-4.25
> 
> I.e, strace 4.25 only fails to build on Xtensa. The reason is that
> uClibc-ng doesn't have the correct values for some POLL* macros: they
> don't match the kernel values.
> 
> Let's take POLLWRBAND as an example. The kernel defines it like this:
> 
> arch/xtensa/include/uapi/asm/poll.h:#define POLLWRBAND  0x0100
> 
> So strace 4.25 checks that it has the correct value:
> 
> #if defined(__m68k__) || defined(__mips__) || defined(__sparc__) || defined(__xtensa__)
> #if defined(POLLWRBAND) || (defined(HAVE_DECL_POLLWRBAND) && HAVE_DECL_POLLWRBAND)
> DIAG_PUSH_IGNORE_TAUTOLOGICAL_COMPARE
> static_assert((POLLWRBAND) == (0x0100), "POLLWRBAND != 0x0100");
> 
> But uClibc-ng doesn't have an arch-specific header to define POLLWRBAND
> on xtensa, so it falls back to the generic definition, which isn't
> correct for xtensa:
> 
> libc/sysdeps/linux/common/bits/poll.h:# define POLLWRBAND       0x200           /* Priority data may be written.  */
> 
> The same issue happens with POLLREMOVE.
> 
> I think xtensa needs to have its own
> libc/sysdeps/linux/xtensa/bits/poll.h in uClibc-ng.
> 
> Best regards,
> 
> Thomas



-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2018-12-11 12:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-07  7:00 [Buildroot] [autobuild.buildroot.net] Build results for 2018-12-06 Thomas Petazzoni
2018-12-07  8:13 ` [Buildroot] strace on xtensa/uclibc Thomas Petazzoni
2018-12-11 12:50   ` Thomas Petazzoni [this message]
2018-12-12 15:27     ` Max Filippov
2018-12-12 15:30       ` Thomas Petazzoni

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=20181211135024.3e80c5db@windsurf \
    --to=thomas.petazzoni@bootlin.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