Due sqlite2 deprecation Reproducible: Always
Needed for building ARM cross development tools Bug is silly: Relevant fragment of /etc/make.conf: cflags = "-fPIC -march=native -O2 -pipe -v " CFLAGS = "$(CC) $(cflags)" What emerge days is the error: creating build-2.7/temp.linux-x86_64-2.7/src -fno-strict-aliasing -fPIC -DMODULE_NAME="pysqlite2.dbapi2" -I/usr/include/python2.7 -c src/module.c -o build-2.7/temp.linux-x86_64-2.7/src/module.o unable to execute -fno-strict-aliasing: No such file or directory error: command '-fno-strict-aliasing' failed with exit status 1 * ERROR: dev-python/pysqlite-2.6.3 failed (compile phase): It is obvious that someone is confusing GG (or GCC) with CFLAGS. This happens a lot. Also note that -fno-strict-aliasing is _not_ part of any make.conf, nor the .ebuild file. So, again, who is generating this brain-dead variable?
(In reply to comment #1) > Needed for building ARM cross development tools > > Bug is silly: > > Relevant fragment of /etc/make.conf: > > cflags = "-fPIC -march=native -O2 -pipe -v " > CFLAGS = "$(CC) $(cflags)" Note this bug is about removing dev-python/pysqlite:0 (support for sqlite 2) because sqlite 2 itself is scheduled to be removed. I strongly recommend you port whatever you use that still needs (py)sqlite 2 over to sqlite 3. Also, that does not seem like a very healthy value for CFLAGS. If you have packages not scheduled to be removed failing in the way you pasted, please file a new bug for that. Please include enough information to allow us to reproduce the problem, as well as a full build log. Finally, -fno-strict-aliasing is (somewhat unfortunately) required for most python extension code, because of how PyObject and PyObject_HEAD are implemented in python 2. This is not something that can be fixed in python 2 for compatibility reasons. Getting the flag added is supposed to happen. (You might want to read up on what -fno-strict-aliasing does for a better understanding of why it is necessary.)
I have masked dev-python/sqlite:0 for removal in 30 days.
This is not handled by treecleaners so removing ourselves from here
Package removed.
Seems no one cared to check for reverse deps before removing or even cared to file bugs for packages that still use it. You can't expect that everyone follows mask/removals every time. So when you remove libs/modules, check reverse deps. You broke at least one stable package. bug 469288
(In reply to comment #6) My apologies; I did do a reverse dependency sweep for pysqlite:0, but I did not realize at the time that pysqlite:2 had also been masked by mgorny.
