ruby compilation overcome

So...
it appears that if you compile ruby and get a "warning clock skew detected" that it
 may be due to your machine having a clock set for a certain time, and an nfs server being set 
for (say) one hour difference or not. Synchronize them and you're good 🙂
Thanks for all those information.

background:

BTW I am using a intel box having 8 processors, each one 2-way hyperthreaded. And yes, the File system id      NFS.

Thanks.
--------
Hemayet Hossain

Dan Gibson wrote:

This happens when you're compiling on a virtual machine, and your host machine supports dynamic frequency modulation. There is a fix to the issue... you can find it on google.

Mike Marty wrote:
While Make is doing its timestamp-based dependency check, the timestamps
on some of your files appeared to be in the future...hence the clock skew
detected message

It is not a GEMS thing.  Sounds like an issue on your host system.

--Mike

Hi All,
I was compiling ruby (gems 1.3) in simics 3.0.14. At the end of
compilation I am getting the following warning. (ruby seems working
fine). Does anybody know why is that coming or is there any potential
problem for that warning?
---------------------------------
Template closure done
Made module
make[1]: warning:  Clock skew detected.  Your build may be incomplete.
make[1]: Leaving directory `/home/vax2/u2/hossain/G3S364/ruby'
Ruby: Linking simics module
cd ../simics; make ruby
make[1]: Entering directory `/home/vax2/u2/hossain/G3S364/workspace'
=== Building module "ruby" ===
make[2]: Entering directory
`/home/vax2/u2/hossain/G3S364/workspace/amd64-linux/obj/modules/ruby'
make[2]: Warning: File
`/home/vax2/u2/hossain/G3S364/workspace/modules/../../ruby/amd64-linux/generated/MOSI_SMP_bcast/obj/util.d'
has modification time 51 s in the future
Using the Simics 3.0 API for ruby module
CCLD    ruby.so
make[2]: warning:  Clock skew detected.  Your build may be incomplete.
make[2]: Leaving directory
`/home/vax2/u2/hossain/G3S364/workspace/amd64-linux/obj/modules/ruby'
make[1]: Leaving directory `/home/vax2/u2/hossain/G3S364/workspace'
Ruby: Moving simics module
make BUILD_FLAGS=-DSIMICS movemodule
make[1]: Entering directory `/home/vax2/u2/hossain/G3S364/ruby'
../scripts/prepare_simics_home.sh ../simics/home/MOSI_SMP_bcast amd64-linux
make[1]: Leaving directory `/home/vax2/u2/hossain/G3S364/ruby'
Ruby: my work is done here...

Thanks.

2 thoughts on “ruby compilation overcome”

  1. -bash-3.00$ sudo python setup.py install
    running install
    running build
    running build_py
    creating build
    error: could not create ‘build’: Permission denied
    -bash-3.00$ chmod a+rwx * -R
    -bash-3.00$ sudo python setup.py install
    running install
    running build
    running build_py
    creating build
    error: could not create ‘build’: Permission denied
    -bash-3.00$ python setup.py install
    running install

    overcome by running python setup.py build && sudo python setup.py install

  2. make[1]: Leaving directory `/misc/webstage/roger/blender/install_files/ruby-1.8.6′
    doing exec sudo make install
    /bin/sh: .installed.list: No such file or directory
    make: *** [install-prereq] Error 1
    ERROR sudo make install appeared to not work!

    when isntalling ruby? no worries, make the directory ‘global writable’ and then sudo can write to it — make sure to change it back after, if worried about security
    ./configure
    make install
    chmod -R a+rwx .
    sudo make install
    good luck!

Leave a Reply

Your email address will not be published. Required fields are marked *

Time limit is exhausted. Please reload the CAPTCHA.