Bug 25064

Summary: Problem compiling poppler 0.12.1
Product: poppler Reporter: Pierre <pierre42d>
Component: glib frontendAssignee: poppler-bugs <poppler-bugs>
Status: RESOLVED DUPLICATE QA Contact:
Severity: normal    
Priority: medium    
Version: unspecified   
Hardware: x86 (IA32)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:

Description Pierre 2009-11-12 17:07:25 UTC
# make
make  all-recursive
make[1]: Entering directory `/tmp/poppler-0.12.1'
Making all in goo
make[2]: Entering directory `/tmp/poppler-0.12.1/goo'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/tmp/poppler-0.12.1/goo'
Making all in fofi
make[2]: Entering directory `/tmp/poppler-0.12.1/fofi'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/tmp/poppler-0.12.1/fofi'
Making all in splash
make[2]: Entering directory `/tmp/poppler-0.12.1/splash'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/tmp/poppler-0.12.1/splash'
Making all in poppler
make[2]: Entering directory `/tmp/poppler-0.12.1/poppler'
make  all-am
make[3]: Entering directory `/tmp/poppler-0.12.1/poppler'
make[3]: Nothing to be done for `all-am'.
make[3]: Leaving directory `/tmp/poppler-0.12.1/poppler'
make[2]: Leaving directory `/tmp/poppler-0.12.1/poppler'
Making all in utils
make[2]: Entering directory `/tmp/poppler-0.12.1/utils'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/tmp/poppler-0.12.1/utils'
Making all in glib
make[2]: Entering directory `/tmp/poppler-0.12.1/glib'
make  all-recursive
make[3]: Entering directory `/tmp/poppler-0.12.1/glib'
Making all in .
make[4]: Entering directory `/tmp/poppler-0.12.1/glib'
/bin/sh ../libtool  --tag=CC   --mode=compile gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I.. -I../poppler -DG_LOG_DOMAIN=\"Poppler\" -I.. -I../poppler  -I/usr/local/include/glib-2.0 -I/usr/local/lib/glib-2.0/include   -I/usr/local/include/gtk-2.0 -I/usr/local/lib/gtk-2.0/include -I/usr/local/include/pango-1.0 -I/usr/local/include/glib-2.0 -I/usr/local/lib/glib-2.0/include -I/usr/local/include/cairo   -I/usr/local/include/freetype2 -I/usr/local/include   -I/usr/local/include    -DG_DISABLE_DEPRECATED -DGDK_DISABLE_DEPRECATED -DGDK_PIXBUF_DISABLE_DEPRECATED -DG_DISABLE_SINGLE_INCLUDES -DGTK_DISABLE_SINGLE_INCLUDES    -s -O3 -march=i686 -MT poppler-enums.lo -MD -MP -MF .deps/poppler-enums.Tpo -c -o poppler-enums.lo poppler-enums.c
libtool: compile:  gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I.. -I../poppler -DG_LOG_DOMAIN=\"Poppler\" -I.. -I../poppler -I/usr/local/include/glib-2.0 -I/usr/local/lib/glib-2.0/include -I/usr/local/include/gtk-2.0 -I/usr/local/lib/gtk-2.0/include -I/usr/local/include/pango-1.0 -I/usr/local/include/glib-2.0 -I/usr/local/lib/glib-2.0/include -I/usr/local/include/cairo -I/usr/local/include/freetype2 -I/usr/local/include -I/usr/local/include -DG_DISABLE_DEPRECATED -DGDK_DISABLE_DEPRECATED -DGDK_PIXBUF_DISABLE_DEPRECATED -DG_DISABLE_SINGLE_INCLUDES -DGTK_DISABLE_SINGLE_INCLUDES -s -O3 -march=i686 -MT poppler-enums.lo -MD -MP -MF .deps/poppler-enums.Tpo -c poppler-enums.c  -fPIC -DPIC -o .libs/poppler-enums.o
In file included from /usr/local/include/gtk-2.0/gdk/gdkspawn.h:26,
                 from /usr/local/include/gtk-2.0/gdk/gdk.h:52,
                 from poppler-page.h:27,
                 from poppler.h:121,
                 from poppler-action.h:23,
                 from poppler-enums.c:9:
/usr/local/include/glib-2.0/glib/gspawn.h:22:2: error: #error "Only <glib.h> can be included directly."
make[4]: *** [poppler-enums.lo] Error 1
make[4]: Leaving directory `/tmp/poppler-0.12.1/glib'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory `/tmp/poppler-0.12.1/glib'
make[2]: *** [all] Error 2
make[2]: Leaving directory `/tmp/poppler-0.12.1/glib'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/tmp/poppler-0.12.1'
make: *** [all] Error 2
Comment 1 Carlos Garcia Campos 2009-11-15 02:34:57 UTC
Yes, this is a suplicate of bug #22090. Thanks for reporting. 

*** This bug has been marked as a duplicate of bug 22090 ***

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.