Thomas 'Balu' Walter �����(�):
>
> [shortened]
> +-Kir Kolyshkin-([EMAIL PROTECTED])-[25.06.01 11:45]:
> > > I've tried to configure on a SuSE-7.0 and a Debian-2.2.r3 with
> > >
> > > --with-openssl --enable-charset-guesser --enable-font-size
> > >
> > > which breaks at:
> > > ...
> > > c++ -DHAVE_CONFIG_H -I. -I. -I../include -g -O2 -D_REENTRANT -c
> > > parse.cpp^M
> > > In file included from parse.cpp:51:^M
> > > ../include/parse.h:180: macro `Free' used without args^M
> > > ../include/parse.h:197: macro `Free' used without args^M
> > > parse.cpp:166: macro `Free' used without args^M
> > > parse.cpp:1736: macro `Free' used without args^M
> > > make[2]: *** [parse.o] Error 1^M
> > > make[2]: Leaving directory `/home/balu/tmp/aspseek-1.2.3/src'^M
> > > make[1]: *** [all-recursive] Error 1^M
> > > make[1]: Leaving directory `/home/balu/tmp/aspseek-1.2.3/src'^M
> > > make: *** [all-recursive] Error 1^M
> >
> > Can you try editing src/parse.cpp and move the include lines
> > surrounded by #ifdef USE_HTTPS/#endif below the local includes,
> > so it will look like this:
> [...]
> > Please try and report your results :)
>
> Okay, I've changed the order and redid
> ./configure --with-openssl --enable-charset-guesser --enable-font-size &&
> make
>
> Same error:
> c++ -DHAVE_CONFIG_H -I. -I. -I../include -g -O2 -D_REENTRANT -c
> parse.cpp
> parse.cpp:166: macro `Free' used without args
> parse.cpp:1736: macro `Free' used without args
>
> I guess, it's because Free is defined as
> #define Free(addr) free(addr)
> in openssl/crypto.h
>
> Now I wonder why you do a Free(); at all - for me it looks like it does
> nothing? Or did you forget to include the address to free?
This is actually CUrl::Free() method (defined in parse.h:180)
By the way, my OpenSSL installation don't define Free macros,
maybe you have old version. Anyway, defining such a generic
macro in public include file is braindamaged idea...so they
should fix it, and I believe they did (I have OpenSSL-0.9.6)
>
> While doing that, I noticed, that the source-file contain many ^Ms (just
> as in my typescript-log above). That looks like the file was edited on a
> DOS-Machine and not converted correctly (DOS uses CR/LF-combination,
> while Unix just uses LF). My own experiences show that this sometimes makes
> problems too - you might want to convert the files.
Well I thought I do...will check it.
>
> [second problem]
> > Well, this is probably because of broken compiler. Try to upgrade
> > gcc to 2.95.3 - this should help.
>
> Actually it was the problem - I know have a debian-testing-distribution,
> because I was to lazy to do that manually...
>
> > -- [EMAIL PROTECTED] http://kir.sever.net ICQ 7551596 --
>
> You might want to introduce your sig by "-- " which is "dash dash blank
> return" - and which is the "original" sig-intro.
>
> Balu
-- [EMAIL PROTECTED] http://kir.sever.net ICQ 7551596 --
Bend the facts to fit the conclusion. It's easier that way.
-- |_ | |\| |_| >< -- |_| |\| | >< -- | ) |\/| --
