Matthias, I've added the --embed flag to the python3.9-config options in my Dockerfile example above, but have the same result. Apparently the specs file comes from libdpkg-perl. I don't understand what the specs file actually does, but I was able to build with or without it. If it *is* supposed to be in the flags for something, libdpkg-perl should at least be a "suggests" if not "recommends", right?
On Mon, Aug 23, 2021 at 5:09 AM Matthias Klose <d...@debian.org> wrote: > > On 8/22/21 5:59 AM, Mark Watts wrote: > > Package: python3.9-dev > > Version: 3.9.2-1 > > Severity: normal > > X-Debbugs-Cc: watts.mark2...@gmail.com > > > > Dear Maintainer, > > > > I'm using the python3.9-config --cflags to provide flags for building a > > program that embeds python. I'm doing this in a Docker container with > > the essential parts described by the Dockerfile excerpt below. I would > > expect that any files referenced in the CFLAGS would be installed along > > with python3.9-config. Instead, I have to install another package to get > > this file or do a sed on cflags to remove the -specs argument. > > your expectations are unexpected. You have to call python3-config with the > --embed options for the embedded case. That will get you the complete options > needed for embedding an interpreter. I'm not sure I want to have these extra > dependencies as part of the python3.9-dev package. > > You also don't write which options are missing from your build. -- Cheers, Mark W.
