- Original Message -
> Hello everyone,
>
> As of Python 3.8, python C extensions modules should not link to libpython,
> unless they embed the interpreter in their code. Relevant upstream PR:
> https://github.com/python/cpython/pull/12946
> If your package links to libpython without requ
On Wed, Jun 03, 2020 at 03:56:03PM +0200, Petr Viktorin wrote:
>
> Judging from the file name, mem_alloc.cpython-38-x86_64-linux-gnu.so is a
> Python module. If that's so, you shouldn't link it using gcc, but use a
> Python import statement to load it.
> Is there some reason to link it using gcc?
On 2020-05-31 10:24, Honggang LI wrote:
On Fri, May 29, 2020 at 06:47:35PM +0200, Petr Viktorin wrote:
On 2020-05-18 03:53, Honggang LI wrote:
On Fri, May 15, 2020 at 02:12:00PM -0400, Charalampos Stratakis wrote:
rdma-coredledford honli jwilson
rdma-core pyverbs must be linked
On Mon, Jun 01, 2020 at 02:59:32PM +0800, Honggang LI wrote:
>
> I think I know how to avoid link pyverbs without libpython3.9. I will
> fix this for rdma-core (fc33).
I confirmed this patch fix this issue. However, upstream wants all shared
ELFs have fully described linking. That means all pytho
On Sun, May 31, 2020 at 11:31:23PM -0700, Gordon Messmer wrote:
> On 5/31/20 6:37 PM, Honggang LI wrote:
> > We have to compile/build the module before we can import it from a
> > python3 shell. The problem is how to compile the modules without pass
> > "-lpython3.9" or "-lpython3.9d" to the linker
On 6/1/20 4:37 AM, Honggang LI wrote:
On Sun, May 31, 2020 at 10:30:32AM -0700, Gordon Messmer wrote:
On 5/31/20 1:24 AM, Honggang LI wrote:
As you see, "-lpython3.9" or "-lpython3.9d" library must be provided to
the linker. Otherwise, a lot of "undefined reference to xxx" error
messages show u
On Mon, Jun 01, 2020 at 09:37:39AM +0800, Honggang LI wrote:
> On Sun, May 31, 2020 at 10:30:32AM -0700, Gordon Messmer wrote:
> > On 5/31/20 1:24 AM, Honggang LI wrote:
> > > As you see, "-lpython3.9" or "-lpython3.9d" library must be provided to
> > > the linker. Otherwise, a lot of "undefined re
On 5/31/20 6:37 PM, Honggang LI wrote:
We have to compile/build the module before we can import it from a
python3 shell. The problem is how to compile the modules without pass
"-lpython3.9" or "-lpython3.9d" to the linker (/usr/bin/ld).
Do you have a link to a build log?
__
On Sun, May 31, 2020 at 10:30:32AM -0700, Gordon Messmer wrote:
> On 5/31/20 1:24 AM, Honggang LI wrote:
> > As you see, "-lpython3.9" or "-lpython3.9d" library must be provided to
> > the linker. Otherwise, a lot of "undefined reference to xxx" error
> > messages show up.
>
>
> I'd guess that yo
On 5/31/20 1:24 AM, Honggang LI wrote:
As you see, "-lpython3.9" or "-lpython3.9d" library must be provided to
the linker. Otherwise, a lot of "undefined reference to xxx" error
messages show up.
I'd guess that you're seeing "undefined reference" when you use ldd on
the so, and that's expecte
On Fri, May 29, 2020 at 06:47:35PM +0200, Petr Viktorin wrote:
>
>
> On 2020-05-18 03:53, Honggang LI wrote:
> > On Fri, May 15, 2020 at 02:12:00PM -0400, Charalampos Stratakis wrote:
> > > rdma-coredledford honli jwilson
> >
> > rdma-core pyverbs must be linked with libpython38. For
On 2020-05-18 03:53, Honggang LI wrote:
On Fri, May 15, 2020 at 02:12:00PM -0400, Charalampos Stratakis wrote:
rdma-coredledford honli jwilson
rdma-core pyverbs must be linked with libpython38. For example,
build]$ nm ./python/pyverbs/mem_alloc.cpython-38-x86_64-linux-gnu.so | g
On 15/05/20 14:12 -0400, Charalampos Stratakis wrote:
Hello everyone,
As of Python 3.8, python C extensions modules should not link to libpython,
unless they embed the interpreter in their code. Relevant upstream PR:
https://github.com/python/cpython/pull/12946
If your package links to libpyth
Thanks Charalampos,
On Fri, May 15, 2020 14:12:00 -0400, Charalampos Stratakis wrote:
> nest ankursinha
I've filed an issue upstream:
https://github.com/nest/nest-simulator/issues/1630
I'll update the packages once I've heard from them.
--
Thanks,
Regards,
Ankur Sinha "Francisc
On Fri, 15 May 2020 14:12:00 -0400 (EDT)
Charalampos Stratakis wrote:
> If you are not sure if your package links to libpython, a way to
> figure this out is to inspect the code for the Py_Initialize and the
> Py_Finalize calls [0]. If the code includes those calls, no action
> is required from
> jskarvad gnuradio gr-air-modes gr-fcdproplus gr-hpsdr gr-iqbal gr-osmosdr
> gr-rds hamlib pidgin
pidgin - it calls Py_Initialize, so I kept is as is
hamlib - fixed & forwarded upstream
gnuradio stuff - it doesn't seem it calls Py_Initialize, but linking without
-python failed:
/usr/bin/ld: ..
- Original Message -
> From: "Charalampos Stratakis"
> To: "Development discussions related to Fedora"
>
> Sent: Friday, May 15, 2020 8:12:00 PM
> Subject: Many packages unnecessarily link to libpython
>
> pyotherside m4rtink
On Friday, May 15, 2020 8:12:00 PM CEST Charalampos Stratakis wrote:
> [...]
> On Fedora Rawhide, there are at this point 144 packages linking to libpython,
> many of those possibly without any need for it.
> [...]
> postgresql hhorak jstanek panovotn pkajaba pkubat praiskup tgl
> [...]
>
On Fri, May 15, 2020 at 02:12:00PM -0400, Charalampos Stratakis wrote:
> rdma-coredledford honli jwilson
rdma-core pyverbs must be linked with libpython38. For example,
build]$ nm ./python/pyverbs/mem_alloc.cpython-38-x86_64-linux-gnu.so | grep -w
U | grep PyInterpreterState_GetID
> On 17 May 2020, at 14:48, Simon Farnsworth wrote:
>
>> On 15 May 2020, at 19:12, Charalampos Stratakis wrote:
>>
>> Hello everyone,
>>
>> As of Python 3.8, python C extensions modules should not link to libpython,
>> unless they embed the interpreter in their code. Relevant upstream PR:
> On 15 May 2020, at 19:12, Charalampos Stratakis wrote:
>
> Hello everyone,
>
> As of Python 3.8, python C extensions modules should not link to libpython,
> unless they embed the interpreter in their code. Relevant upstream PR:
> https://github.com/python/cpython/pull/12946
> If your package
> nemo-extensions jcpunk leigh123linux
nemo-extensions has Py_Initialize / Py_Finalize in the nemo-python sub-package
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora
On Fri, May 15, 2020 at 02:12:00PM -0400, Charalampos Stratakis wrote:
> libsbml sagitter zbyszek
Should be fixed now (assuming the build suceeds ;)).
Zbyszek
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an ema
On Fri, May 15, 2020 at 02:12:00PM -0400, Charalampos Stratakis wrote:
> Hello everyone,
>
> As of Python 3.8, python C extensions modules should not link to libpython,
> unless they embed the interpreter in their code. Relevant upstream PR:
> https://github.com/python/cpython/pull/12946
> If yo
swift-lang includes its own private copy of LLDB for its REPL, which uses
Python as its scripting language so it too is linking correctly.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedorapro
Charalampos Stratakis wrote:
> kkoflercalamares kig
These both embed the Python interpreter and thus necessarily link to
libpython.
Kevin Kofler
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-l
* Charalampos Stratakis:
> If your package links to libpython without requiring it, it won't be
> possible to use the python3-debug binary with your python C extension,
> unless you recompile the extension against it.
Would it make sense to work around this by some other means?
Thanks,
Florian
_
On pe, 15 touko 2020, Charalampos Stratakis wrote:
Hello everyone,
As of Python 3.8, python C extensions modules should not link to
libpython, unless they embed the interpreter in their code. Relevant
upstream PR: https://github.com/python/cpython/pull/12946 If your
package links to libpython wi
On 15. 05. 20 20:12, Charalampos Stratakis wrote:
Hello everyone,
As of Python 3.8, python C extensions modules should not link to libpython,
unless they embed the interpreter in their code. Relevant upstream
PR:https://github.com/python/cpython/pull/12946
If your package links to libpython wi
On Fri, May 15, 2020 at 12:12 PM Charalampos Stratakis
wrote:
> cvc4 brouhaha jjames
The cvc4 package has been fixed in Rawhide. I'll talk to upstream about it.
--
Jerry James
http://www.jamezone.org/
___
devel mailing list -- devel@li
On 15. 05. 20 20:12, Charalampos Stratakis wrote:
libarcus churchyard gferon
libarcus-lulzbot spot
libsavitar churchyard gferon
I know for sure those packages link to libpython unnecessarily just because
their cmake build script does so. The fix is simple:
https://s
Hi,
On Fri, May 15, 2020 at 02:12:00PM -0400, Charalampos Stratakis wrote:
> Hello everyone,
>
> As of Python 3.8, python C extensions modules should not link to libpython,
> unless they embed the interpreter in their code. Relevant upstream PR:
> https://github.com/python/cpython/pull/12946
>
- Original Message -
> From: "Richard W.M. Jones"
> To: "Charalampos Stratakis"
> Cc: "Development discussions related to Fedora"
> , ebl...@redhat.com
> Sent: Friday, May 15, 2020 8:50:31 PM
> Subject: Re: Many packages unnecessarily l
On Fri, May 15, 2020 at 02:12:00PM -0400, Charalampos Stratakis wrote:
> nbdkit rjones
I guess nbdkit is one of the good ones? We link to libpython because
we want to run Python code from a C main program (nbdkit, an NBD
server written in C).
http://libguestfs.org/nbdkit-python-plu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On Fri, 2020-05-15 at 14:12 -0400, Charalampos Stratakis wrote:
> Hello everyone,
Hey,
> As of Python 3.8, python C extensions modules should not link to
> libpython, unless they embed the interpreter in their code. Relevant
> upstream PR: https://g
Hello everyone,
As of Python 3.8, python C extensions modules should not link to libpython,
unless they embed the interpreter in their code. Relevant upstream PR:
https://github.com/python/cpython/pull/12946
If your package links to libpython without requiring it, it won't be possible
to use th
36 matches
Mail list logo
