similar to: Compile syslinux64.exe on ubuntu

Signed-off-by: Paul Bolle <pebolle at tiscali.nl> --- 0) If I build syslinux on a system without mingw a (successful) build will end with: ls: cannot access win32/syslinux.exe: No such file or directory ls: cannot access win64/syslinux64.exe: No such file or directory [...] make: [all] Error 2 (ignored) Ie, it ends with an ignored error. That's confusing (and a bit

Hi there, I've been trying to boot some new machines via uEFI and it does not work, as you can see below. From my hunting around on the mailing list, there may have been a bunch of fixes that have been committed that have some bearing on uEFI, and even some on the mailing list that appear to be aimed at solving similar problems. However, I can't manage to build a new one based on the

> > Is it turned ON in your build? > Yes it is turned on in my build here is my build script PATH=/mingw64/bin:$PATH FFI_INCLUDE_DIR="$(pkg-config --cflags libffi)" > FFI_INCLUDE_DIR=$(echo $FFI_INCLUDE_DIR | sed 's|-I||g') > > /mingw64/bin/cmake.exe \ > -G"MSYS Makefiles" \ > -DCMAKE_MAKE_PROGRAM="/usr/bin/make.exe" \ >

Hi, I'm building using MINGW64 on a very slow system (Intel Atom 330 X2 1.6 GHz), but it seems rather odd that the system has been linking clang.exe for the past two hours. It appears that a couple of gigabytes of virtual memory are being used (causing constant swapping) - the system has only 2 GB of physical memory. Is this a bug in MINGW64 (binutils 2.22) or is it just too little RAM in

Hello, I'm booting linux-3.16-686-pae kernel (32-bit) via syslinux.efi 64-bit version. After boot linux sees only 2.5G of RAM while system has 32G installed. If I boot the same kernel with GRUB64 efi instead of syslinux then amount of RAM available to linux is 32G. Is this a bug or I'm missing something? syslinux.cfg: label live-686-pae menu label Linux (686-pae) menu

Hi, I tried that out, I got a new error about pthreads in my config.log. Could you take another look. Thanks again, Reza > On Aug 20, 2019, at 12:36 PM, Daniel P. Berrangé <berrange@redhat.com> wrote: > > On Tue, Aug 20, 2019 at 12:29:15PM -0400, reza shahriari wrote: >> Hi, >> >> I have attached my compressed config file. >> >> Thanks,

于 2012/5/27 11:04, Mikael Lyngvig 写道: > Hi, > > I'm building using MINGW64 on a very slow system (Intel Atom 330 X2 > 1.6 GHz), but it seems rather odd that the system has been linking > clang.exe for the past two hours. It appears that a couple of > gigabytes of virtual memory are being used (causing constant swapping) > - the system has only 2 GB of physical memory.

Hi, I accidentally noticed the following line when building LLVM and Clang on Windows 7 x64 using Mingw64: Linking CXX shared library ..\..\..\..\bin\liblibclang.dll "Liblib" seems a bit overkill. FYI. BTW, for those who happen to search on LLVM, Clang, Windows, and Mingw64: The v3.1 release does NOT build with Mingw64. I believe this has been fixed in the Subversion sources as

In message <BLU0-SMTP4359BC7EA366B1FB76EA9188BBF0 at phx.gbl>, Ady <ady-sf at hotmail.com> wrote: >I am probably misunderstanding something. We seem to go backwards. Yes, and ever moreso. >"Something" changed. If you now cannot see your USB drive in your >list (press F12 during POST), there is no point on redacting >instructions. *Now* that I have set up

Ady, before responding to you further, I'll ask you now to take onje more (fresh) look at this thread that I started over in the GParted forums: http://gparted-forum.surf4.info/viewtopic.php?pid=31834 Please note that I have now followed-up on myself and that I have added quite a lot of new & additional information. It now appears to me that GParted's reporting of the status of

Sorry for bothering you I am trying to build the R grpc package on windows: https://github.com/nfultz/grpc against an MSYS2 build of grpc. when running devtools::install() I am getting the following error: C:/msys64/mingw64/include/grpc/impl/codegen/port_platform.h:47:2: error: #error "Please compile grpc with _WIN32_WINNT of at least 0x600 (aka Windows Vista)" #error \ ^ Which,

Hi, I have attached my compressed config file. Thanks, Reza > On Aug 20, 2019, at 12:03 PM, Daniel P. Berrangé <berrange@redhat.com> wrote: > > Re-adding the mailing list CC - please don't drop it. > > On Tue, Aug 20, 2019 at 11:54:34AM -0400, reza shahriari wrote: >> Hi, >> >> I am using msys2. When I run `./configure` without any parameters

Thanks so much. I got it to go past pthreads. Now I am working on other dependencies > On Aug 20, 2019, at 1:30 PM, Daniel P. Berrangé <berrange@redhat.com> wrote: > > On Tue, Aug 20, 2019 at 01:03:40PM -0400, reza shahriari wrote: >> Hi, >> >> I tried that out, I got a new error about pthreads in my config.log. > > It finds the header file now which is

Hi, I just did a "make install" on Win7x64 using Mingw64 and it dropped off the files in "C:\Program Files (x86)\LLVM". That's almost right, but nicer would be if the 64-bit build was dropped off in "C:\Program Files\LLVM". I am fairly confident that it is me who is doing something wrong because I simply do this: (retrieve trunk version of LLVM, Clang,

> > the problem is that very few LLVM developers use or know anything about > Windows. > The only way for this to change is for people who do know and care about > Windows > to step forward, work on improving Windows support, and contribute their > Windows > viewpoint to design discussions etc. > As it is now, Windows users will quite likely drop LLVM because of the

On Thu, May 24, 2012 at 12:53 PM, Mikael Lyngvig <mikael at lyngvig.org> wrote: > One project I'd like to complete pretty soon is to go through the build > instructions, for mingw32, and see if I can't somehow create a mingw64 > build.  I believe the 32-bit platform is dying by the hour so I'm rather > eager to have a mingw64 version of LLVM/Clang.  Also, I'd love

Hi, I was wondering if you guys are using a tool of some sort for generating the HTML for LLVM or if you are writing it by hand? I am thinking of submitting some Windows-specific documentation because I honestly find it quite difficult to get things up and running with MINGW64. I may be daft, but so may others :-) As a former build master, I have a strong preference for documentation that

On Mon, Jun 18, 2012 at 6:25 AM, Mikael Lyngvig <mikael at lyngvig.org> wrote: > Hi all, > > Here's an updated version of my proposed "Building with MinGW on Windows" > document. In summary, the document gives a step-by-step description of how > to build LLVM + Clang on Windows WITHOUT having Microsoft Visual Studio > installed. The high-level goal of the

Is it possible to merger mingw32 and mingw64 with mingw, because we can distinguish them with arch(i386,amd64) 2009/8/15, Anton Korobeynikov <anton at korobeynikov.info>: > Hello > >> I add solaris and pic16. >> And add support for mingw. > Mingw part is not ok. The proper rules should be: > > i[[3456789]]86-*-mingw32* => mingw32 > x86_64-*-mingw* =>

I successfully used .Fortran to load and execute my fortran procedures under WinXP and 32 bit R. Alas, the same isn't true with my next Windows 7/64 machine, R 2.14.1 (64 bit) and the gnu gfortran (64) compiler (mingw64 v. 4.6.1). Though I'm able to compile the routines from the command line using gfortran '...', .Fortran('foo2') results in an error saying the Fortran