Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: Romain Naour <romain.naour@gmail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v2 01/17] package/python-iptables: fix _find_library()
Date: Fri, 25 Aug 2023 18:11:51 +0200	[thread overview]
Message-ID: <87sf879k54.fsf@48ers.dk> (raw)
In-Reply-To: <20230608232859.1245497-1-romain.naour@gmail.com> (Romain Naour's message of "Fri, 9 Jun 2023 01:28:43 +0200")

>>>>> "Romain" == Romain Naour <romain.naour@gmail.com> writes:

 > While the commit [1] already fixed some runtime issue with
 > uClibc toolchain, the same test TestPythonPy3Iptables fail
 > with Glibc toolchain.

 >   xtables_version = 12
 >   if xtables_version:
 >       _searchlib = "libxtables.so.%s" % (xtables_version,)
 >   else:
 >       _searchlib = "xtables"
 >   _lib_xtables, xtables_version = find_library(_searchlib)

 >   _lib_xtables and xtables_version are null with glibc

 > The implementation of find_library() rely on the custom
 > _find_library() that try to use the IPTABLES_LIBDIR
 > environment variable (that does not exist in the context
 > of Buildroot).

 > Within the scope of buildroot we can determine what
 > IPTABLES_LIBDIR should be at build time and replace the
 > calls to os.environ.get('IPTABLES_LIBDIR', None) with
 > the correct value.

 > [1] d341ec035067120b456f669a826e26eb594c0237

 > Signed-off-by: Romain Naour <romain.naour@gmail.com>
 > ---
 > I don't know why TestPythonPy3Iptables pass succesfully
 > with a uClibc toolchain but not with a glibc toolchain.
 > The current python code searching for xtables, modules
 > and libraries seems fragile...

Committed to 2023.02.x and 2023.05.x, thanks.

-- 
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      parent reply	other threads:[~2023-08-25 16:11 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-08 23:28 [Buildroot] [PATCH v2 01/17] package/python-iptables: fix _find_library() Romain Naour
2023-06-08 23:28 ` [Buildroot] [PATCH v2 02/17] support/testing: TestPythonPy3S3transfer: increase ext2 size to 250M Romain Naour
2023-06-08 23:28 ` [Buildroot] [PATCH v2 03/17] support/testing: TestPythonPy3Boto3: " Romain Naour
2023-06-08 23:28 ` [Buildroot] [PATCH v2 04/17] support/testing: TestPythonPy3Botocore: " Romain Naour
2023-06-08 23:28 ` [Buildroot] [PATCH v2 05/17] support/testing: TestSELinuxSystemd: kernel bump 6.1.26 Romain Naour
2023-06-08 23:28 ` [Buildroot] [PATCH v2 06/17] support/testing/infra/basetest.py: use Bootlin toolchain stable 2022.08-1 Romain Naour
2023-06-08 23:28 ` [Buildroot] [PATCH v2 07/17] support/testing: TestMtools: use base configuration Romain Naour
2023-06-08 23:28 ` [Buildroot] [PATCH v2 08/17] support/testing: TestZ3: " Romain Naour
2023-06-08 23:28 ` [Buildroot] [PATCH v2 09/17] support/testing: Test{No, All, NonDefaultLimited}Timezone: " Romain Naour
2023-06-08 23:28 ` [Buildroot] [PATCH v2 10/17] support/testing: TestPythonPy3SciPy: use python " Romain Naour
2023-06-08 23:28 ` [Buildroot] [PATCH v2 11/17] support/testing: TestPythonPy3Autobahn: " Romain Naour
2023-06-08 23:28 ` [Buildroot] [PATCH v2 12/17] support/testing: TestPythonPy3Crossbar: " Romain Naour
2023-06-08 23:28 ` [Buildroot] [PATCH v2 13/17] support/testing: TestPythonPy3Cryptography: " Romain Naour
2023-06-08 23:28 ` [Buildroot] [PATCH v2 14/17] support/testing: TestPythonPy3MagicWormhole: " Romain Naour
2023-06-08 23:28 ` [Buildroot] [PATCH v2 15/17] support/testing: TestPythonPy3ServiceIdentity: " Romain Naour
2023-06-08 23:28 ` [Buildroot] [PATCH v2 16/17] support/testing: TestPythonPy3Treq: " Romain Naour
2023-06-08 23:28 ` [Buildroot] [PATCH v2 17/17] support/testing: TestPythonPy3Txtorcon: " Romain Naour
2023-07-12 21:24 ` [Buildroot] [PATCH v2 01/17] package/python-iptables: fix _find_library() Thomas Petazzoni via buildroot
2023-08-25 16:11 ` Peter Korsgaard [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=87sf879k54.fsf@48ers.dk \
    --to=peter@korsgaard.com \
    --cc=buildroot@buildroot.org \
    --cc=romain.naour@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox