Re: [Boost-users] [xpressive] compilation woes with gcc 3.3.3

From: Mike Marchywka (marchywka_at_[hidden])
Date: 2008-06-02 13:53:03

> Sorry, my gcc-3.3.3 build failed with:

I think when I went through my first boost effort, I ended up getting an odd runtime
problem ( unable to catch an exception ) until I switched compilers from the cygwin 3.3 version.
I'm just pointing this out in case it is relevant and makes the effort you are discussing
futile ( so it compiles but can't be reasonably made to run).

Mike Marchywka
586 Saint James Walk
Marietta GA 30067-7165
404-788-1216 (C)<- leave message
989-348-4796 (P)<- emergency only
marchywka_at_[hidden]
Note: If I am asking for free stuff, I normally use for hobby/non-profit
information but may use in investment forums, public and private.
Please indicate any concerns if applicable.
Note: Hotmail is possibly blocking my mom's entire
ISP - try  me on marchywka_at_[hidden] if no reply
here. Thanks.

> Date: Mon, 2 Jun 2008 10:21:37 -0700
> From: eric_at_[hidden]
> To: boost-users_at_[hidden]
> Subject: Re: [Boost-users] [xpressive] compilation woes with gcc 3.3.3
>
> Eric Niebler wrote:
>> Christoph Duelli wrote:
>>> Ok, checked it:
>>> I did indeed #ifdef out the lines stated in the last post.
>>>
>>> As I have said, the above two sections in regex_actions.hpp cause trouble.
>>> Even including regex_actions.hpp causes the compiler to choke on it.
>>> (see gcc-out1.txt for compiling just the header *with* these sections not
>>> #ifdef'ed out.
>>> )
>> 
>>
>> I can't tell from the logs. I'm building gcc-3.3.3 now and will
>> investigate when that's done.
>
> Sorry, my gcc-3.3.3 build failed with:
>
> ../../gcc-3.3.3/gcc/gcc.c: In function `process_command':
> ../../gcc-3.3.3/gcc/gcc.c:3609: error: assignment of read-only location
> ../../gcc-3.3.3/gcc/gcc.c:3611: error: assignment of read-only location
>
> I'm giving up now. If you would like to pursue this, I would suggest you
> preprocess your test first and then reproduce the error. The line
> indicated by the error message contains a macro expansion. The error is
> somewhere in there. If you track it down and find a workaround, I'll
> gladly accept a patch.
>
> Good luck,
>
> --
> Eric Niebler
> Boost Consulting
> www.boost-consulting.com
> _______________________________________________
> Boost-users mailing list
> Boost-users_at_[hidden]
> http://lists.boost.org/mailman/listinfo.cgi/boost-users

_________________________________________________________________
Make every e-mail and IM count. Join the i’m Initiative from Microsoft.
http://im.live.com/Messenger/IM/Join/Default.aspx?source=EML_WL_ MakeCount