sourcecode mtime discrepancy?
I'm not familiar with the intricacies of installing from a server --> client PC (is that a net-install?), however I have seen the 'clock skew' error before when building stuff from source. It happens when there is a (large) discrepancy between the system clock time and the mtime (modification time) of the source code; for example, the system detects that the source code is future-dated.
If indeed you are/were building from source, try entering the source directory and running the `autoconf` or `autoreconf` command/script, which should correct the mtime discrepancy of the source files. Then, try building the code.
Does this help?
Last edited by GrapefruiTgirl; 06-22-2009 at 08:56 AM.