next message in archive
no next message in thread
previous message in archive
previous message in thread
Index of Subjects
Index of Subjects On Sun, 4 May 1997, John Nemeth wrote: > Actually, I have seen this problem as well. In one of my build > attempts, I ran out of diskspace. I restarted ./csbuild and specified > a different $CS_ROOT. It blew up, because not everything got > unpacked. I ended up downloading a new copy of the distribution and > tucking it away in a seperate directory. On each build attempt, I > would blow away $CS_DIST and make a copy of it from my stash > directory. I have noted this problem before. Well this is the same problem, having a partially installed CSuite and then getting a fresh one to install over it. Aparently, it doesn't have to be a new dist. All I know is that if you run ./csbuild then /usr/src/csuite-1.0 will have a number of files and directories created. My guess, when you run the make it checks if the files are there already. If you get a new dist then the files created from the first make would be there and the new make is recognizing that they are not the same files and assumes that it hasn't been made, but then tries to write stuff with the same file name and gets into trouble. A similar thing would happen if you were to change $CS_ROOT, it wouldn't find the files because they won't be in the same directory. Then it writes stuff to /usr/src/csuite-1.0 with the same file name. The reason why I consider it a "non-bug" is because both circumstances are out of the ordinary. The first cause is because of trying to install a newer dist over an older one (something you normally won't try, might turn into a problem with upgrades). The other cause is by changing $CS_ROOT which would probably only occur if you ran out of space, which is why the new install docs include a partitioning scheme which will help ensure that csuite has enough space to breathe. If the problem does seem to be more common then it will be documented and we will search for any possible fixes. I hope that this makes sense. The basic problem seems to be that make wants to write files into /usr/src/csuite-1.0 if the file has not been done already. When there are newer versions of the file or the files are in another directory then make thinks that the files weren't created and then writes its files to /usr/src/csuite-1.0, which tries to overwrite files with the same name (from the previous make). ========================================================================= Andrew Dacey ac213@chebucto.ns.ca CSuite Installation Co-ordinator, http://www.chebucto.ns.ca/~ac213/ Chebucto Community Net 455-6195 hm, 494-2449 wk =========================================================================
next message in archive
no next message in thread
previous message in archive
previous message in thread
Index of Subjects