Ugh.
I am using XCode 3.2.1's gcc and g++. I am really tempted to wipe this
system clean, as I think my advisor's distribution messed up a lot of
stuff.
Would you mind posting or sending your config.log? I'd like to see if
there is something significantly different or strange about my
parameters e
Protobuf does subclass hash_map and hash_set in order to "fix" the
interfaces to look like GCC's. However, it does not use __declspec on these
definitions.
Can you create a minimal self-contained example program demonstrating the
problem?
On Fri, Dec 18, 2009 at 2:23 AM, Anu KR wrote:
> Thanks
Hmmm... that should work fine; there *was* a related bug in an early build,
but...
Can I check which version and framework you are using? I've checked on r275,
and it works fine "as is", for both empty lists and some arbitrary data I
made up.
Sorry for the delay, btw - seasonal break, etc...
Mar
Thanks Kenton. That worked.
On Fri, Dec 18, 2009 at 1:55 PM, Kenton Varda wrote:
> You need to install GNU libtool.
>
>
> On Fri, Dec 18, 2009 at 7:56 AM, Delip Rao wrote:
>
>> I'm trying to build version 2.3.0 from the SVN and find no "configure"
>> script. I also tried "sh autogen.sh" to gene
You need to install GNU libtool.
On Fri, Dec 18, 2009 at 7:56 AM, Delip Rao wrote:
> I'm trying to build version 2.3.0 from the SVN and find no "configure"
> script. I also tried "sh autogen.sh" to generate the script but I get
> this error:
>
> configure.ac:29: error: possibly undefined macro:
On Fri, Dec 18, 2009 at 07:01:36AM -0800, Scott Stafford wrote:
> We don't have a formal spec of it or anything, but from what I can
> tell we evolved the same syntax as the internal Google effort. No
> frills, just a sequence of N field names separated by dots (.). I'll
> try to write out the rul
I'm trying to build version 2.3.0 from the SVN and find no "configure"
script. I also tried "sh autogen.sh" to generate the script but I get
this error:
configure.ac:29: error: possibly undefined macro: AC_PROG_LIBTOOL
If this token and others are legitimate, please use
m4_pattern_allow.
The implementation is already in a different namespace .
namespace abc
{
namespace xyv
{
typedef std::set int_set;
class MY_DLL_EXPORT has_riskgroups : private int_set
}
}
2009/12/18 Александр Мельников :
> If it really that, you may use names
We don't have a formal spec of it or anything, but from what I can
tell we evolved the same syntax as the internal Google effort. No
frills, just a sequence of N field names separated by dots (.). I'll
try to write out the rules in English, but I might mess this up since
I'm just doing it from mem
If it really that, you may use namespace to get this symbol different name.
I.e:
namespace my_ns
{
class MY_DLL_EXPORT my_class : public std::set
{
};
}
--
From: "Anu KR"
Sent: Friday, December 18, 2009 4:23 PM
To: "Protocol Buffers"
Subject: Re:
Thanks every body for the reply.
I did checked the project settings for protocol buffer libraries and
our libraries, and they are the same. They were Multi-threaded Debug
DLL (/MDd) for debug version and and Multi-threaded DLL (/MD) for
release.
However we found that one of our classes were inhe
FYI, I've verified that protobuf-2.2.0 works correctly on Snow Leopard with
the latest Xcode compiler.
On Wed, Nov 11, 2009 at 2:10 PM, Kenton Varda wrote:
> I have no idea what the problem could be. However, I have a fancy new Mac
> laptop arriving next week on which I will make sure to test p
12 matches
Mail list logo
