2010/5/24 Denis Barbier <bou...@gmail.com> > 2010/5/23 John Griessen wrote: > > Denis Barbier wrote: > > > >> I ran the same commands, except that this one has to be called with > >> sudo. Do you build pythonocc as root, or did you simply forget it? > > > > Je l'ai oublié. > > sudo python2.6 setup.py install > > est ce que je fais. > [...] > > I made more tests, and better understand what happens. Our problems > are related to > http://bugs.python.org/issue7562 > In short, one cannot run > python setup.py build install > because generated python files are then not installed. > When running two distinct steps: > python setup.py build > sudo python setup.py install > everything should work fine. I had trouble even when doing so, but am > pretty sure that they were due to resource usage (either disk or CPU). > Maybe this can be mentioned in INSTALL file, by adding another note like: > ** Note ** due to limitations in distutils, these two commands must > be run sequentially, it is not possible to run 'python setup.py build > install' or directy 'python setup.py install'. > > Please note also that this paragraph (about step 3) is duplicated. > > Denis > > Hi Denis,
The sequential build/install was actually not documented. I updated the INSTALL file and committed changes to the svn repository. Thomas
_______________________________________________ Pythonocc-users mailing list Pythonocc-users@gna.org https://mail.gna.org/listinfo/pythonocc-users
