On Fri, Jun 09, 2000 at 07:08:59PM +1000, Andrew Lister wrote:
> Alexander Mai writes
> >gcc -DHAVE_CONFIG_H -I. -I. -I../include -I./../include -I../include
> >-I../../../include/Motif-1.2 -I../../../include/Motif-1.2
>-I../../../include/Motif-1.2
> >-I../../../include/Motif-1.2 -I/usr/local/include -I/usr/X11R6/include -g -O2 -Wall
>-c
> >-fPIC -DPIC Actions.c -o Actions.lo
> >In file included from ../../../include/Motif-1.2/Xm/TextInP.h:29,
> > from ../../../include/Motif-1.2/Xm/TextP.h:31,
> > from ../include/Xbae/Macros.h:44,
> > from ../include/Xbae/Draw.h:38,
> > from Actions.c:45:
> >../../../include/Motif-1.2/Xm/TextStrSoP.h:36: conflicting types for `EditDone'
> >/usr/local/include/Xm/Xm.h:2867: previous declaration of `EditDone
>
> You might like to try a 'make depend' before building (if configure
> supports it)
As I mentioned it was the lazy approach, configure w/o arguments, etc.
Initially I thought one could at least detect this by adding
a check to configure. But the 'accident' described above
won't happen with all combinations of LessTif/Motif.
Currently I don't know how to detect a non-matching Xm.h WRT
to the other headers.
So one had to do some explicit test for the Xm.h probably.
These -I../../../include/Motif-1.2 seem to be hardcoded
and should be addressed before a major new release of libXbae
is done.
--
Alexander Mai
[EMAIL PROTECTED]
