> On Tue, Nov 19, 2002 at 11:55:35AM +0100, midan23_at_gmx.de wrote:
> > > On Tue, Nov 12, 2002 at 05:59:28PM -0800, Denis Perelyubskiy wrote:
> > > > * <dominik.vogt_at_gmx.de> [12-Nov-02 17:55 -0800]:
> > > > >
> > > > >On Mon, Nov 11, 2002 at 10:02:36AM +0100, midan23_at_gmx.de wrote:
> > > > >> Hi,
> > > > >>
> > > > >> I tried to compile fvwm (version 2.4.13) on my Mac
> > > > >> (Mac OS X 10.2.1, Compiler is gcc 3.1) and I got an
> > > > >> error ...
> > > > >>
> > > > >> Here is the output :
> > > > >> menus.c:240: illegal expression, found 'void'
> > > > >> fvwm.h:120: parse error in conditional expression
> > > > >>
> > > > >> It seems to me that the preprozessor doesn't like
> > > > >> #if RETSIGTYPE != void
> > > > >>
> > > > >> What can I do to compile fvwm ?
> > > > >> (And please, don't tell me that I should update my compile, I
> can't
> > > do it
> > > > >
> > > > >Well, if upgrading is out of the question, how about downgrading?
> > > > >Are you maybe running a broken cpp? Is it definitely the one
> that
> > > > >comes with gcc?
> > > > [...]
> > > >
> > > > I know next to nothing about the way fvwm is built (I know
> > > > it works when I ./configure/make it :) ), but it seems that
> > > > RETSIGTYPE is defined in config.h. Is that file dynamically
> > > > generated?
> > > >
> > > > I could see how if that file is not present (or is for some
> > > > reason wrong) and RETSIGTYPE is not defined, you'd get an
> > > > error message, since preprocessor would see something like
> > > > #if != void
> > >
> > > Then it should stop compiling when it reaches the
> > >
> > > #include "config.h"
> > >
> > > line.
> >
> > thanks for your help ...
> >
> > I made it simple, I played preprocessor ...
> > I looked in config.h, found that RETSIGTYPE was defined as void and
> replaced
> > the corresponding lines in fvwm/fvwm.h.
> > Now the line looks like "#define SIGNAL_RETURN return"
> >
> > After that little change, I can run make ...
> >
> > ... but I get another error :
> >
> > Compiling of FvwmBacker stops with an error about undefined symbols :
> >
> > gcc -g -O2 -o FvwmBacker FvwmBacker.o root_bits.o -L../../libs
> > -L/usr/X11R6/lib -lfvwm -lXpm -lSM -lICE -lXext -lX11 -lm
> > ld: Undefined symbols:
> > _Pcmap
> > _Pdepth
> > _Pdpy
> > _Pvisual
> > make[3]: *** [FvwmBacker] Error 1
> > make[2]: *** [all-recursive] Error 1
> > make[1]: *** [all-recursive] Error 1
> > make: *** [all-recursive-am] Error 2
> >
> > What can I do here ?
> >
> > (My goal is to write a little howto for compiling Fvwm 2.4.13 on Mac Os
> X
> > version 10.2.2 ...)
>
> Really, I think all you can do is to switch to a working compiler
> and report the bugs to the gcc crew.
>
> Bye
>
> Dominik ^_^ ^_^
>
I know two things :
1) The actual version of gcc is 3.2
2) The version 3.1 for Mac Os X 10.2.2 is part of the devlopper tools ...
I don't know if it is possible to simpy upgrade gcc to 3.2 ...
And reporting Bugs ... not really a solution. Here's the result of gcc -v
Reading specs from /usr/libexec/gcc/darwin/ppc/3.1/specs
Thread model: posix
Apple Computer, Inc. GCC version 1161, based on gcc version 3.1 20020420
(prerelease)
--
Frederic Gobin
Georg-Wopfner-Str. 58
80939 Muenchen
Telefon : 089 / 32 36 91 13
Handy : 0170 / 804 68 52
eMail : mailto:midan23_at_gmx.de
--
Visit the official FVWM web page at <URL: http://www.fvwm.org/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_fvwm.org.
To report problems, send mail to fvwm-owner_at_fvwm.org.
Received on Tue Nov 19 2002 - 06:03:29 GMT