stringify macro issue [was: Re: GCC 3.4.x + RTEMS 4.6.2 release.]

[Karel Gardas]

Hello,

I've found the reason why I had these strange issues with gcc3.2.3 and
rtems 4.6.2. I've found them since I've also started to have them with
rtems trunk and gcc3.4.3. The reason is that we write code like:

class Foo
{
....
    std::string stringify () const;
...

while RTEMS seems to define stringify macro:

     145
     146 #define stringify( _x ) # _x
     147

in file <target>/<bsp>/lib/include/rtems/system.h

which causes corruption of our definition to:

    std::string "" () const;

which is really uncompilable. :-)

Cheers,
Karel

On Thu, 13 Jan 2005, Karel Gardas wrote:

>
> Hello,
>
> since I have kind of strange issues with gcc3.2.3 as adviced to be used
> with 4.6.2 release in its documentation, I would like to ask if anybody
> here does have some experience with gcc 3.4.x with the latest RTEMS
> release. The patch gcc-3.4.0-rtems-20040510.diff on ftp.rtems.com looks
> really small. Does it means that every rtems related change against older
> gcc versions are already merged into the 3.4.x branch?
>
> Thanks,
> Karel
> --
> Karel Gardas                  kgardas at objectsecurity.com
> ObjectSecurity Ltd.           http://www.objectsecurity.com
>
>

--
Karel Gardas                  kgardas at objectsecurity.com
ObjectSecurity Ltd.           http://www.objectsecurity.com