Summary: | games-util/nml-0.2.4-r2 fails to install nmlc compiler | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | MaurizioB <mauriziob> |
Component: | [OLD] Games | Assignee: | Gentoo Games <games> |
Status: | RESOLVED OBSOLETE | ||
Severity: | normal | CC: | python |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
emerge --info
Full emerge output output of equery files nml |
Description
MaurizioB
2014-01-25 22:42:02 UTC
reopen with the output of emerge --info Created attachment 368804 [details]
emerge --info
Can you attach the full output of the build please? Also it would be great if you can install gentoolkit and post the output from equery files nml Created attachment 369352 [details]
Full emerge output
Created attachment 369354 [details]
output of equery files nml
What version of dev-python/setuptools? I have the latest stable version of setuptools, 0.8-r1. Well, something's not right on your system with related to setuptools since you're getting: /usr/lib/python2.7/distutils/dist.py:267: UserWarning: Unknown distribution option: 'entry_points' warnings.warn(msg) did you remember to run python-updater when you upgraded python last? Try re-emerging your python-related packages and make sure to follow any additional directions that the ebuilds print out. As I remember I did run python-updater, to be sure I just reemerged both python-2.7, setuptools and pip (googling around resulted in similar errors regarding pip and I remember that about 6 months ago I messed around with it by mistake). Still no nmlc when installing nml and I still get that error. I checked setuptools emerge log and there's such no error, and I can't emerge every python package I have to check for the same error. Is there a package which can show a similar error? Or a specific package I could have missed that should be emerged again? maybe the python group can help you out. #gentoo-bugs | MaurizioB | I was able to track the origin of the issue, so there was no actual bug, just a problem with my python configuration |