From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Fiona Klute <fiona.klute@gmx.de>
Cc: James Hilliard <james.hilliard1@gmail.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 0/7] Add package/python-memray and dependencies
Date: Sun, 10 Aug 2025 12:47:36 +0200 [thread overview]
Message-ID: <20250810124736.00b1cc30@windsurf> (raw)
In-Reply-To: <20250809223229.2307960-1-fiona.klute@gmx.de>
Hello Fiona,
On Sun, 10 Aug 2025 00:32:22 +0200
Fiona Klute <fiona.klute@gmx.de> wrote:
> This series adds the Memray memory profiler for Python [1] and its
> dependencies. I needed it to help reduce memory usage of some custom
> tools, and figure it might be useful to others for
> debugging/optimization, too.
>
> The individual patches are fairly simple, just a bunch of new Python
> packages. Memray itself includes a binary module that needs to be
> cross-compiled.
Thanks for the patch series! Since it's mostly made if Python packages,
it would be nice to have some tests in support/testing/ for those
packages, or at least for the "top-level" Memray package.
> One thing I'm not sure about is whether there should be a separate
> option to enable building libdebuginfod in package/elfutils, instead
> of enabling it if the dependencies are met. Having an option would
> allow people who need package/json-c and package/libcurl, but don't
> build anything that links against libdebuginfod to save a few kB (in
> my arm64 build /usr/lib/libdebuginfod-0.192.so is about 38 kB), at the
> price of slightly more complexity in the config system. I'm happy to
> add the option if that's preferred.
In this particular case, I believe I would create an explicit
sub-option. Not because 38 KiB matters, but because it's rather
impossible to "guess" that json-c and libcurl are needed to get
libdebuginfod to be built.
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2025-08-10 11:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-09 22:32 [Buildroot] [PATCH 0/7] Add package/python-memray and dependencies Fiona Klute via buildroot
2025-08-09 22:32 ` [Buildroot] [PATCH 1/7] package/elfutils: enable libdebuginfod for target if requirements are met Fiona Klute via buildroot
2025-08-09 22:32 ` [Buildroot] [PATCH 2/7] package/python-mdurl: new package Fiona Klute via buildroot
2025-08-09 22:32 ` [Buildroot] [PATCH 3/7] package/python-markdown-it-py: " Fiona Klute via buildroot
2025-08-09 22:32 ` [Buildroot] [PATCH 4/7] package/python-platformdirs: " Fiona Klute via buildroot
2025-08-09 22:32 ` [Buildroot] [PATCH 5/7] package/python-rich: " Fiona Klute via buildroot
2025-08-09 22:32 ` [Buildroot] [PATCH 6/7] package/python-textual: " Fiona Klute via buildroot
2025-08-09 22:32 ` [Buildroot] [PATCH 7/7] package/python-memray: " Fiona Klute via buildroot
2025-08-10 10:47 ` Thomas Petazzoni via buildroot [this message]
2025-08-11 10:53 ` [Buildroot] [PATCH 0/7] Add package/python-memray and dependencies Fiona Klute via buildroot
2025-08-11 20:28 ` Thomas Petazzoni via buildroot
2025-08-11 20:52 ` Thomas Petazzoni via buildroot
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=20250810124736.00b1cc30@windsurf \
--to=buildroot@buildroot.org \
--cc=fiona.klute@gmx.de \
--cc=james.hilliard1@gmail.com \
--cc=thomas.petazzoni@bootlin.com \
/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.