Summary: | dev-lang/yasm-1.1.0 fails to build with >=dev-python/cython-0.14 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Robert Cabrera <robcab666> |
Component: | [OLD] Development | Assignee: | AMD64 Project <amd64> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | aidanamarks, anarchy, arfrever, che, email, heluani, jarausch, kdvgent, rabbe, u.plate, zeekec |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | All | ||
URL: | http://codespeak.net/pipermail/cython-dev/2010-December/010414.html | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
build.log
yasm-1.1.0-cython-0.14.patch |
Description
Robert Cabrera
2010-12-13 06:34:16 UTC
For me not compile it with USE=python. I use python ~2.7.1 (In reply to comment #1) > For me not compile it with USE=python. > I use python ~2.7.1 > от ~amd64 (In reply to comment #1) > For me not compile it with USE=python. > I use python ~2.7.1 > ooops, sorry on ~amd64 confirmed here that -python works. ~amd64 here. Created attachment 257031 [details]
build.log
USE=python nls
(In reply to comment #0) > dev-lang/yasm-1.1.0 crashes during compile stage of emerge on my ~x86 laptop > with the following error msg: Here (python-2.7.1, cython-0.14_rc0 on ~amd64) I get x86_64-pc-linux-gnu-gcc -std=gnu99 -mtune=native -O2 -msse3 -pipe -Wl,-O1 -Wl,--as-needed -o vsyasm vsyasm.o yasm-options.o libyasm.a # pyxstr... # wrote _yasm.pxi, 2188 lines /usr/bin/python -c "from Cython.Compiler.Main import main; main(command_line=1)" \ -o yasm_python.c yasm.pyx Traceback (most recent call last): File "<string>", line 1, in <module> File "/usr/lib64/python2.7/site-packages/Cython/Compiler/Main.py", line 790, in main result = compile(sources, options) File "/usr/lib64/python2.7/site-packages/Cython/Compiler/Main.py", line 765, in compile return compile_multiple(source, options) File "/usr/lib64/python2.7/site-packages/Cython/Compiler/Main.py", line 737, in compile_multiple result = run_pipeline(source, options) File "/usr/lib64/python2.7/site-packages/Cython/Compiler/Main.py", line 601, in run_pipeline err, enddata = context.run_pipeline(pipeline, source) File "/usr/lib64/python2.7/site-packages/Cython/Compiler/Main.py", line 240, in run_pipeline data = phase(data) File "/usr/lib64/python2.7/site-packages/Cython/Compiler/ParseTreeTransforms.py", line 1025, in __call__ return super(AnalyseDeclarationsTransform, self).__call__(root) File "Visitor.py", line 272, in Cython.Compiler.Visitor.CythonTransform.__call__ (Cython/Compiler/Visitor.c:4936) File "Visitor.py", line 255, in Cython.Compiler.Visitor.VisitorTransform.__call__ (Cython/Compiler/Visitor.c:4696) File "Visitor.py", line 163, in Cython.Compiler.Visitor.TreeVisitor._visit (Cython/Compiler/Visitor.c:3254) File "/usr/lib64/python2.7/site-packages/Cython/Compiler/ParseTreeTransforms.py", line 1033, in visit_ModuleNode node.analyse_declarations(self.env_stack[-1]) File "/usr/lib64/python2.7/site-packages/Cython/Compiler/ModuleNode.py", line 64, in analyse_declarations self.body.analyse_declarations(env) File "/usr/lib64/python2.7/site-packages/Cython/Compiler/Nodes.py", line 346, in analyse_declarations stat.analyse_declarations(env) File "/usr/lib64/python2.7/site-packages/Cython/Compiler/Nodes.py", line 346, in analyse_declarations stat.analyse_declarations(env) File "/usr/lib64/python2.7/site-packages/Cython/Compiler/Nodes.py", line 3249, in analyse_declarations self.body.analyse_declarations(scope) File "/usr/lib64/python2.7/site-packages/Cython/Compiler/Nodes.py", line 346, in analyse_declarations stat.analyse_declarations(env) File "/usr/lib64/python2.7/site-packages/Cython/Compiler/Nodes.py", line 1999, in analyse_declarations self.analyse_signature(env) File "/usr/lib64/python2.7/site-packages/Cython/Compiler/Nodes.py", line 2097, in analyse_signature arg.hdr_type = sig.fixed_arg_type(i) File "/usr/lib64/python2.7/site-packages/Cython/Compiler/TypeSlots.py", line 100, in fixed_arg_type return self.format_map[self.fixed_arg_format[i]] KeyError: 'T' I don't know if this is a cython or a yasm problem, Helmut. I too can confirm on my ~x86 laptop that yasm builds and installs with USE="-python" flag during emerge. I don't know how this changes functionality or what package even brought in yasm in the first place. But it does build with -python flag. I came across this problem too when trying to emerge mplayer on Gentoo Prefix. A sufficient workaround in the Gentoo Prefix case is to put a mask "=dev-lang/yasm-1.1.0" in etc/portage/package.mask, which causes version 1.0.1 to be emerged instead. (In reply to comment #8) > I came across this problem too when trying to emerge mplayer on Gentoo Prefix. > A sufficient workaround in the Gentoo Prefix case is to put a mask > "=dev-lang/yasm-1.1.0" in etc/portage/package.mask, which causes version 1.0.1 > to be emerged instead. > I don't know how new to Gentoo or Linux you are, but masking an unstable package to downgrade to a previous stable version is really not a workaround. A workaround is when you come up with a solution or method that allows the package in question to work as intended or work with some limited functionality. Example: In comment #4 on this thread Fernando V. suggested that building with -python use flag allows yasm to compile and install. This is a workaround, as it allows the package in question to build and install. None of us know yet what effect this has on functionality, but since we're running an ~ arch this is what we are here to find out. People running ~ arches are the beta testers for those running stable arches. All you did was downgrade to the stable version. Anyone can do this at any time to any package they so choose. In fact, sometimes you may find you have to run a stable version because it is critical for what you need to do at that time. As experienced Gentoo users we know that we can mask a package that doesn't compile or crashes, or unmask one that we'd would like to experiment with. This goes without saying. However, doing so does nothing to help in ironing out the issue(s) that's causing the problem in the first place and thus not a workaround. I hope this clarifies things. I just stumbled across this myself... I found that I had upgraded cython by accident... try downgrading to dev-python/cython-0.13, yasm doesn't compile for me with 0.14. I run an Intel processor and noticed this problem after I upgraded to python-2.7 Not sure if it is related to the update, as I had already unmerged python-2.6 by the time. USE=-python does let it compile fine. (In reply to comment #10) > I just stumbled across this myself... I found that I had upgraded cython by > accident... try downgrading to dev-python/cython-0.13, yasm doesn't compile for > me with 0.14. I can confirm that dev-lang/yasm-1.1.0 fails to compile with cython-0.14_rc0, but compiles fine with 0.13. (In reply to comment #9) > (In reply to comment #8) Oops, I realize that my comment looks silly. I was about to file a bug under Gentoo/Alt-PrefixSupport when I found that the yasm problem was already reported. In the context of applications on Gentoo Prefix that may pull in dozens of dependencies, or Gentoo Prefix itself, I tend to think of little tweaks such as changing the emerge order or inserting a mask as a "workaround" if it gets me to the goal. Not so in the case of this bug report though. Thanks for the notice. (In reply to comment #13) Rabbe, sorry if I came on strong this was not my intention and I don't want to discourage you. We are all trying to make Gentoo better and comments in bug reports are an important way to do so. Please keep helping with your input when you find a problem. Thanks for your comments. (In reply to comment #14) > (In reply to comment #13) > Rabbe, sorry if I came on strong this was not my intention and I don't want to > discourage you. We are all trying to make Gentoo better and comments in bug > reports are an important way to do so. Please keep helping with your input when > you find a problem. Thanks for your comments. > np, next time just try to be positive and don't across as being negative. the whole point is to encourage collaboration and communications. i know you was trying to come across positive but your words didn't, try harder as you mention. I understand your point of view but try to come across a different way next time around ;) Gentoo is a family so treat users like one. :) Same problem for me on ~amd64 - yasm compiles fine with cython-0.13, with cython-0.14 no luck. Of course for 2.x branch I have set python-2.7.1. dev-python/cython-0.14-r1 prints proper error message instead of raising exception. Now dev-lang/yasm needs to be fixed. Created attachment 257994 [details, diff]
yasm-1.1.0-cython-0.14.patch
(In reply to comment #18) > Created an attachment (id=257994) [details] > yasm-1.1.0-cython-0.14.patch > thanks, applied in tree please take yasm-1.1.0-r1 with cython-0.14 when you plan to stabilize it |