New submission from Antonio Cavallo:
I've noticed that linux distros have a set of patch to fix a hardcoded lib in
their makefiles:
eg. Makefile.pre.in:
INCLUDEDIR=¬@includedir@
CONFINCLUDEDIR=¬$(exec_prefix)/include
SCRIPTDIR=¬…$(prefix)/lib<== HARDCODED
This is due to
Antonio Cavallo added the comment:
Hi,
the patch it is really simple, it adds the @LIB@ and @ARCH@ variables to the
configure machinery.
If you look into the Makefile.pre.in:
INCLUDEDIR=¬@includedir@
CONFINCLUDEDIR=¬$(exec_prefix)/include
SCRIPTDIR=¬…$(prefix)/lib
This hardcodes lib that
New submission from Antonio Cavallo :
Hi,
I've seen the code change in /python/trunk/configure.in (rev. 74072):
it enforces a specific autoconfig version (2.61) in order to build
python.
Unfortunately OpenSuSE 11.1 (mainstream at time of writing) has an
updated version of autoconf 2.63
Antonio Cavallo added the comment:
Yes the rebuild does an autoreconf step.
--
___
Python tracker
<http://bugs.python.org/issue6585>
___
___
Python-bugs-list m
Antonio Cavallo added the comment:
This patch changes the log.py in order to make use of the logging
infrastructure.
There are few point tough worth of mention.
There're two separate stages when log.py is used:
a) during the python interpreter build (let's call it bootstrap)
Antonio Cavallo added the comment:
Hi Tarek,
I agree that a change in that module is "risky" but a warning won't
solve the main problem in the long run: anyway I'm not able to comment
about the best strategy.
Now the access problem:
If an import logging is put into th
Changes by Antonio Cavallo :
Added file: http://bugs.python.org/file13908/issue3992.remove-custom-log.diff
___
Python tracker
<http://bugs.python.org/issue3992>
___
___
Changes by Antonio Cavallo :
Removed file: http://bugs.python.org/file13906/issue3992.remove-custom-log.diff
___
Python tracker
<http://bugs.python.org/issue3992>
___
___
Antonio Cavallo added the comment:
Hi Tarek,
there is a new patch.
- Logger is now back to Log
- put back INFO/DEBUG etc.
- Wrapped the code inside a try/except
I removed the _global_logger/logger variables, because they're
superfluous: so the cound of the module exported sy
Changes by Antonio Cavallo :
Removed file: http://bugs.python.org/file13908/issue3992.remove-custom-log.diff
___
Python tracker
<http://bugs.python.org/issue3992>
___
___
Antonio Cavallo added the comment:
Actually I think the problem (see the attached file susebuild.log) is
in the module time.so: during the build the python interpreter has not
access to it (it is dynamically loaded) and it fails.
If that works is because an already python is set in the
Antonio Cavallo added the comment:
Hi,
the latest patch (custom-log.diff minus the import logging
at the begin) breaks the imaging python module build:
the log is in the file susebuild.failed.imaging.log.
--
Added file: http://bugs.python.org/file13939/susebuild.failed.imaging.log
Antonio Cavallo added the comment:
Hi Tarek,
there is a colliding warn symbol: one defiend whiting import warnings
as warn and another defined as warn = logger.warn (~ line 56).
It breaks all the modules build (see attached file
susebuild.failed.imaging-2.log).
As soon I confirm the patch
Antonio Cavallo added the comment:
Hi Tarek,
This is the latest patch to log.py that compiles with the latest python
svn 72494. It shows no problem with the few modules I've used so far:
now I can't decide if this should go mainline or not but I'll leave
here as reference
New submission from Antonio Cavallo:
This patch introduces two new options (--enable-ptmx, --enable-ptc) to
the configure script.
In cross compile the actual code requires an external config.site config file to
set the result values for the AC_CHECK_FILE macros on /dev/ptmx, /dev/ptc.
These
Antonio Cavallo added the comment:
I suppose to reduce the noise is better close this, thanks
--
resolution: -> out of date
status: open -> closed
___
Python tracker
<http://bugs.python.org/i
Changes by Antonio Cavallo :
--
nosy: +benjamin.peterson, doko
___
Python tracker
<http://bugs.python.org/issue17819>
___
___
Python-bugs-list mailing list
Unsub
Antonio Cavallo added the comment:
So far it seems the special handling in config.site is restricted to these two
bits ptc/ptmx (I'm targeting android in cross compiling at the moment).
--
___
Python tracker
<http://bugs.python.org/is
New submission from Antonio Cavallo:
This patch adds autoconf.ac check for the locale.h file in addition to
langinfo.h. The patch contains also a fix to Python/fileutils.c file.
The android ndk provides locale.h but no langinfo.h: this fixes the issue.
BTW bionic doesn't have any ru
Antonio Cavallo added the comment:
I see, in that case wouldn't make more sense completely remove the check for
the langinfo.h either?
I think is better to close the issue to keep the noise low.
Thanks
--
resolution: -> works for me
status: open -
Antonio Cavallo added the comment:
ok I see it, thanks.
I've attached a new patch fixing the files with the locale's guards.
Modules/readline.c might have the SAVE_LOCALE renamed into HAVE_SETLOCALE but
the patch doesn't address that bit.
Android has definitively locale.h bu
21 matches
Mail list logo