Hi.
Just had a talk with my resident GCC guru, and his suggestion (which seems to work for
me) is to #define the functions as nothing, i.e.
#define func_name(a)
thats it. nothing after that. now GCC is happy :-)
--
Oded Arbel
m-Wise Mobile Solutions
[EMAIL PROTECTED]
Mobile: +972-67-340014
Tel: +972-9-9581711 (ext: 116)
::..
The President publicly apologized today to all those offended by his brother's remark,
"There's more Arabs in this country than there is Jews!". Those offended include
Arabs, Jews, and English teachers.
-- Baltimore, Channel 11 News, on Jimmy Carter
> -----Original Message-----
> From: Stipe Tolj [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, June 13, 2002 3:00 PM
> To: Oded Arbel
> Cc: Kannel-devel (E-mail)
> Subject: Re: Kannel automatic compilation test for SunOS
>
>
> Oded Arbel wrote:
> >
> > Hi list.
> > The definitions for the gw_mem calls in malloc=native mode
> result in lots of compilation warning - would it be possible
> to #define those in such a way as to completly be ignored by
> the compiler ? as gcc doesn't like the meaningles statements
> created by the current #defines.
>
> Hmm, I played around a bit to solve this, but this seems to be more
> tricky then I thought of.
>
> Anyone having an idea for this one?
>
> Stipe
>
> [EMAIL PROTECTED]
> -------------------------------------------------------------------
> Wapme Systems AG
>
> Vogelsanger Weg 80
> 40470 D�sseldorf
>
> Tel: +49-211-74845-0
> Fax: +49-211-74845-299
>
> E-Mail: [EMAIL PROTECTED]
> Internet: http://www.wapme-systems.de
> -------------------------------------------------------------------
> wapme.net - wherever you are
>
