From: Michael Jeanson via lttng-dev <lttng-dev@lists.lttng.org>
To: Elad Lahav <e2lahav@gmail.com>
Cc: lttng-dev@lists.lttng.org
Subject: Re: [lttng-dev] Change to CPU number detection breaks QNX compilation
Date: Mon, 15 Aug 2022 11:55:48 -0400 [thread overview]
Message-ID: <7e3f4047-101e-d8d4-93ed-370c8eaf7494@efficios.com> (raw)
In-Reply-To: <CAJbg=FWjjBT1RbGxvCcx1+6qgJfhqtF3h3WpLB11cGSb1Efzqw@mail.gmail.com>
On 2022-08-15 10 h 04, Elad Lahav wrote:
> The problem is the use of d_type as a member of the dirent structure.
> POSIX does not define such a member.
> I can provide the necessary code for getting the file type in a
> readdir() loop on QNX, but it seems unnecessary given that there is no
> /sys file system with CPU information. The method for getting
> information on processors is different, and I suspect that is true for
> *BSDs and other non-Linux OSs.
>
> --Elad
Can you try this patch [1] to see if it fixes the build on QNX? Can you
also run 'make check' in 'tests/unit', the linux specific tests should
be skipped.
Michael
[1] https://review.lttng.org/c/userspace-rcu/+/8664
_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
next prev parent reply other threads:[~2022-08-15 15:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-13 23:10 Elad Lahav via lttng-dev
2022-08-15 13:53 ` Michael Jeanson via lttng-dev
[not found] ` <CAJbg=FWjjBT1RbGxvCcx1+6qgJfhqtF3h3WpLB11cGSb1Efzqw@mail.gmail.com>
2022-08-15 15:55 ` Michael Jeanson via lttng-dev [this message]
2022-08-15 16:56 ` Elad Lahav via lttng-dev
2022-08-15 17:39 ` Michael Jeanson via lttng-dev
2022-08-15 17:52 ` Elad Lahav via lttng-dev
2022-08-16 15:20 ` Michael Jeanson via lttng-dev
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=7e3f4047-101e-d8d4-93ed-370c8eaf7494@efficios.com \
--to=lttng-dev@lists.lttng.org \
--cc=e2lahav@gmail.com \
--cc=mjeanson@efficios.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox