Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
To: Markus Volk <f_l_k@t-online.de>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [oe-core][PATCH] swig: update 4.2.1 -> 4.3.0
Date: Mon, 28 Oct 2024 15:09:51 +0100	[thread overview]
Message-ID: <Zx-bL-Eir-qb_gE9@bootlin-mathieu> (raw)
In-Reply-To: <20241026070941.309659-1-f_l_k@t-online.de>

On Sat, Oct 26, 2024 at 09:09:41AM +0200, Markus Volk wrote:
> - refresh patch
> 
> SWIG-4.3.0 summary:
> - Add experimental support for C as a target language.
> - MzScheme/Racket is deprecated and planned for removal in SWIG-4.4.
> - The distributed Windows binary is now a 64-bit executable.
> - Add some missing use of move semantics for performance improvements.
> - Enhanced handling of namespaces when using the nspace feature.
> - STL wrapper enhancements for std::unique_ptr, std::string_view,
>   std::filesystem.
> - Various enum and enum class wrapping improvements.
> - Other C++ handling improvements around templates, friends, C++11
>   trailing return types and C++17 fold expressions.
> - Many parser improvements for both C and C++, especially expressions.
> - Improvements to handling of string and character literals.
> - Minor preprocessor fixes.
> - Python: Stricter stable ABI conformance, add support for python-3.13.
> - C#: Add support for converting Doxygen comments into XML C# comments.
> - Various other target language specific enhancements and updates for
>   Java, Javascript, Lua, MzScheme, Ocaml, Octave, Perl, Python, R, Ruby.
> 

Hi,

I suspect this patch is responsible of some failures we observe on the
autobuilder:

/srv/pokybuild/yocto-worker/meta-virt/build/build/tmp/work/x86_64-linux/python3-dtc-native/1.7.0/git/pylibfdt/libfdt_wrap.c:5598:17:
error: too few arguments to function ‘SWIG_Python_AppendOutput’
     resultobj = SWIG_Python_AppendOutput(resultobj, val);

https://valkyrie.yoctoproject.org/#/builders/89/builds/300/steps/16/logs/stdio
https://valkyrie.yoctoproject.org/#/builders/6/builds/328/steps/11/logs/stdio

Can you please have a look at this failure ?

-- 
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
httpse//bootlin.com


  reply	other threads:[~2024-10-28 14:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-26  7:09 [oe-core][PATCH] swig: update 4.2.1 -> 4.3.0 Markus Volk
2024-10-28 14:09 ` Mathieu Dubois-Briand [this message]
2024-10-28 17:37   ` Markus Volk

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=Zx-bL-Eir-qb_gE9@bootlin-mathieu \
    --to=mathieu.dubois-briand@bootlin.com \
    --cc=f_l_k@t-online.de \
    --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