chrony: FEAT_RTC not defined by configure (l: 248, 249)
Bug #292590 reported by
Martin
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| chrony (Ubuntu) |
Expired
|
Undecided
|
Unassigned | ||
Bug Description
Binary package hint: chrony
running sh compatible, configure script fails to define FEAT_RTC macro by += operator
lines affected: 248, 249
symptom:
chronyd fails to recognize operating system's real time clock support by logging on startup:
"Real time clock not supported on this operating system"
Revision history for this message
| Christian Ehrhardt (paelzer) wrote | #1 |
| Changed in chrony (Ubuntu): | |
| status: | New → Incomplete |
Revision history for this message
| Launchpad Janitor (janitor) wrote | #2 |
| Changed in chrony (Ubuntu): | |
| status: | Incomplete → Expired |
To post a comment you must log in.
Hi Vladim,
I worked on Chrony in 18.04 and it is quite good now IMHO.
Given that 10.04 is EOL for quite some time I'll mark this bug incomplete.
Please if you still have/find an issue in it these days please let us know.
It will unlikely be the same bug, so if you do I'd recommend you open a new bug for those.