From: Russell Johnson <russell.johnson@kratosdefense.com>
To: Julien Blanc <julien.blanc@sprinte.eu>,
"xenomai@xenomai.org" <xenomai@xenomai.org>
Subject: RE: [External] - Re: <evl/heap.h> compile conflict with Boost
Date: Mon, 13 Jun 2022 21:25:10 +0000 [thread overview]
Message-ID: <PH1P110MB1050262973A8FF3F17B1D6B1E2AB9@PH1P110MB1050.NAMP110.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <e6438951abfa01c114c58b9ab27ff033c4006308.camel@sprinte.eu>
I agree with your proposed fix.
-----Original Message-----
From: Julien Blanc <julien.blanc@sprinte.eu>
Sent: Monday, June 13, 2022 9:17 AM
To: Russell Johnson <russell.johnson@kratosdefense.com>; xenomai@xenomai.org
Subject: [External] - Re: <evl/heap.h> compile conflict with Boost
CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.
Le lundi 13 juin 2022 à 14:39 +0000, Russell Johnson via Xenomai a écrit :
> I use boost throughout my entire app, so I need to figure how to get
> both of these libraries to play nice with each other. Any ideas? ( I
> am using gcc 8.3 and boost 1.70.0)
>
> /opt/evl/include/evl/compiler.h:64:36: error: '__fallthrough__' was
> not declared in this scope
>
> #define fallthrough __attribute__((__fallthrough__))
>
> ^~~~~~~~~~~~~~~
This line looks wrong. The correct way to use the fallthrough attribute (at least with gcc) is __attribute__((fallthrough)) , so that will conflict with any usage (not only boost's).
It should probably be fixed by:
#define __fallthrough __attribute__((fallthrough))
Regards,
Julien
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 6759 bytes
Desc: not available
URL: <http://xenomai.org/pipermail/xenomai/attachments/20220613/a0334209/attachment.bin>
next prev parent reply other threads:[~2022-06-13 21:25 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-13 14:39 <evl/heap.h> compile conflict with Boost Russell Johnson
2022-06-13 15:17 ` Julien Blanc
2022-06-13 21:25 ` Russell Johnson [this message]
2022-06-14 6:54 ` Philippe Gerum
2022-06-14 7:08 ` Julien Blanc
2022-06-14 8:04 ` Philippe Gerum
2022-06-14 8:29 ` Julien Blanc
2022-06-14 8:41 ` Bezdeka, Florian
2022-06-14 9:01 ` Philippe Gerum
2022-06-14 9:44 ` Bezdeka, Florian
2022-06-14 10:34 ` Julien Blanc
2022-06-14 10:43 ` Philippe Gerum
2022-06-14 13:27 ` [External] - " Russell Johnson
2022-06-14 14:05 ` Philippe Gerum
2022-06-14 14:18 Russell Johnson
2022-06-14 15:11 ` Jan Kiszka
2022-06-14 15:22 ` Philippe Gerum
2022-06-14 15:34 ` [External] - " Russell Johnson
2022-06-14 16:06 ` Philippe Gerum
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=PH1P110MB1050262973A8FF3F17B1D6B1E2AB9@PH1P110MB1050.NAMP110.PROD.OUTLOOK.COM \
--to=russell.johnson@kratosdefense.com \
--cc=julien.blanc@sprinte.eu \
--cc=xenomai@xenomai.org \
/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.