similar to: msvc trunk breakage

On Thu, Mar 29, 2007 at 03:39:01PM +0100, richard wrote: > bin/xapian-tcpsrv.cc,tests/harness/testsuite.cc: First of many > parts of a large patch from Mark Hammond working towards enabling > remote databases on windows. When displaying errors which might > be socket errors, display the error number as well as the output > of strerror - on windows, strerror doesn't display

I'm currently seeing: utils.cc c:\src\xapian\xapian-core\common\utils.h(84) : error C2061: syntax error : identifier 'mode_t' c:\src\xapian\xapian-core\common\utils.h(85) : error C2065: 'mode' : undeclared identifier I *think* I've done everything correctly this time in terms of updating svn and rebuilding :) My solution was to add: typedef int mode_t; to safestat.h -

I tried to compile xapian 1.0.1 under windows but the new /msvc/version.h file has #undef XAPIAN_HAS_REMOTE_BACKEND which prevents /backends/dbfactory_remote.cc to be built. The old (hand-written) version.h.win32 had it defined to 1. Everything build fine if I replace #undef with #define in version.h. Cheers, -- Daniel M?nard

Hi, src/unix/Rscript.c on R trunk stopped building with a compiler error of "unknown not defined/declared" on line 160-ish, where R_SVN_REVISION is , on my system. I see trunk r60972, trunk r60975 changes R_SVN_REVISION to a number - if it can be found, from being a string. The thing is, I track R development with git's svn support (which IMHO works far better). So svn info cannot

Hi, everyone. I'm a third-year student in Computer Science. I have a few projects (school-related) on Bitbucket <https://bitbucket.org/philipchung/philipchungtech>. I've been looking at the project-ideas list and I'm interested in making Omega use libraries instead of external programs. Right now I'm trying to get Olly's patch that was linked there to apply to the

Hi guys, We've been in discussion with Richard and Olly on this issue, in various different forums, but as the correct answer isn't immediately obvious, I'm opening it up for wider discussion and comment. The problem is that a xapian tcp-server in 'writable' mode makes no attempt to ensure only one 'active' connection at a time is trying to modify the database. If

Dear Xapian developers, I am happy to announce that the Xapian-Ruby bindings now pass all tests defined in smoketest.rb. (These tests are mostly drawn from smoketest.py; a few tests that are not applicable to the Ruby version have been removed.) I have also added Olly's patch to integrate the Ruby bindings into the automake/configure scripts. The latest version is available by anonymous

On 24 August 2014 02:05, Alex Rosenberg <alexr at leftfield.org> wrote: > But it must. If you want to be able to use LLVM DLLs inside a Windows app, it has to be built with MSVC because they have their own C++ ABI. At some point, Clang will support Microsoft's ABI well enough to consider a bootstrap instead. Ah, there's my answer! I thought we were at that stage already.

Yes. I’ll handle the documentation updates too. I’ll base the list of C++11 features on the MSDN documentation. -Chris > On Jan 30, 2015, at 3:57 PM, Aaron Ballman <aaron at aaronballman.com> wrote: > > On Fri, Jan 30, 2015 at 6:51 PM, Chris Bieneman <cbieneman at apple.com> wrote: >> +Alex Bradbury >> >> Sounds to me like we have no known users still on

On Thu, Mar 01, 2007 at 03:29:26PM +0000, richard wrote: > * common/utils.c,common/utils.h: For windows, add an om_tostring()function for > 64 bit integers: time() and GetProcessId() return these, and without this, > backends/quartz/quartz_log.cc reports an error. This change generates a new warning in the mingw cross-build: common/utils.cc:82: warning: int format, different type

+Alex Bradbury Sounds to me like we have no known users still on VS 2012. So, how about we plan to move forward again with Chandler’s proposal for making this transition. For those who don’t want to dig through to the beginning here’s the basic plan: 1) Loop in cfe-dev and lldb-dev (Done!) 2) Wait until this email fully circulates in digests and LLVM Weekly so that everyone who has an objection

On Fri, Jan 30, 2015 at 6:51 PM, Chris Bieneman <cbieneman at apple.com> wrote: > +Alex Bradbury > > Sounds to me like we have no known users still on VS 2012. > > So, how about we plan to move forward again with Chandler’s proposal for making this transition. For those who don’t want to dig through to the beginning here’s the basic plan: > > 1) Loop in cfe-dev and

If we have no other major users who require VS 2012 support, I think it's reasonable to officially switch now. We might want to wait for 3.6 to go out the door, just to reduce possible issues with porting fixes, but that may be overly cautious. ~Aaron On Wed, Jan 28, 2015 at 7:16 AM, Greg Bedwell <gregbedwell at gmail.com> wrote: > This thread seems to have stalled again without

On Wed, Oct 8, 2014 at 12:17 PM, Greg Bedwell <gregbedwell at gmail.com> wrote: > Hi, > > To follow up from Paul last week: > >> I'm expecting to have our internal builds switched over later this >> week. Our investigations have shown no problems. > > We've now updated our internal builds from 2012.4 (cl.exe 17.0.61030) to > 2013.3 (cl.exe

> -----Original Message----- > From: cfe-dev-bounces at cs.uiuc.edu [mailto:cfe-dev-bounces at cs.uiuc.edu] On > Behalf Of Aaron Ballman > Sent: Monday, September 29, 2014 4:45 PM > To: Chris Bieneman > Cc: lldb-dev at cs.uiuc.edu; cfe-dev Developers; LLVM Developers Mailing List > Subject: Re: [cfe-dev] [LLVMdev] [RFC] Raising LLVM minimum required MSVC > version to 2013

MSVC survives because there's no effective competition- it's like communications providers in the United States or political parties in China. The alternatives like GCC have no decent development environments for them, and Clang has the bonus of not being mature w.r.t. things like Standard libraries. The reality is, there's nowhere to go *but* MSVC. This stuff is the major reason why

In a recent post, someone asked about storing "metadata" in a document. My guess would have been to use add_value. Olly's recommendation was to use set_data. What are the general guidelines for deciding whether to use values or data in a document? Garrett

olly wrote: > Log message (7 lines): > backends/database.cc: Database::Internal can't call the > PostingIterator(PostingIterator::Internal*) ctor (at least under > g++ 3.3.5) because it isn't a friend (only class Database is). For the record, Mark just reported this to me under windows so it was a problem there too, but it does work under GCC 4.1. No idea which compiler is

On Mon, Feb 9, 2015 at 8:36 AM, Greg Bedwell <gregbedwell at gmail.com> wrote: > We've just encountered an issue with ninja and VS2013 when using versions of > CMake prior to 2.8.12.1. This isn't a combination that we typically use so > we've not run into it previously in our own builds. It isn't specifically > tied to upgrading the minimum version as it's a

On Tue, May 12, 2009 at 11:55 PM, Chris Lattner <clattner at apple.com> wrote: > Dan, can you add IVUsers.cpp to the appropriate cmakefile? > > -chris > > > On May 12, 2009, at 10:54 PM, OvermindDL1 wrote: > >> On Tue, May 12, 2009 at 11:40 PM, Chris Lattner <clattner at apple.com> >> wrote: >>> >>> On May 12, 2009, at 10:24 PM,