Bugzilla Bug 89478

Emerging courier-imap on gentoo system, errors out with the following message:

hecking fam.h usability... no
checking fam.h presence... no
checking for fam.h... no
checking for symlink... yes
checking for readlink... yes
checking for strcasecmp... yes
checking for utime... yes
checking for utimes... yes
checking for FAMOpen in -lfam... yes
checking for fam.h... (cached) no
configure: WARNING: The development header files and libraries for fam,
configure: WARNING: the File Alteration Monitor, are not installed.
configure: WARNING: You appear to have the FAM runtime libraries installed,
configure: WARNING: so you need to simply install the additional development
configure: WARNING: package for your operating system.
configure: error: FAM development libraries not found.
configure: error: /bin/sh './configure' failed for maildir

I re-emerged the fam package.
/usr/include/fam.h DOES exist




Reproducible: Always
Steps to Reproduce:
1.
2.
3.

*** Bug 89480 has been marked as a duplicate of this bug. ***

emerge info, and please tell if you have fam or gamin installed.
Also attach config.log to the bug.

fam is installed (2005.0 stage-3 install)

Emerge info:

Portage 2.0.51.19 (default-linux/amd64/2005.0, gcc-3.4.3, glibc-2.3.4.20041102-r1, 2.6.11-gentoo-r1 x86_64)
=================================================================
System uname: 2.6.11-gentoo-r1 x86_64 AMD Athlon(tm) 64 Processor 3200+
Gentoo Base System version 1.4.16
Python:              dev-lang/python-2.3.4-r1 [2.3.4 (#1, Apr 16 2005, 12:27:53)]
dev-lang/python:     2.3.4-r1
sys-devel/autoconf:  2.59-r6, 2.13
sys-devel/automake:  1.7.9-r1, 1.8.5-r3, 1.5, 1.4_p6, 1.6.3, 1.9.4
sys-devel/binutils:  2.15.92.0.2-r7
sys-devel/libtool:   1.5.14
virtual/os-headers:  2.6.8.1-r4
ACCEPT_KEYWORDS="amd64"
AUTOCLEAN="yes"
CFLAGS="-march=k8 -pipe -fomit-frame-pointer -O2"
CHOST="x86_64-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.3/env /usr/kde/3.3/share/config /usr/kde/3.3/shutdown /usr/kde/3/share/config /usr/lib/X11/xkb /usr/share/config /var/bind /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d"
CXXFLAGS="-march=k8 -pipe -fomit-frame-pointer -O2"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoaddcvs autoconfig ccache distlocks sandbox strict"
GENTOO_MIRRORS="http://distfiles.gentoo.org http://distro.ibiblio.org/pub/Linux/distributions/gentoo"
MAKEOPTS="-j2"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="amd64 OSS X acpi alsa bash-completion berkdb bitmap-fonts cdr crypt cups curl esd fam flac font-server fortran gif gpm gtk imlib ipv6 java jp2 jpeg kde lzw lzw-tiff motif mp3 mysql ncurses nls ogg opengl oss pam perl png python qt readline samba sdl ssl tcltk tcpd tiff truetype truetype-fonts type1-fonts usb userlocales xml2 xpm xrandr xv zlib"
Unset:  ASFLAGS, CBUILD, CTARGET, LANG, LC_ALL, LDFLAGS, LINGUAS, PORTDIR_OVERLAY

Created an attachment (id=56599) [edit]
config.log file from attempted build of courier-imap

please attach config.log in maildir/

This also happends with courier .

Okay guys, I managed to get it to compile right and it seems to be working
sweet as. Seems like configure can't find the fam.h file, but what is actually
happening is this 

fam.h includes limits.h
limits.h includes the 64bit limits.h
(/usr/include/gentoo-multilib/amd64/limits.h)
amd64/limits.h attempts to include the compilers limits.h
(/usr/lib64/gcc/x86_64-pc-linux-gnu/3.4.3/include/limits.h)

but for some reason it can't find the file

In file included from /usr/include/limits.h:7,
                 from /usr/include/fam.h:44,
                 from conftest.c:69:
/usr/include/gentoo-multilib/amd64/limits.h:124:26: no include path in which to
search for limits.h

To get it to work I just modified my 64bit limits.h file to specifically
include the compilers limits.h file

#if defined __GNUC__ && !defined _GCC_LIMITS_H_
/* `_GCC_LIMITS_H_' is what GCC's file defines.  */
/* # include_next <limits.h> */
# include_next </usr/lib64/gcc/x86_64-pc-linux-gnu/3.4.3/include/limits.h>

After that it seemed to work fine, although I've changed it back after the
emerge just in case it breaks something else :D

Hope this helps

It looks like amd64 issue. Reassign.

Interresting, missed that it was marked amd64.
My problem is with a dual Pentium 3.
linux-headers-2.6.11 , if that helps you :)

I'm getting a different error on x86 using linux-headers-2.6.11
Just create a basic C file and #include <fam.h> and you get

In file included from /usr/include/limits.h:124,
                 from /usr/include/limits.h:124,
                 from /usr/include/limits.h:124,
   for ages and finally
                from /usr/include/fam.h:44,
                 from x.c:1:
/usr/include/limits.h:124:26: error: #include nested too deeply

Easiet fix is to change line 44 of /usr/include/fam.h
#include "limits.h"
to
#include <limits.h>

With that fix in place, fam, courier-imap, courier-authlib, maildrop and mod_php still compile and work fine.

Assigning to foser as he owns the fam package

Created an attachment (id=58214) [edit]
fixes fam.h to #include <limits.h> instead of #include "limits.h"

please apply & close Roy. Thanks.

Fixed in fam-2.7.0-r4

*** Bug 100948 has been marked as a duplicate of this bug. ***

*** Bug 104501 has been marked as a duplicate of this bug. ***

Yes, it worked. Thumbs up for resolution Turnaround time! 

*** Bug 104973 has been marked as a duplicate of this bug. ***

*** Bug 105317 has been marked as a duplicate of this bug. ***

*** Bug 105606 has been marked as a duplicate of this bug. ***

*** Bug 106585 has been marked as a duplicate of this bug. ***

*** Bug 106798 has been marked as a duplicate of this bug. ***

*** Bug 106730 has been marked as a duplicate of this bug. ***

*** Bug 110527 has been marked as a duplicate of this bug. ***

*** Bug 111905 has been marked as a duplicate of this bug. ***

*** Bug 113656 has been marked as a duplicate of this bug. ***

Someone needs to move on bringing fam 2.7.0-r4 into stable.  This problem was
reported and supposedly resolved back in May, and fam stable is still at
2.7.0-r2 for amd64, which has the problem described (and resolved) here.  Foser?
 'zat your department ??

I just did another amd64 install and tripped on the same problem again, although
emerging fam unstable fixes it.

*** Bug 114502 has been marked as a duplicate of this bug. ***

*** Bug 116353 has been marked as a duplicate of this bug. ***

*** Bug 116527 has been marked as a duplicate of this bug. ***