similar to: [LLVMdev] Issues running LLVM tests on Windows + MKS; filed 4 PRs and have patches

Displaying 20 results from an estimated 2000 matches similar to: "[LLVMdev] Issues running LLVM tests on Windows + MKS; filed 4 PRs and have patches"

2011 Apr 14
0
[LLVMdev] Issues running LLVM tests on Windows + MKS; filed 4 PRs and have patches
Good morning David, I won't accept your patches for now. It breaks lots of things in current environments, autoconf - msys, cmake - msys, cmake -mingw and cmake - msvs. - You should never forget other environments. (eg., MSYS and CMD.EXE) You should implement detecting MKS if you tweak MKS-specific stuff. - Bash should be assumed to be mature. I suppose MKS bash might be
2012 Jun 16
9
[LLVMdev] Fwd: RFC: "Building with MinGW on Windows" (DOC, NEW)
Mikael, Thanks for working on. My gross comments... - Canonical URL of LLVM project is; http://llvm.org/ , not www.llvm.org. - "test-suite and cygwin" could be split out. It would be special thing. - Memory/storage requirements would be moved to "A.B Debugging". Less memory would be enough without debug build. - Python (x64 binary) is available, too. I am using. Python
1999 Nov 17
6
Samba 2.0.6, MKS' touch.exe, and file/dir time stamps
Hello all, we are experiencing problems with samba 2.0.6 and the MKS touch command. during our builds, we touch files and directories so that our make dependencies work correctly. Unfortunately, it seems that MKS' touch.exe doesn't actually change the time stamp of a file or directory. The command returns without an error, but the timestamp does not change. The same problem exists
2012 Jun 17
0
[LLVMdev] Fwd: RFC: "Building with MinGW on Windows" (DOC, NEW)
Now I can't make CMake use "MSYS Makefiles". I get an error about GNU v4.7.0 being broken as it can't build a simple test program. Using "MinGW Makefiles", everything works out of the box. And I am trying to give the user the most Windowsy experience (to avoid Cygwin, GnuWin32, and MSYS, if I can). So I think I'll stick to my current angle - which is to let the
2012 Jun 17
0
[LLVMdev] Fwd: RFC: "Building with MinGW on Windows" (DOC, NEW)
As for Ninja, I'd like to wait until it is officially part of the released CMake. As I understand it, Windows support has been checked into the CMake repository but no offical release supporting Ninja has been made yet. I just retrieved Ninja from Github and this time it built without problems. 2012/6/16 NAKAMURA Takumi <geek4civic at gmail.com> > Mikael, > > Thanks for
2012 Jun 16
5
[LLVMdev] Fwd: RFC: "Building with MinGW on Windows" (DOC, NEW)
On Sat, Jun 16, 2012 at 3:29 AM, Mikael Lyngvig <mikael at lyngvig.org> wrote: > Hi Takumi, > > THANK YOU for your excellent review! It makes all the work worthwhile in > itself. > > It is getting "late" here (it is early morning) so I am about to call it a > day. But I will contemplate and incorporate your suggestions tomorrow, and > send you a full
2012 Jun 17
1
[LLVMdev] Fwd: RFC: "Building with MinGW on Windows" (DOC, NEW)
Oh, didn't realize that there already is a semi-official build of CMake with Ninja support. I am trying it out right now and it seems very promising. So I'll change the document to use Ninja instead of "MinGW Makefiles". No need to waste energy on MinGW and MSYS Makefiles when Ninja outdoes them both. I thought people would have to build CMake themselves, something I'd
2012 Jun 16
0
[LLVMdev] Fwd: RFC: "Building with MinGW on Windows" (DOC, NEW)
Hi Takumi, THANK YOU for your excellent review! It makes all the work worthwhile in itself. It is getting "late" here (it is early morning) so I am about to call it a day. But I will contemplate and incorporate your suggestions tomorrow, and send you a full reply. I think I originally wrote a document where I addressed both Visual Studio and MinGW, but then decided that there were
2012 Jun 16
0
[LLVMdev] Fwd: RFC: "Building with MinGW on Windows" (DOC, NEW)
For those interested in the actual file, it is now attached. ---------- Forwarded message ---------- From: Mikael Lyngvig <mikael at lyngvig.org> Date: 2012/6/16 Subject: RFC: "Building with MinGW on Windows" (DOC, NEW) To: LLVMdev Mailing List <llvmdev at cs.uiuc.edu> Here's the first part of my Windows set up documentation. This one only covers the process of
1998 Jun 18
1
Windows app, MKS Source Integrity, Samba, and Unix
Novice question: I'm trying to use MKS Source Integrity, which is a (mostly) windows based source code control system to access a bunch of code stored in an MKS repository on an NT box and deposit the checked out files on a Unix box via a Samba share. (It's come to this, I'm porting Windows code to Unix, how depressing.) Anyway, the problem I'm having is that the Windows box
2012 Jun 16
2
[LLVMdev] RFC: "Building with MinGW on Windows" (DOC, NEW)
Here's the first part of my Windows set up documentation. This one only covers the process of setting up a normal box for building LLVM and Clang. A later document, which will follow in a few days, will cover how to set up a buildbot slave. As usual: I'm not a psychic, so if you have opinions regarding or suggestions on this document, please feel free to share them with me (on this
2014 Dec 05
3
Version 4.1.13 can't join domain as BDC
Hi All Having problem to join Samba as BDC in existing domain PDC - w2003 Partition[DC=MKS,DC=lan,DC=net] objects[10114] linked_values[0] Refusing to replicate DC=NN\0ADEL:9aac4878-b274-4bf6-92aa-4f42e40d1c43,DC=MKS,DC=lan,DC=net from a read-only repilca into a read-write replica! Failed to convert object DC=NN\0ADEL:9aac4878-b274-4bf6-92aa-4f42e40d1c43,DC=MKS,DC=lan,DC=net:
2014 Dec 05
2
Re Version 4.1.13 can't join domain as BDC
Sat, 06 Dec 2014 07:19:29 +1300 from Andrew Bartlett <abartlet at samba.org>: >On Fri, 2014-12-05 at 11:50 +0300, ?????? wrote: >> Hi All >> >> Having problem to join Samba as BDC in existing domain >> >> PDC - w2003 >> >> Partition[DC=MKS,DC=lan,DC=net] objects[10114] linked_values[0] >> Refusing to replicate
2012 May 27
0
[LLVMdev] Minor correction to the Visual Studio documentation
2012/5/24 Mikael Lyngvig <mikael at lyngvig.org>: > I know that the documentation says that I am to install GnuWin32 tools, but > I strongly oppose that idea.  We Windows people have our own tools and > practices and I think the LLVM developers should open up to a more > multi-platform approach than the current (Unix then, perhaps maybe, Windows) > approach.  CMake works
2012 May 23
6
[LLVMdev] Minor correction to the Visual Studio documentation
Hi again, The Visual Studio getting started guide ( http://llvm.org/docs/GettingStartedVS.html) mentions the "llvm-lit" tool, but fails to mention these things: 1. Either you need to run it from bash or a similar Unix shell, as Windows does not recognize the extensionless Python script that it is. 2. Alternatively, you can invoke it using Python like this: python bin/llvm-lit
2010 Sep 29
3
[LLVMdev] LLVM2.8rc2 on MinGW 4.5.1 with --enable-shared
Anybody having success building an LLVM.dll in this configuration? It's failing for me, in tools/llvm-shlib, with an error suggesting that the gcc ld doesn't understand the format of the exports map being generated. (plain configure && make works just fine, it's just this shared option that fails; google shows support for --enable-shared was added around 2.7 timeframe and
2010 Sep 29
0
[LLVMdev] LLVM2.8rc2 on MinGW 4.5.1 with --enable-shared
Good midnight, Kevin. cygming/shared might have been broken since r112976, IIRC. (ToT, too) A trivial patch; --- a/Makefile.rules +++ b/Makefile.rules @@ -942,6 +942,11 @@ ifdef EXPORTED_SYMBOL_FILE # First, set up the native export file, which may differ from the source # export file. +# The option --version-script is not effective on GNU ld win32. +ifneq (,$(filter $(HOST_OS),Cygwin
1997 Dec 01
1
Why \pipe\MKSPipe ?
I've got Source Integrity installed on our network and at least one person is having a problem checking files in. A tcpdump shows that the client is trying to open \pipe\MKSPipe (MKS is the Source Integrity Manufacturer). SAMBA (of course) replies with: SMBError = ERRSRV - ERRaccess (The requester does not have the necessary access rights within the specified context for the requested
2003 Dec 11
1
samba 3.0 vfs module problem
Hello First I prepared mks_vir Daemon, necessary libraries and modules, everything work fine (I can scan files for vireses from the command line) after that I had install samba from source next I copies and modyfying necessary mks configuration file like /etc/samba/vscan-mks32.conf and add to /usr/local/samba/lib/smb.conf following lines in global section: vfs object =
2007 Jan 11
1
rename or mv not possible when unix write mode not set
Hi, I'm wondering if anyone knows of a workaround or fix for the below issue. The Samba server is running on: Red Hat Enterprise Linux AS release 3 (Taroon Update 4) kernel=2.4.21-27.0.2.1.9.ELsmp Samba version = 3.0.20b chmod and mv are from the MKS toolkit. The question/issue: In unix I can do: touch kltest chmod 544 kltest mv kltest kltest3 If I create a directory on the samba