Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Mikko Rapeli <mikko.rapeli@linaro.org>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH 0/3] swig: update from 4.2.1 to 4.3.0
Date: Thu, 5 Dec 2024 12:11:37 +0200	[thread overview]
Message-ID: <Z1F8WTH18m_fzyxQ@nuoska> (raw)
In-Reply-To: <CA+chaQfkLvTfv5o30LZzuBHJ42Yo_q1MHkg55HJbcZTw+SdqDQ@mail.gmail.com>

Hi,

On Thu, Dec 05, 2024 at 10:43:19AM +0100, Martin Jansa wrote:
> Does this swig upgrade fix the issue with work around added in:
> https://git.openembedded.org/meta-openembedded/commit/?id=f9158ce32fffa6f18eed4008c3295146c81d55ea
> if yes, can you please send revert of this work around to meta-oe?

Unfortunately no. Without f9158ce32fffa6f18eed4008c3295146 in meta-openembedded
python3-m2crypto fails:

| src/SWIG/_m2crypto_wrap.c: In function '_wrap_fd_set___fds_bits_set':
| src/SWIG/_m2crypto_wrap.c:11826:88: error: 'fd_set' has no member named '__fds_bits'; did you mean 'fds_bits'?
| 11826 |       for (; ii < (size_t)1024/(8*(int) sizeof(__fd_mask)); ++ii) *(__fd_mask *)&arg1->__fds_bits[ii] = *((__fd_mask
 *)arg2 + ii);
|       |                                                                                        ^~~~~~~~~~
|       |                                                                                        fds_bits
| src/SWIG/_m2crypto_wrap.c: In function '_wrap_fd_set___fds_bits_get':
| src/SWIG/_m2crypto_wrap.c:11851:48: error: 'fd_set' has no member named '__fds_bits'; did you mean 'fds_bits'?
| 11851 |   result = (__fd_mask *)(__fd_mask *) ((arg1)->__fds_bits);
|       |                                                ^~~~~~~~~~
|       |                                                fds_bits

With workaround f9158ce32fffa6f18eed4008c3295146c build passes.

Cheers,

-Mikko


  reply	other threads:[~2024-12-05 10:11 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-05  9:32 [PATCH 0/3] swig: update from 4.2.1 to 4.3.0 Mikko Rapeli
2024-12-05  9:32 ` [PATCH 1/3] " Mikko Rapeli
2024-12-05  9:32 ` [PATCH 2/3] python3-dtc: update from 1.7.0 to 1.7.2 Mikko Rapeli
2024-12-05  9:32 ` [PATCH 3/3] dtc: " Mikko Rapeli
2024-12-05  9:43 ` [OE-core] [PATCH 0/3] swig: update from 4.2.1 to 4.3.0 Martin Jansa
2024-12-05 10:11   ` Mikko Rapeli [this message]
2024-12-05 10:39     ` Martin Jansa
2024-12-05 15:07 ` Mikko Rapeli
2024-12-05 15:13   ` [OE-core] " Alexander Kanavin
2024-12-05 15:20     ` Mikko Rapeli

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=Z1F8WTH18m_fzyxQ@nuoska \
    --to=mikko.rapeli@linaro.org \
    --cc=martin.jansa@gmail.com \
    --cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox