| Summary: | media-libs/libvpx-0.9.6 gets stuck on future timestamps in gcc | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | N. Andrew Walsh <n.andrew.walsh> |
| Component: | Current packages | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
| Status: | RESOLVED INVALID | ||
| Severity: | normal | ||
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| URL: | http://www.gentoo.org/doc/en/handbook/handbook-amd64.xml?part=1&chap=5#doc_chap1 | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
Fix your clock before you start chrooting and installing? :) The solution for you is to wait around 4 hours before you continue installing your favourite software. |
[DEP] vpx/src/vpx_decoder_compat.c.d [DEP] vpx/src/vpx_decoder.c.d make[1]: Warning: File `/usr/lib/gcc/x86_64-pc-linux-gnu/4.5.2/include-fixed/limits.h' has modification time 13501 s in the future [DEP] vp8/decoder/x86/x86_dsystemdependent.c.d that bit about modification times in the future causes this stage of the emerge (lots of lines with the [DEP] at the beginning) to repeat over and over. Forever. This is on a new system with ~amd64 and the latest snapshot. Reproducible: Always Steps to Reproduce: 1. install new system, get timestamps in the gcc subdirectories in the future 2. emerge libvpx 3. watch it go round and round Actual Results: emerge gets stuck on the error, and keeps trying over and over Expected Results: If incorrect timestamps is preventing the emerge from completing, it should fail gracefully.