All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Gibson <david@gibson.dropbear.id.au>
To: Xi Ruoyao <xry111@xry111.site>
Cc: Rudi Heitbaum <rudi@heitbaum.com>,
	u-boot@lists.denx.de, devicetree-compiler@vger.kernel.org
Subject: Re: [PATCH] libfdt: Fix build with swig 4.3.0
Date: Wed, 30 Oct 2024 12:08:56 +1100	[thread overview]
Message-ID: <ZyGHKJZe4q3ZP5oc@zatzit> (raw)
In-Reply-To: <fc3dcef2676252484cfa427ad0197cd9aa697420.camel@xry111.site>

[-- Attachment #1: Type: text/plain, Size: 2326 bytes --]

On Tue, Oct 29, 2024 at 08:52:52PM +0800, Xi Ruoyao wrote:
> On Sat, 2024-10-26 at 12:34 +0000, Rudi Heitbaum wrote:
> > Call SWIG_AppendOutput instead of SWIG_Python_AppendOutput so that
> > is_void is handled within swig.
> > 
> > Link: https://github.com/swig/swig/commit/cd39cf132c96a0887be07c826b80804d7677a701
> > 
> > Signed-off-by: Rudi Heitbaum <rudi@heitbaum.com>
> 
> Dtc is a separate project at
> https://git.kernel.org/pub/scm/utils/dtc/dtc.git, so the patch should be
> rebased against it and sent to devicetree-compiler@vger.kernel.org.

Looks like someone independently fixed it upstream:
    https://github.com/dgibson/dtc/pull/154

I'm doing final tests now and expect to merge shortly.

> 
> > ---
> >  scripts/dtc/pylibfdt/libfdt.i_shipped | 6 +++---
> >  1 file changed, 3 insertions(+), 3 deletions(-)
> > 
> > diff --git a/scripts/dtc/pylibfdt/libfdt.i_shipped b/scripts/dtc/pylibfdt/libfdt.i_shipped
> > index 56cc5d48f4..e4659489a9 100644
> > --- a/scripts/dtc/pylibfdt/libfdt.i_shipped
> > +++ b/scripts/dtc/pylibfdt/libfdt.i_shipped
> > @@ -1037,7 +1037,7 @@ typedef uint32_t fdt32_t;
> >  			fdt_string(fdt1, fdt32_to_cpu($1->nameoff)));
> >  		buff = PyByteArray_FromStringAndSize(
> >  			(const char *)($1 + 1), fdt32_to_cpu($1->len));
> > -		resultobj = SWIG_Python_AppendOutput(resultobj, buff);
> > +		resultobj = SWIG_AppendOutput(resultobj, buff);
> >  	}
> >  }
> >  
> > @@ -1076,7 +1076,7 @@ typedef uint32_t fdt32_t;
> >  
> >  %typemap(argout) int *depth {
> >          PyObject *val = Py_BuildValue("i", *arg$argnum);
> > -        resultobj = SWIG_Python_AppendOutput(resultobj, val);
> > +        resultobj = SWIG_AppendOutput(resultobj, val);
> >  }
> >  
> >  %apply int *depth { int *depth };
> > @@ -1092,7 +1092,7 @@ typedef uint32_t fdt32_t;
> >             if (PyTuple_GET_SIZE(resultobj) == 0)
> >                resultobj = val;
> >             else
> > -              resultobj = SWIG_Python_AppendOutput(resultobj, val);
> > +              resultobj = SWIG_AppendOutput(resultobj, val);
> >          }
> >  }
> >  
> 

-- 
David Gibson (he or they)	| I'll have my music baroque, and my code
david AT gibson.dropbear.id.au	| minimalist, thank you, not the other way
				| around.
http://www.ozlabs.org/~dgibson

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2024-10-30  1:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-26 12:34 [PATCH] libfdt: Fix build with swig 4.3.0 Rudi Heitbaum
2024-10-29 12:52 ` Xi Ruoyao
2024-10-30  1:08   ` David Gibson [this message]
2024-10-31 12:36     ` Rob Herring
2024-11-06  3:24       ` David Gibson

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=ZyGHKJZe4q3ZP5oc@zatzit \
    --to=david@gibson.dropbear.id.au \
    --cc=devicetree-compiler@vger.kernel.org \
    --cc=rudi@heitbaum.com \
    --cc=u-boot@lists.denx.de \
    --cc=xry111@xry111.site \
    /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.