[aspectc-user] current release (0.7.2) unusable due to bug 13 7

[Green Bryan - bgreen]

Yes, I have had the same problem with xstring on a windows machine as well.
I gave up.  If this is solved I would love it because I could convince the
company I work for that it is usable for complex ( lots of templates )
development.  They are skeptical due to problems like this.  Even though I
freely admitted it was most likely my not knowing what I was doing.



-----Original Message-----
From: aspectc-user-admin at aspectc.org
[mailto:aspectc-user-admin at aspectc.org]On Behalf Of p
Sent: Tuesday, January 20, 2004 2:17 AM
To: Danilo Beuche; thiagoacorrea
Cc: aspectc-user at aspectc.org
Subject: Re: [aspectc-user] current release (0.7.2) unusable due to bug
137


Hi,

...having the same problem on GNU/Linux (using gcc version 3.2.2):

/usr/include/c++/3.2.2/bits/basic_string.tcc:165: error: redefinition of 
`basic_string::_S_construct'
/usr/include/c++/3.2.2/bits/basic_string.h:747: previously defined here
make: *** [ac] Error 1

Tweaking of the PUMA_CONFIG file (`-D __GNUC_MINOR__=95' and `-D
__GNUG__=2') 
as suggested by README did not help.

Could you please give me an example on how/what defines would be required on

the command line (or the PUMA_CONFIG file)?

Thanks,
Philipp


On Tuesday 20 Jan 2004 8:52 am, Danilo Beuche wrote:
> Hi,
>
> the same problem was sometimes ago mentioned on the mailing list.
> My answer was
>
> ---
> The problem is probably due to some missing #define for ac++. Please
> have a look in the specified file  C:/Program Files/Microsoft Visual
> Studio/VC98/Include/xstring around line 100 for any suspicious #ifdef
> statement(s).
> Add the required defines either to your command line or to the
> PUMA_CONFIG file.
>
> Please make sure that you use the right PUMA_CONFIG (pumavc7.cfg)!
> ---
>
> If someone would send us the problematic lines from the xstring include
> we could put the right stuff into an pumavc6.cfg. Maybe you should try
> the modifications of Frank Prantl (yesterday on the mailing list). If
> this still does not work, the problem should be considered more serious
> indeed.
>
>
> Regards,
> 	Danilo
>
> thiagoacorrea wrote:
> > <a href="http://www.aspectc.org/bugzilla/show_bug.cgi?
> > id=137">Bug 137</a>, taken as Severity "Normal" should be
> > considered blocking since it prevents you from using
> > AspectC++ with code that depends on the STL.
> >
> > You don't need to do any fancy thing to be hit by the bug,
> > for example, by just adding "#include <string>" to the Order
> > example you will get this:
> >
> > C:\AC>ac++ -p examples\Order -d examples\Order-out -
> > Iexamples\Order -v9
> > * Running ac++ 0.7.2
> > * Simple Dependency Check
> > * Handling Translation Unit `main.cc'.
> >   - Path "examples/Order/main.cc"
> > C:/Arquivos de programas/Microsoft Visual
> > Studio/VC98/include/xstring:108: error
> >
> > : redefinition of `append'
> >
> > C:/Arquivos de programas/Microsoft Visual
> > Studio/VC98/include/xstring:100: previ
> > ously defined here
> > C:\AC>
> >
> > May someone please take the issue more seriously, as it
> > prevents using ac++ on any non-trivial C++ project. I can't
> > find any way of working around this :(
> >
> > Thanks in advance and best regards,
> >   Thiago A. Correa
> >
> >
> >
> > ---
> > Acabe com aquelas janelinhas que pulam na sua tela.
> > AntiPop-up UOL - É grátis!
> > http://antipopup.uol.com.br
> >
> >
> > _______________________________________________
> > aspectc-user mailing list
> > aspectc-user at aspectc.org
> > http://www.aspectc.org/mailman/listinfo/aspectc-user


_______________________________________________
aspectc-user mailing list
aspectc-user at aspectc.org
http://www.aspectc.org/mailman/listinfo/aspectc-user


**********************************************************************
The information contained in this communication is
confidential, is intended only for the use of the recipient
named above, and may be legally privileged.
If the reader of this message is not the intended
recipient, you are hereby notified that any dissemination, 
distribution, or copying of this communication is strictly
prohibited.
If you have received this communication in error,
please re-send this communication to the sender and
delete the original message or any copy of it from your
computer system. Thank You.