similar to: problem for compiling xapian in windows xp

Displaying 20 results from an estimated 5000 matches similar to: "problem for compiling xapian in windows xp"

2010 Jun 04
2
Xapian-devel Digest, Vol 66, Issue 2
Hi Charlie, Thanks for your reply. I've modified config.mak according to README. I just want to output the xapian dll for php, so i removed other config such python, csharp, etc. I download source code from php site & set the path in config.mak accordingly. It still reports this error. I'm confused which config i missed. Thanks. Jaber 2010/6/3 <xapian-devel-request at
2013 Aug 26
1
[LLVMdev] Building LLVM 3.3 on Win64
... Or maybe not? I just tried it again in the exact same configuration that did work before, and this time it fails at an earlier stage with a different error: [ 66%] Building CXX object lib/Target/Mips/CMakeFiles/LLVMMipsCodeGen.dir/Mips16FrameLowering.cpp.obj Mips16FrameLowering.cpp NMAKE : fatal error U1077: 'C:\PROGRA~2\MICROS~2.0\VC\bin\cl.exe' : return code '0xffffffff'
2013 Aug 26
0
[LLVMdev] Building LLVM 3.3 on Win64
After some running some more tests, a weird addendum to this case: the build also fails at the same place with the same error message if MinGW isn't in the path. I'm not talking about MinGW instead of Microsoft C++, it's just that the build works if and only if MinGW is in the path _as well as_ the 32-bit version of Microsoft C++. On Sat, Aug 24, 2013 at 8:15 PM, Russell Wallace
2013 Aug 24
4
[LLVMdev] Building LLVM 3.3 on Win64
I'm trying to build LLVM 3.3 using cmake/nmake, Microsoft C++ 2012, on a 64-bit Windows 7 system. I tried it with the 32-bit compiler as a test case first and that appeared to work, then with the 64-bit compiler in the hope that would give me a 64-bit build of LLVM, but instead got this error message: [ 86%] Generating X86CompilationCallback_Win64.obj Microsoft (R) Macro Assembler (x64)
2013 Aug 26
0
[LLVMdev] Building LLVM 3.3 on Win64
Hi Russel, I never tried to build LLVM with nmake. With msbuild it works without problems. You can find a short desription here: http://wiki.dlang.org/Building_and_hacking_LDC_on_Windows_using_MSVC, section Build LLVM. Regards Kai On 24.08.2013 21:15, Russell Wallace wrote: > I'm trying to build LLVM 3.3 using cmake/nmake, Microsoft C++ 2012, on a > 64-bit Windows 7 system. I
2009 Sep 15
1
can´t build ruby bindings with msvc (xapian 1.1.2)
hi i?m trying to build the ruby bindings in xapian 1.1.2 on win xp. i?ve 1. pulled the tags/1.1.2 revision from svn 2. built SWIG from repo via MinGW and MSYS (swig -help works, so build seems ok to me) 3. built xapian-core following readme in ...\win32msvc, apitest doesn?t give errors now if i try to build: "...\ruby>nmake SWIGBUILD=1 Microsoft (R) Program
2008 Feb 28
2
Can't get xapian-core 1.05 to build under windows xp
Here is the output I get from nmake. I am not a guru at getting C programs to build under windows, I never had any troubles I could not solve on OSX :-( I am using the released sources, I have Visual Studio 2005, I have the make files from lemur. I read ALL the readme.txt file before starting. And this is what I get. C:\Documents and Settings\jroberson\My Documents\DOWNLOADS\xapian-
2006 Aug 22
4
Native Extensions on Windows 0.10 series
Hi all, I''ve just noticed that 0.10 is out and wanted to give it a try on windows. I''m not at all an VS C++ Developer so I might do something very stupid here. My env: Windows Server 2003 VS .NET 2003 On the command line with nmake from VC7 in the path this is what I get: Attempting remote update of ferret Building native extensions. This could take a while... Microsoft
2008 Jun 04
3
Ruby 1.8.7
Hi all, Has anyone else been able to build Ruby 1.8.7 from source on Windows? I get this when I run configure: C:\>win32\configure.bat find: =: No such file or directory Creating Makefile Creating Makefile(6) : fatal error C1085: Cannot write compiler generated file: '''': Invalid argument NMAKE : fatal error U1077: ''cl'' : return code ''0x1''
2011 Jan 01
1
[LLVMdev] "nmake check" doesn't work for MSVC
Hi, I built llvm+Clang for MSVC 10 with cmake ../../Source/LLVM -G"NMake Makefiles" nmake And I tried to do a nmake check (which works for MinGW and "mingw32-make check") and get the following error: >Scanning dependencies of target check >[100%] Running LLVM regression tests >Traceback (most recent call last): > File
2012 Aug 06
1
Windows link.exe error : libbrass.lib(brass_table.obj) : unresolved external symbol _inflateEnd
Hi guys, I discovered xapian today and I'm trying it because it looks promising compared to other FTS engines. However I'm in a windows environment so it's a bit painful to set up as there is no official binaries. I've heard about http://www.flax.co.uk/xapian_binaries And I'm trying to build their latest release (1.2.8). After a few tries I manage to compile everything with
2008 Jun 25
3
[OT] Byacc error
Hi all, Yeah, I''m going OT here... I''m not entirely sure I understand how Ruby builds parse.y on Windows, but it works. However, when I changed all instances of "Ruby" to "Sapphire", and renamed all the source files, I suddenly started getting this error: byacc ./parse.y ''byacc'' is not recognized as an internal or external command,
2009 May 14
1
(no subject)
Hi, Vista Visual Studio 2008 This has popped up on my Vista box with a fresh download of ruby-1.8.6-p114: pack.c(1926) : warning C4018: ''>'' : signed/unsigned mismatch byacc ./parse.y ''byacc'' is not recognized as an internal or external command, operable program or batch file. NMAKE : fatal error U1077: ''byacc'' : return code
2004 May 24
1
Cannot call R's ISNAN() from a C code in >1.7 versions.
Dear R users, Have you experienced any difficulty in calling R's ISNAN() from a C code? I have C codes including ISNAN() calls and they worked well until I upgraded my R from 1.7 to later versions. When I tried to compile the codes in the version 1.8 and 1.9, I got error messages like this: test.obj : error LNK2001: unresolved external symbol _isnan .\testR.dll : fatal error LNK1120: 1
2015 Jan 03
3
Xapian-discuss Digest, Vol 127, Issue 1
Hey Richhiey, Most probably Xapian is used with CYGWIN in Windows and Windows Specific Code in Xapian is based on CYGWIN, However we would be able to help you out with this issue, if you could pastebin whole 'gnu-make' generated report. Regards, Abhishek On Sat, Jan 3, 2015 at 5:30 PM, <xapian-discuss-request at lists.xapian.org> wrote: > Send Xapian-discuss mailing list
2009 Oct 22
2
Reliability issues when using Windows 7
Hello, at our company we are using Samba 4.3.2 in conjunction with Windows 7. We use the Windows 7 machines for our nightly compiles. However, occasionally the schedules compiles stop with a Windows network error message, such as: . . . [ 16%] Generating ui/moc_versiondialog.cxx [ 16%] NMAKE : fatal error U1077: 'R:\usr\20091022\121890\release\win\bin\cmake.exe' : return code
2003 Oct 25
9
Windows Compile Error
I''ve gotten a lot farther building wxRuby than I did a few months ago. But its getting late here and I''m going to bed. In the meantime, does anyone know why I''m getting this compile error: Microsoft (R) Program Maintenance Utility Version 6.00.8168.0 Copyright (C) Microsoft Corp 1988-1998. All rights reserved. cl -MD -Zi -O2b2xg- -G6
2005 May 01
3
win32-dir 0.1.0 compile problems
I tried to download/compile/install win32-dir, but I couldn''t get it to go. Over a private email Daniel Berger had me... "Curious. What platform are you on exactly? Try modifying the extconf.rb file. Add ''have_library("SHFolder")'' above ''have_library("shell32")''. If that doesn''t work, try uncommenting the other
2009 Nov 12
1
[ win32utils-Bugs-27425 ] win32-open3 doesn't build with 1.9.1
Bugs item #27425, was opened at 2009-11-11 21:15 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=411&aid=27425&group_id=85 Category: win32-open3 Group: Code Status: Open Resolution: None Priority: 3 Submitted By: Daniel Berger (djberg96) Assigned to: Nobody (None) Summary: win32-open3 doesn''t build with 1.9.1 Initial Comment: Windows XP VC++ 9
2017 Sep 01
1
how to build Xapian project on windows?
> Those nmake files have been without a maintainer since about 2011, so > it's not a big surprise that they don't work without a few tweaks at > this point. > Nobody seems interested in keeping the nmake files up to date, so it's > probably time we just removed them. I think formerly it was listed on the Xapian website which was the last version of xapian-core known to