Dear all, I know I risk to be tedious but since leaving the Dev Tools installer take all its time (3+ hrs) has solved the problem of the missing files (python 2.5.5 installed OK and works) there is a lesson to be learned, by me and maybe others:
It is - with no reasonable doubt - dangerous to stop the "Optimizing System Performance" procedure (even if progress bar is almost at the end but not advancing) in that it may leave a Dev Tools installation into an unreliable state or somehow corrupt the system files. I certainly was not aware of the entity of problem nor suspecting it. Even if common knowledge tells us that only a pre-binding takes place during Optimization there must be something else involved (otherwise one would simply do a pre-binding afterward on the command line in case the Optimizing apparently freezes: and I happened to have done exactly that). So in case you'll face the same problem (installer apparently freezing) be patient and resist the urge to stop the installer assuming the installation must be complete (ie all files): take your wife to dinner or go to a meeting ;-) PS Jeff, no problem, it is worth a wait of 3+ hrs to have a correct installation, although not common for Dev Tools and certainly tedious. All problems disappeared and I have now a larger than before /usr/include tree. After all, weird, isn't it? >Wednesday, January 16, 2002, at 06:33 pm, Massimo Marino wrote: > >> This time I let it go without interfering: 3+ hrs!!! I have been >> tempted to stop it again. So I guess during Optimizing it still writes >> files and updates directories. > >Nah, optimizing just runs update_prebinding. Hmm... Odd that you should >have lost lots of your headers... Points to disk corruption, or >something like that. > > -- Finlay > > >My mistake then. Please accept my apologies (especially Massimo.) It >looked to me like a "incomplete Dev Tools installation" problem and assumed >the Dec Tools were not installed. > >Hope you're able to get it going Massimo. > > Jeff > > > > > On Wednesday, January 16, 2002, at 03:41 pm, Hester, Jeffrey W. wrote: >> >> > It happened because the Dec version of the Dev Tools were NOT installed! >> > >> > That's why there is a FAQ on the Fink site about installing and what is >> > required *before* installing Fink. >> >> No, that's just plain wrong. The Developer Tools obviously were >> installed, just lots of the headers missing. >> > > -- Finlay > > -- -- Massimo Marino NERSC Division - HPC Department Lawrence Berkeley National Laboratory http://www.slac.stanford.edu/~marino Phone: 510.486.7695 Fax: 510.486.4004 _______________________________________________ Fink-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-users
