search for: fmsc

...e of course "files winbind") but I'm still having problems accessing directories in a share that has folders owned by groups which are defined in /etc/group rather than winbind.. e.g I have a 'Group' share with the following test directories at the moment: drwxrwx--- 23 root FMSC 4096 Jan 31 09:28 FMSC drwxrwx--- 7 root website 4096 Jan 22 11:28 School Website My account, now that I've edited nsswitch to use files for groups only, is a member of the following (/etc/group) groups: # groups njps3 njps3 : Domuser FMSC school isd cetl timetable anatomy faculty hhstaf...

...NICODE /D UNICODE /Gm- /EHsc /RTC1 /MDd /GS /fp:precise /Zc:wchar_t /Zc:forScope /Fo"Debug\x64\\" /Fd"Debug\x64\vc120.pdb" /Gd /TP /wd4068 /wd4200 /wd4244 /wd4267 /wd4305 /wd4309 /wd4311 /wd4800 /FIC:\[top-level-dir]\[source-dir]\\[prefix-header].h /errorReport:prompt -m64 -fmsc-version=1800 -ferror-limit=1000 -m64 -fmsc-version=1800 [source-file].cpp And here's the error: 1> In file included from [source-file].cpp:9: 1> In file included from C:\[top-level-dir]\[source-dir]/[source-file].h:12: 1>C:\[top-level-dir]\[source-dir]/[another-header-file].h(14,...

...e of course "files winbind") but I'm still having problems accessing directories in a share that has folders owned by groups which are defined in /etc/group rather than winbind.. e.g I have a 'Group' share with the following test directories at the moment: drwxrwx--- 23 root FMSC 4096 Jan 31 09:28 FMSC drwxrwx--- 7 root website 4096 Jan 22 11:28 School Website My account, now that I've edited nsswitch to use files for groups only, is a member of the following (/etc/group) groups: # groups njps3 njps3 : Domuser FMSC school isd cetl timetable anatomy faculty hhstaf...

...example, if I do a straight port using Visual Studio, I have the replace all the uses of blocks with either callbacks or lambdas. Having spent a couple of hours on this, I'm now wondering if perhaps it's not as straight-forward as I thought. For example, the toolset.props file adds the -fmsc-version=1800 compiler flag, which fools the conditional compilation in my header files into acting just like they do with the Visual Studio compiler. Also, I'm seeing an error where different header files have different ideas about the type of t_size, but that my just be something I have to...

...> if you really want to target mingw. If I split it up like this, I get > link errors: > $ clang++ -c t.cpp -o t.o --target=x86_64-windows-gnu > $ clang++ t.o -o t.exe --target=x86_64-windows-msvc -fuse-ld=lld Actually just doing: clang++ -c t.cpp -o t.o --target=x86_64-windows-msvc -fmsc-version=1900 clang++ t.o -o t.exe --target=x86_64-windows-msvc -fuse-ld=lld is not working for me. The first invocation works but the second just hangs and never completes. Should it work ? If not, how can I invoke the second to make it work properly ? > C:\src\llvm-project\build_mingw\bin\l...

...>> >> I recall that you copied the win32 platform toolset xml files over by >> hand, and I don't think they will have the correct flags. If you see this >> line in the x64 toolset.props file, replace -m32 with -m64 and try again: >> <AdditionalOptions>-m32 -fmsc-version=1700 >> %(AdditionalOptions)</AdditionalOptions> >> >> In the meantime, I think Hans is trying to fix the installation of >> those xml files and hopefully that will fix issues for other users going >> forwards. >> >> On Tue, Sep 30, 2014 at 1...

...9:03 PM, Reid Kleckner via llvm-dev wrote: > On Thu, Mar 30, 2017 at 5:57 PM, Edward Diener via llvm-dev > <llvm-dev at lists.llvm.org <mailto:llvm-dev at lists.llvm.org>> wrote: > > Actually just doing: > > clang++ -c t.cpp -o t.o --target=x86_64-windows-msvc -fmsc-version=1900 > clang++ t.o -o t.exe --target=x86_64-windows-msvc -fuse-ld=lld > > is not working for me. The first invocation works but the second > just hangs and never completes. Should it work ? If not, how can I > invoke the second to make it work properly ? >...

...e/../lib/clang/3.1 include -internal-isystem "C:\\Program Files\\Microsoft Visual Studio 9.0\\VC\\ nclude" -internal-isystem "C:\\Program Files\\Microsoft SDKs\\Windows\\v6.0A\\\ include" -O3 -ferror-limit 19 -fmessage-length 80 -mstackrealign -fms-extension -fms-compatibility -fmsc-version=1300 -fdelayed-template-parsing -fgnu-runtime -fobjc-runtime-has-arc -fobjc-runtime-has-weak -fobjc-fragile-abi -fdiagnostics show-option -fcolor-diagnostics -o test.s -x c test.c .def _f; .scl 2; .type 32; .endef .text .globl _f .align 16, 0x90 _f:...

...n from this approach is the ability to directly compile Objective-C code. I'll try that today and see what happens. I'm also hoping that Objective-C mixed in with C++ will work, but perhaps _MSC_VER will mean that won't work? > I think you can turn of the _MSC_VER definition with -fmsc-version= or > some other flag, if you want to try that. I wouldn't recommend it, > because windows.h and other system headers usually need to have > _MSC_VER defined. Yes, that makes sense. > I saw your other thread about installation troubles, but it's hard to > debug re...

...m64 argument? > > I recall that you copied the win32 platform toolset xml files over by > hand, and I don't think they will have the correct flags. If you see > this line in the x64 toolset.props file, replace -m32 with -m64 and > try again: > <AdditionalOptions>-m32 -fmsc-version=1700 > %(AdditionalOptions)</AdditionalOptions> > > In the meantime, I think Hans is trying to fix the installation of > those xml files and hopefully that will fix issues for other users > going forwards. > > On Tue, Sep 30, 2014 at 1:55 PM, Eric Mader <ema...

I'm getting compile errors because size_t is getting redefined. My "forced include file" starts with: #if BUILDING_FOR_WINDOWS #define NOMINMAX /* deal with the fact that windef.h also defines BOOL */ #define BOOL WINBOOL #include <windows.h> #include <intrin.h> #undef BOOL #endif Looking at the preprocessor expansion of a typical .cpp file, I see that crtdefs.h

...;$(LLVMInstallDir)\lib\clang\3.6.0\lib\windows;$(LibraryPath)</LibraryPath> > </PropertyGroup> > > <ItemDefinitionGroup> > <ClCompile> > <!-- Set the value of _MSC_VER to claim for compatibility --> > <AdditionalOptions>-m64 -fmsc-version=1800 > %(AdditionalOptions)</AdditionalOptions> > </ClCompile> > </ItemDefinitionGroup> > </Project> > > It still doesn't work... Is there something else I need to change? > > Regards, > Eric > > > On 9/29/14, 10:41 AM, R...

...g the -m64 argument? > > I recall that you copied the win32 platform toolset xml files over by > hand, and I don't think they will have the correct flags. If you see this > line in the x64 toolset.props file, replace -m32 with -m64 and try again: > <AdditionalOptions>-m32 -fmsc-version=1700 > %(AdditionalOptions)</AdditionalOptions> > > In the meantime, I think Hans is trying to fix the installation of those > xml files and hopefully that will fix issues for other users going forwards. > > On Tue, Sep 30, 2014 at 1:55 PM, Eric Mader <emader at...

...ws;$(LibraryPath)</LibraryPath> >> </PropertyGroup> >> >> <ItemDefinitionGroup> >> <ClCompile> >> <!-- Set the value of _MSC_VER to claim for compatibility --> >> <AdditionalOptions>-m64 -fmsc-version=1800 >> %(AdditionalOptions)</AdditionalOptions> >> </ClCompile> >> </ItemDefinitionGroup> >> </Project> >> >> It still doesn't work... Is there something else I need to change? >> >> R...

Open the file toolset-vs2013.props and you'll understand what's happening and where the path is set. It tries to fetch the LLVM installation path from the Windows registry. Just fix this (maybe editing your registry or editing the .props file, whatever suits you best). On Mon, Sep 29, 2014 at 5:33 PM, Eric Mader <emader at gmx.us> wrote: > I copied the x64 toolsets by hand and

...bin/../lib/clang/3.0/include -internal-isystem "C:\\Program Files\\Microsoft Visual Studio 9.0\\VC\\include" -internal-isystem "C:\\Program Files\\Microsoft SDKs\\Windows\\v7.0\\\\include" -fdeprecated-macro -ferror-limit 19 -fmessage-length 0 -fms-extensions -fms-compatibility -fmsc-version=1300 -fdelayed-template-parsing -fgnu-runtime -fobjc-runtime-has-arc -fobjc-runtime-has-weak -fobjc-fragile-abi -fcxx-exceptions -fexceptions -fdiagnostics-show-option -o C:/cygwin/tmp/hello-066049.o -x c++ hello.cpp clang -cc1 version 3.0 based upon llvm 3.0 hosted on i686-pc-win32 #includ...

On 3/29/2017 1:38 PM, Reid Kleckner via llvm-dev wrote: > If clang is targeting VC++, then -fuse-ld=lld should be enough to make > it run lld-link.exe, and you won't need to set the flavor or do anything > special to get PE/COFF files. > > This example worked for me: > > $ cat t.cpp > #include <iostream> > int main() { std::cout << "hello

I build llvm/clang/lld from source on Windows using mingw-64/gcc-6.3. I use clang++ both to test clang targeting gcc and clang targeting VC++. When using clang targeting VC++ I use the appropriate target triple when compiling and am trying to use lld to link the object file(s) into an exe. To do that I use the clang option "-fuse-ld=lld" when linking. According to the llvm doc on