public inbox for linux-i2c@vger.kernel.org
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Rob Herring <robh@kernel.org>
Cc: linux-renesas-soc@vger.kernel.org, linux-i2c@vger.kernel.org,
	devicetree-spec@vger.kernel.org
Subject: Re: [PATCH dt-schema 0/3] schemas: i2c: fix "smbus_alert" handling
Date: Thu, 15 Aug 2024 23:23:15 +0200	[thread overview]
Message-ID: <Zr5xw9-dY0dXfIGt@shikoro> (raw)
In-Reply-To: <CAL_Jsq+n96kzS9gpNb23d698pi0M1unfOpi1YvSGzDB+7VrENw@mail.gmail.com>

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


> >   × Building wheel for pylibfdt (pyproject.toml) did not run successfully.
> >   │ exit code: 1
> >   ╰─> [14 lines of output]
> >       WARNING setuptools_scm.pyproject_reading toml section missing 'pyproject.toml does not contain a tool.setuptools_scm section'

Thanks for bearing with me. I have to admit I stopped reading after
this...

> >       Traceback (most recent call last):
> >         File "/tmp/pip-build-env-5v1x378l/normal/lib/python3.11/site-packages/setuptools_scm/_integration/pyproject_reading.py", line 36, in read_pyproject
> >           section = defn.get("tool", {})[tool_name]
> >                     ~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^

... and this ...

> >       KeyError: 'setuptools_scm'
> >       running bdist_wheel
> >       running build
> >       running build_py
> >       running build_ext
> >       building '_libfdt' extension
> >       swigging libfdt/libfdt.i to libfdt/libfdt_wrap.c
> >       swig -python -Ilibfdt -o libfdt/libfdt_wrap.c libfdt/libfdt.i
> >       error: command 'swig' failed: No such file or directory

... so I totally missed this. It is even documented in README. Sorry!

> You have to install 'swig' which is a C to python binding thing
> pylibfdt uses. You should have a distro package for it. There's also a

It works now, thank you!

> pip package 'swig' that will download and build it. There's actually a
> MR to make that a dependency I need to go look at.

Sounds like a good idea to save you from support like here ;)

I will send out v2 in a few minutes.


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

      reply	other threads:[~2024-08-15 21:23 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-15 12:09 [PATCH dt-schema 0/3] schemas: i2c: fix "smbus_alert" handling Wolfram Sang
2024-08-15 12:09 ` [PATCH dt-schema 1/3] schemas: i2c: reword descriptions for inclusive language Wolfram Sang
2024-08-15 12:09 ` [PATCH dt-schema 2/3] schemas: i2c: clean up interrupt descriptions for I2C targets Wolfram Sang
2024-08-15 12:09 ` [PATCH dt-schema 3/3] schemas: i2c: add generic interrupt name for I2C controllers Wolfram Sang
2024-08-15 14:54   ` Rob Herring
2024-08-15 18:42     ` Wolfram Sang
2024-08-15 20:39       ` Rob Herring
2024-08-15 14:46 ` [PATCH dt-schema 0/3] schemas: i2c: fix "smbus_alert" handling Rob Herring
2024-08-15 18:36   ` Wolfram Sang
2024-08-15 20:36     ` Rob Herring
2024-08-15 21:23       ` Wolfram Sang [this message]

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=Zr5xw9-dY0dXfIGt@shikoro \
    --to=wsa+renesas@sang-engineering.com \
    --cc=devicetree-spec@vger.kernel.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=robh@kernel.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