![]() It seems that this is actually a glibc problem and while 2.6.4 builds without the patch on newer versions of gcc (@8:), it still sometimes segfaults (as observed during the doxygen build). |
||
---|---|---|
.. | ||
package.py |
![]() It seems that this is actually a glibc problem and while 2.6.4 builds without the patch on newer versions of gcc (@8:), it still sometimes segfaults (as observed during the doxygen build). |
||
---|---|---|
.. | ||
package.py |