ntp FTBFS: error: 'MOD_NANO' undeclared

Bug #412242 reported by Jamie Strandboge on 2009-08-11
This bug affects 2 people
Affects Status Importance Assigned to Milestone
ntp (Ubuntu)
Jamie Strandboge

Bug Description

Binary package hint: ntp

ntp no longer builds on karmic:

gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I.. -I../include -I../include -I../libopts -D_GNU_SOURCE -I/usr/include -g -fno-strict-aliasing -O2 -Wall -Wcast-qual -Wmissing-prototypes -Wpointer-arith -Wshadow -Wstrict-prototypes -c ntp_loopfilter.c
ntp_loopfilter.c: In function 'local_clock':
ntp_loopfilter.c:571: error: 'MOD_NANO' undeclared (first use in this function)
ntp_loopfilter.c:571: error: (Each undeclared identifier is reported only once
ntp_loopfilter.c:571: error: for each function it appears in.)
ntp_loopfilter.c: In function 'loop_config':
ntp_loopfilter.c:896: error: 'MOD_NANO' undeclared (first use in this function)
make[4]: *** [ntp_loopfilter.o] Error 1
make[3]: *** [all] Error 2
make[2]: *** [all-recursive] Error 1
make[1]: *** [all] Error 2
make: *** [build-stamp] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2

This patch should fix the issue:

Changed in ntp (Ubuntu):
assignee: nobody → Jamie Strandboge (jdstrand)
importance: Undecided → Critical
status: New → In Progress
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package ntp - 1:4.2.4p6+dfsg-1ubuntu3

ntp (1:4.2.4p6+dfsg-1ubuntu3) karmic; urgency=low

  * Add enforcing AppArmor profile (LP: #382905)
    - debian/control: add Conflicts/Replaces on apparmor-profiles <
      2.3.1+1403-0ubuntu10 (since we are now shipping usr.sbin.ntpd) and
      apparmor < 2.3.1+1403-0ubuntu10 (since we are now shipping
    - debian/control: add Suggests on apparmor
    - debian/ntp.dirs: add apparmor directories
    - debian/ntp.preinst: force complain on certain upgrades
    - debian/ntp.postinst: reload apparmor profile
    - debian/ntp.postrm: remove the force-complain file
    - add debian/apparmor-profile*
    - debian/rules: install apparmor-profile and apparmor-profile.tunable
    - debian/README.Debian: add note on AppArmor
  * debian/patches/fix-nano.patch: enable nanokernel support (LP: #412242)

 -- Jamie Strandboge <email address hidden> Tue, 11 Aug 2009 18:25:50 -0500

Changed in ntp (Ubuntu):
status: In Progress → Fix Released
summary: - ntp FTBFS
+ ntp FTBFS: error: 'MOD_NANO' undeclared
Jamie Strandboge (jdstrand) wrote :

Ubuntu 9.10 should be ok with the applied patch, because kernels after 2.6.26 are nanokernels (ie, they have STA_NANO available). However, according to Debian maintainer Kurt Roeckx, using this patch on a non-nano kernel (eg Hardy) may have some odd side-effects. If people are backporting Karmic's ntp to Ubuntu 8.04 LTS, they should be aware of this issue.

An alternate patch that checks if the kernel supports nano seconds or not is at:

Jamie Strandboge (jdstrand) wrote :

One more link for more context:

Jamie Strandboge (jdstrand) wrote :

Actually, this should not be a problem with a backport, as the will require recompile. The problem comes when the binary compiled for a nanokernel is used on a non-nano kernel.

Rich Wales (richw) wrote :

Has this bug really been fixed? I have a system running karmic, and I just upgraded everything, and /usr/include/sys/timex.h (dated 2009-10-07, with "definitions from linux/timex.h as of 2.6.30") still does not contain a definition of MOD_NANO.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.