Am 15.05.2014 um 12:57 schrieb Joerg Schilling <[email protected]>:
> slowfranklin <[email protected]> wrote: > >> Hi guys and a cheerio from SambaXP! >> >> I'm working on a poppler update and noticed that compilation spits out lot >> of LFS related warning: >> >> ---8<--- >> In file included from poppler-private.h:4:0, >> from poppler-form-field.cc:22: >> ../config.h:262:0: warning: "_FILE_OFFSET_BITS" redefined >> #define _FILE_OFFSET_BITS 64 >> ^ >> In file included from /usr/include/limits.h:17:0, >> from >> /opt/csw/lib/gcc/i386-pc-solaris2.10/4.9.0/include-fixed/limits.h:168, >> from >> /opt/csw/lib/gcc/i386-pc-solaris2.10/4.9.0/include-fixed/syslimits.h:7, >> from >> /opt/csw/lib/gcc/i386-pc-solaris2.10/4.9.0/include-fixed/limits.h:34, >> from /opt/csw/lib/glib-2.0/include/glibconfig.h:11, >> from /opt/csw/include/glib-2.0/glib/gtypes.h:32, >> from /opt/csw/include/glib-2.0/glib/galloca.h:32, >> from /opt/csw/include/glib-2.0/glib.h:30, >> from /opt/csw/include/glib-2.0/gobject/gbinding.h:28, >> from /opt/csw/include/glib-2.0/glib-object.h:23, >> from poppler.h:22, >> from poppler-form-field.cc:21: >> /opt/csw/lib/gcc/i386-pc-solaris2.10/4.9.0/include-fixed/sys/feature_tests.h:196:0: >> note: this is the location of the previous definition >> #define _FILE_OFFSET_BITS 32 >> ^ >> ---8<--- >> >> poppler uses the autoconf macro for enabling LFS support so things should >> just work afaict. > > _FILE_OFFSET_BITS must be (if ever) set one before including any system > include > file. > > This OSS is aparently broken as it first includes system include files and > later includes it's config.h. This OSS is Solaris 10 on the buildfarm. :) -bash-4.3$ hostname unstable10x -bash-4.3$ uname -a SunOS unstable10x 5.10 Generic_147441-19 i86pc i386 i86pc -bash-4.3$ Turned out the poppler guys simply fail to properly include config.h in all places. Stuffing _FILE_OFFSET_BITS=64 in its throat from gar fixes it. Cheers! -slow
