xpdf, new gcc?

Bruce Dubbs bruce.dubbs at gmail.com
Thu Feb 15 11:17:16 PST 2007


On 2/15/07, Ken Moffat <ken at linuxfromscratch.org> wrote:
>  This is on a multilib build, using the second gcc-4.1.2 release
> candidate.  I don't think the multilib part is relevant, so I'll
> take the risk of asking here.  Xpdf (3.01pl2) is failing to compile
> with (lines wrapped)
>
> g++ -m32 -O2 -DHAVE_CONFIG_H -I.. -I./../goo -I./../fofi
> -I./../splash -I. -I/usr/include/freetype2          -DHAVE_XPDFCORE
> -c -o SecurityHandler.x.o \
>                 SecurityHandler.cc
> /usr/include/X11/VendorP.h:87: error: previous declaration of
> 'VendorShellClassRec vendorShellClassRec' with 'C++' linkage
> /usr/include/Xm/VendorSP.h:58: error: conflicts with new declaration
> with 'C' linkage
> make[1]: *** [SecurityHandler.x.o] Error 1
> make[1]: Leaving directory `/usr/src/xpdf-3.01/xpdf'
> make: *** [all] Error 2
>
>  As far as I can see, the header hasn't changed since I last built
> xpdf:
>
> typedef struct _VendorShellClassRec {
>         CoreClassPart      core_class;
>         CompositeClassPart composite_class;
>         ShellClassPart  shell_class;
>         WMShellClassPart   wm_shell_class;
>         VendorShellClassPart vendor_shell_class;
> } VendorShellClassRec;
>
> externalref VendorShellClassRec vendorShellClassRec;
>
>  line 87 is the 'externalref'.
>
> Any suggestions, please?

If VendorShellClassRec is defined twice, what happens if the local one
is commented out?  The easiest way I can see if to comment out line 87
and see if that fixes things.

Note: I may not be understanding the whole thing here.  I'm jsut
throwing out ideas.
  -- Bruce

  -- Bruce



More information about the blfs-support mailing list