Akira Kitada <[EMAIL PROTECTED]> added the comment:
I think this patch is harmless and also deserve to be merged
into 2.5.3 release. (As I mentioned earlier, this has been already
merged into 3.0 and 2.6 branches)
___
Python tracker <[EMAIL PROTECTE
Changes by Akira Kitada <[EMAIL PROTECTED]>:
--
versions: +Python 2.5.3, Python 2.6, Python 2.7, Python 3.0
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.python.
Akira Kitada <[EMAIL PROTECTED]> added the comment:
OS X 10.5.5 seems to have the problem just as described,
whereas there seems no problem on FreeBSD 6.3.
--
components: +Build, Macintosh
nosy: +akitada
___
Python tracker <[EMAIL PROTECTE
Changes by Akira Kitada <[EMAIL PROTECTED]>:
Removed file: http://bugs.python.org/file12160/issue4370.diff
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.pytho
Akira Kitada <[EMAIL PROTECTED]> added the comment:
Attached patch just leaves Py_GCC_ATTRIBUTE as it is now.
Here is the highlight.
/*
* Hide GCC's format attribute from compilers if one of the following is
true:
* a) the compiler does not support it and not on RISC OS
* b) t
Akira Kitada <[EMAIL PROTECTED]> added the comment:
Updating versions.
--
versions: +Python 2.5.3, Python 2.6, Python 2.7, Python 3.0
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.pytho
Akira Kitada <[EMAIL PROTECTED]> added the comment:
I'm just curious to know which is the right behavior.
# Python 3.0
Traceback (most recent call last):
File "bad_range.py", line 7, in
print(range(MyInt(2**3), MyInt(2**3+10)))
TypeError: 'MyInt' obj
Changes by Akira Kitada <[EMAIL PROTECTED]>:
--
versions: +Python 2.5.3
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue4368>
___
__
Akira Kitada <[EMAIL PROTECTED]> added the comment:
Martin,
Thank you for the feedback.
I think we can avoid the problem that would be introduced by the removal
of Py_GCC_ATTRIBUTE by leaving it as is
(probably adding "#warning this macro is deprecated. Please use
Py_GCC_FORMA
Akira Kitada <[EMAIL PROTECTED]> added the comment:
Tested my patch on
* FreeBSD 4.11 (gcc version 2.95.4, does not support "z")
* FreeBSD 6.3 (gcc version 3.4.6, supports "z")
and it worked fine on both. (using trunk)
___
Python
Changes by Akira Kitada <[EMAIL PROTECTED]>:
Removed file: http://bugs.python.org/file12159/issue4370.diff
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.pytho
Changes by Akira Kitada <[EMAIL PROTECTED]>:
Added file: http://bugs.python.org/file12160/issue4370.diff
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.pytho
Changes by Akira Kitada <[EMAIL PROTECTED]>:
Removed file: http://bugs.python.org/file12124/pyport.h.diff
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.pytho
Akira Kitada <[EMAIL PROTECTED]> added the comment:
The new patch attached renamed Py_GCC_ATTRIBUTE to Py_GCC_FORMAT_ATTRIBUTE.
As Roumen pointed out, "the current python code use Py_GCC_ATTRIBUTE
only for 'format(printf(...)) ' attribute.", so this change sh
Akira Kitada <[EMAIL PROTECTED]> added the comment:
I'm having similar problem with distutils.
http://mail.python.org/pipermail/python-dev/2008-November/083670.html
Is there any reason customize_compiler
- only get CPPFLAGS in env, not ones from sysconfig?
- doesn't get OPT fro
Akira Kitada <[EMAIL PROTECTED]> added the comment:
Martin,
Two questions:
1. Isn't Christian's patch enough for this?
2. How about Python 3.0 and 2.6.1? Are they also out of scope for this?
___
Python tracker <[EMAIL PROTECTED]>
&
Changes by Akira Kitada <[EMAIL PROTECTED]>:
--
versions: +Python 2.5.3, Python 2.6, Python 2.7, Python 3.0, Python 3.1
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.pytho
Akira Kitada <[EMAIL PROTECTED]> added the comment:
Thank you again for the feedback.
I think those warnings are not so useful, or even misleading,
when we know they are handled appropriately.
with these warnings hidden, it would get much more easy to read
build log and find real warnings
Akira Kitada <[EMAIL PROTECTED]> added the comment:
Roumen,
Thanks for the feedback!
This patch disables __attribute__ when PY_FORMAT_SIZE_T isn't defined,
not always.
About the name of the macro, I think you are right.
Py_GCC_FORMAT_ATTRIBUTE would be much better name if it is n
Akira Kitada <[EMAIL PROTECTED]> added the comment:
I tested this on FreeBSD 6.3 and it worked. (release25-maint)
waiting for review.
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.pytho
Akira Kitada <[EMAIL PROTECTED]> added the comment:
Changing the title again because this problem is not FreeBSD 4 specific.
Build on recent FreeBSD also has the same problem.
(I tested this on 6.3, too)
--
title: cannot find -lpython2.X when buinding Python on FreeBSD 4.11 -&g
Akira Kitada <[EMAIL PROTECTED]> added the comment:
Changing the title because this is not 2.5.x specific.
--
title: cannot find -lpython2.5 when buinding Python 2.5.2 on FreeBSD 4.11 ->
cannot find -lpython2.X when buinding Python on FreeBSD 4.11
versions: +Python 2.5.3, P
Akira Kitada <[EMAIL PROTECTED]> added the comment:
Amaury,
thank you for pointing that out.
Attached patch disables this "__attribute__"
when PY_FORMAT_SIZE_T is undefined after configure script.
I confirmed this eliminate warnings in FreeBSD 4.11
--
keywords: +patch
Akira Kitada <[EMAIL PROTECTED]> added the comment:
I looked into the code and found these warnings about 'z' were
not from printf family but PyString_FromFormat.
Apparently PyString_FromFormat handles the 'z' itself, without
delegating that to printf family.
Then why a
Akira Kitada <[EMAIL PROTECTED]> added the comment:
Yes, that change was not merged into 2.5 branch.
I Hope it's not yet been too late for 2.5.3.
I confirmed this fixes the problem on FreeBSD 4.11.
___
Python tracker <[EMAIL PRO
New submission from Akira Kitada <[EMAIL PROTECTED]>:
Some compilers don't understand "%zd" format specifer
and gcc 2.95.4 is one of them.
(You can find more on http://www.and.org/vstr/printf_comparison)
When building Python with such compilers, you will see a lot
Akira Kitada <[EMAIL PROTECTED]> added the comment:
Christian's patch fixed this problem!
(tested on 4.11-RELEASE)
I'm not sure why the other platforms don't suffer this problem.
___
Python tracker <[EMAIL PROTECTED]>
<ht
New submission from Akira Kitada <[EMAIL PROTECTED]>:
Excerpt from configure.in
"""
# On FreeBSD 4.8 and MacOS X 10.2, a bug in ncurses.h means that
# it craps out if _XOPEN_EXTENDED_SOURCE is defined. Apparently,
# this is fixed in 10.3, which identifies itself as Dar
Changes by Akira Kitada <[EMAIL PROTECTED]>:
--
nosy: akitada
severity: normal
status: open
title: a bug in ncurses.h still exist in
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.pytho
New submission from Akira Kitada <[EMAIL PROTECTED]>:
I get a number of "cannot find -lpython2.5" error when building Python
2.5.2 on FreeBSD 2.5.2 with gcc 2.95.4.
This problem is only occured when I build it with "--enable-shared"
configure option.
This is how you
Akira Kitada <[EMAIL PROTECTED]> added the comment:
Christian,
Thank you for the review.
Let me know if there is anything I could help with this.
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.pytho
Akira Kitada <[EMAIL PROTECTED]> added the comment:
Thank you for pointing that out, Roumen!
I didn't realize that.
I updated the patch again.
Added file: http://bugs.python.org/file11901/issue4204.diff
___
Python tracker <[EMAIL PRO
Changes by Akira Kitada <[EMAIL PROTECTED]>:
Removed file: http://bugs.python.org/file11897/issue4204.diff
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.pytho
Changes by Akira Kitada <[EMAIL PROTECTED]>:
Removed file: http://bugs.python.org/file11892/Modules_readline.c.diff
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.pytho
Changes by Akira Kitada <[EMAIL PROTECTED]>:
Removed file: http://bugs.python.org/file11890/configure.in.diff
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.pytho
Akira Kitada <[EMAIL PROTECTED]> added the comment:
Roumen,
in Darwin, there is a macro called _DARWIN_C_SOURCE,
which re-enables things disabled by _XOPEN_SOURCE or the like.
(At least on OS X 10.5.5)
___
Python tracker <[EMAIL PROTECTE
Akira Kitada <[EMAIL PROTECTED]> added the comment:
Here's the output of configure.
Just as Mark said, it looks this is due to a libm bug.
"""
$ grep tanh config.log
configure:22062: checking whether tanh preserves the sign of zero
|and tanh(-0.) == -0. */
|
Akira Kitada <[EMAIL PROTECTED]> added the comment:
Attached is the patch containing all fixes.
I tested this on py3k and trunk on FreeBSD 4.11.
The test was done by using unitests in Lib/test.
Because I could not find a test for readline and
multiprocessing's test does not work on s
Akira Kitada <[EMAIL PROTECTED]> added the comment:
I will.
Would it be enough to test on trunk and py3k branch?
By the way, trunk seems to have some problem building now.
./Parser/asdl_c.py -h ./Include ./Parser/Python.asdl
env: python: No such file or directory
*** Error code 127
S
Akira Kitada <[EMAIL PROTECTED]> added the comment:
Here's the one.
I tested this patch on FreeBSD 4.11 and 6.3.
Both worked. :)
Added file: http://bugs.python.org/file11892/Modules_readline.c.diff
___
Python tracker <[EMAIL PRO
Akira Kitada <[EMAIL PROTECTED]> added the comment:
Thanks Christian,
Now all modules are working.
$ ./python
Python 2.6 (r26:66714, Oct 14 2008, 15:18:41)
[GCC 2.95.4 20020320 [FreeBSD]] on freebsd4
Type "help", "copyright", "credits" or "
Akira Kitada <[EMAIL PROTECTED]> added the comment:
Attached patch fixes build problem of math and mmap.
Apparently, FreeBSD 4 does not make some math functions available when
_XOPEN_SOURCE is defined and unlike newer FreeBSD, it cannot be fixed
with __BSD_VISIBLE macro.
As for readli
New submission from Akira Kitada <[EMAIL PROTECTED]>:
I was trying to build Python 2.6 on FreeBSD 4.11 and found it failed
to build some of the modules.
"""
Failed to find the necessary bits to build these modules:
_bsddb _sqlite3 _tkinter
gdbm
401 - 443 of 443 matches
Mail list logo
