On Thu, 28 Feb 2002, Martin Costabel wrote:

> "Brian W. Barrett" wrote:
>
> > cc -I/sw/include/gnome-1.0 -DNEED_GNOMESUPPORT_H -I/sw/lib/gnome-libs/include 
>-I/sw/include -I/sw/include/glib-1.2 -I/sw/lib/glib/include -I/sw/include/orbit-1.0 
>-I/sw/include/gtk-1.2 -I/usr/X11R6/include -I/sw/include/gnome-xml -I./.. -c 
>libglade-scan.c  -fno-common -DPIC -o .libs/libglade-scan.lo
> > libglade-scan.c:1317: bad macro argument list
>
> This looks so much the same as the error I got recently when I tried to
> rebuild gdk-pixbuf, that it must have the same cause. There the cause
> was (found by Peter O'Gorman) an incompatibility with the gtk-doc package.
>
> You could try to remove this package, or, if fink doesn't want to let
> you, move the file /sw/bin/gtkdoc-mkdb temporarily out of the way:
>
> sudo mv /sw/bin/gtkdoc-mkdb /sw/bin/gtkdoc-mkdb_away
>
> so that configure is led to believe that gtkdoc is not installed.
> Then rebuild libglade.

So, after much digging around, I think I found the problem.  The g_warning
macro is used all over libglade, but only caused problems on the docs
files, which are autogenerated from some magical program (I would prefer
to know as little about GNOME as possible - I just use it :).  Anyway, the
Fink info file sets CFLAGS to be -no-cpp-precomp, so all the source files
are compiled with that option.  However, the Makefile.am in the doc
directory of libglade overrides CFLAGS, so -no-cpp-precomp was not
specified when the libglade-scan.c file was attempted to be compiled.

I added -no-cpp-precomp to their list of CFLAGS and the entire thing
compiled.  Now, I only have a vague understanding of what -no-cpp-precomp
does or why it caused badness here, but since they were docs, I really
didn't worry about it all that much.

Brian

-- 
  Brian Barrett
  Graduate Student, Open Systems Lab, Indiana University
  http://www.osl.iu.edu/~brbarret/


_______________________________________________
Fink-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fink-users

Reply via email to