Le Sat, Oct 30, 2021 at 10:20:18AM +0200, Landry Breuil a écrit :
> Le Sat, Oct 30, 2021 at 09:51:34AM +0200, Landry Breuil a écrit :
> > Hi,
> > 
> > i dunno if something should be fixed in the python build system (is it
> > *necessary* to point at /usr/local/lib for libpython3.8.so ?), but i
> > think there's something definitely wrong somewhere. That probably
> > accounts for many failures i remember seeing building python updates
> > when the previous version was installed systemwide, and taking precedence
> > over the just-newly-built lib/extension.
> 
> looking a bit more at our python port and reading
> https://docs.python.org/3/using/configure.html#linker-flags, the
> paths seem to come from MAKE_FLAGS += LDFLAGS='-L${WRKSRC}
> -L${LOCALBASE}/lib/' in /usr/ports/lang/python/Makefile.inc. Dunno if
> that's right or wrong for them to end up in LDSHARED, so i wonder if
> PY_LDFLAGS or PY_CORE_LDFLAGS or LDSHARED should be overriden.

Hah !! https://bugs.python.org/issue35257 and
https://bugs.python.org/issue21121 looks definitely related ! so
i think we should use PY_LDFLAGS_NODIST / CFLAGS_NODIST in the python
port to build python itself, so that those paths dont 'leak' to
extensions built later on..

Landry

Reply via email to