| View previous topic :: View next topic |
| Author |
Message |
Duncan_Shriek
n00b
Joined: 17 Aug 2010
Posts: 10
|
 Posted: Wed Nov 12, 2014 8:13 pm Post subject: Portage shot itself by updating libffi from 3.1-r3 to 3.2 |
 |
|
Since that update every emerge fails after unpacking with:
| Code: |
Traceback (most recent call last):
File "/usr/lib64/python3.4/site-packages/portage/util/_async/ForkProcess.py", line 43, in _spawn
portage.process._setup_pipes(fd_pipes, close_fds=False)
File "/usr/lib64/python3.4/site-packages/portage/proxy/objectproxy.py", line 22, in __getattribute__
result = object.__getattribute__(self, '_get_target')()
File "/usr/lib64/python3.4/site-packages/portage/proxy/lazyimport.py", line 107, in _get_target
__import__(name)
File "/usr/lib64/python3.4/site-packages/portage/process.py", line 27, in <module>
from portage.util._ctypes import find_library, LoadLibrary, ctypes
File "/usr/lib64/python3.4/site-packages/portage/util/_ctypes.py", line 5, in <module>
import ctypes
File "/usr/lib64/python3.4/ctypes/__init__.py", line 541, in <module>
_reset_cache()
File "/usr/lib64/python3.4/ctypes/__init__.py", line 280, in _reset_cache
CFUNCTYPE(c_int)(lambda: None)
MemoryError
|
Any ideas how to revert that libffi update now? Any other ideas how to repair emerge? |
|
| Back to top |
|
 |
ct85711
Veteran
Joined: 27 Sep 2005
Posts: 1791
|
| Posted: Wed Nov 12, 2014 10:01 pm Post subject: |
|
|
| Just curious, did you try it with the active python set to either python 2.7 or 3.2? The main reason why I mention it, is because support for python 3.4 is still masked. |
|
| Back to top |
|
|
Duncan_Shriek
n00b
Joined: 17 Aug 2010
Posts: 10
|
| Posted: Wed Nov 12, 2014 10:05 pm Post subject: |
|
|
| ct85711 wrote: | | Just curious, did you try it with the active python set to either python 2.7 or 3.2? The main reason why I mention it, is because support for python 3.4 is still masked. |
Yes, I've usually python 2.7 eselected. 3.4 didn't change the error. |
|
| Back to top |
|
|
SemmZemm
n00b
Joined: 05 Jul 2013
Posts: 62
Location: France, Russia
|
| Posted: Thu Nov 13, 2014 1:56 pm Post subject: |
|
|
I have apparently the same problem as you but I did easily:
emerge -1 =dev-libs/libffi-3.1-r3 |
|
| Back to top |
|
|
Duncan_Shriek
n00b
Joined: 17 Aug 2010
Posts: 10
|
| Posted: Thu Nov 13, 2014 2:11 pm Post subject: |
|
|
| As I posted already in the other thread: booting with on the kernel command line was enough to fix it for me. |
|
| Back to top |
|
|
229566
Tux's lil' helper
Joined: 16 Aug 2010
Posts: 127
|
| Posted: Thu Nov 13, 2014 6:37 pm Post subject: |
|
|
However, that is not really a fix but a temporary solution. If you do run SELinux already, check what policy is causing this and why, and easily fix it with audit2allow. |
|
| Back to top |
|
|
N8Fear
Tux's lil' helper
Joined: 15 Apr 2013
Posts: 140
Location: Berlin (Germany)
|
| Posted: Thu Nov 13, 2014 9:29 pm Post subject: |
|
|
| Likely you just have to setsebool executable memory enabled (which is essentially what libffi does and why it clashes with pax enabled kernels too unless the binaries are marked with -m or -E). |
|
| Back to top |
|
|
|
Portage & Programming
