Displaying 20 results from an estimated 2000 matches similar to: "Libvirt Compilation on MS Vista"
2010 Apr 28
2
Windows Client
Having newly compiled a Libvirt on a Windows Vista machine (many thanks to
Matthias Bolte) I have attempted to connect to a remote Ubuntu machine using
virsh.exe. However, the connection fails as follows:
$ virsh -c qemu+tcp:///system
error: unable to connect to libvirtd at 'localhost': errno=10061
error: failed to connect to the hypervisor
1. I have modified
2011 Nov 14
2
[LLVMdev] Build LLVM as a DLL on Windows x86
Hi Takumi,
> > Otherwise,
> > I haven't installed binutils since I don't seem to need it.?
>
> You need binutils, esp. ld, nm, objdump.
>
> FYI, how to browse export table in DLL with objdump; $ objdump -x
> XXX.dll
Ok, I got the latest version of binutils from
http://sourceforge.net/projects/mingw/files/MinGW/Base/binutils/.
> > As you can tell, I am
2011 Nov 14
0
[LLVMdev] Build LLVM as a DLL on Windows x86
2011/11/13 Alan Garny <agarny at hellix.com>:
> Now, I know that shared libraries are not supported on Windows using CMake
> (according to http://www.llvm.org/docs/CMake.html) which would have been my
> preferred building choice, but I didn’t see anything against them not being
> supported using Autotools, so I thought I would try it that way (as I
> successively did on Linux
2011 Nov 13
5
[LLVMdev] Build LLVM as a DLL on Windows x86
Hi,
I need to build a shared version of LLVM on Windows, Linux (both x86 and
x64) and Mac OS X. So far, I have been able to build LLVM on Linux and Mac
OS X, and it's all working fine as confirmed by a small LLVM test code that
I wrote.
However, on Windows, even though I get a DLL, that DLL doesn't contain any
(exported) functions (according to DLL Export Viewer; see
2011 Nov 14
0
[LLVMdev] Build LLVM as a DLL on Windows x86
"Alan Garny" <agarny at hellix.com> writes:
>> GNU make is essential to msys build. I guess msysdtk would have it.
>
> I could find a copy of msysDTK at
> http://sourceforge.net/projects/mingw/files/Other/Unsupported/MSYS/msysDTK/,
> but not only is the 'latest' version a very old version (2003!), but once
> installed I couldn't find a copy of
2006 Apr 30
0
[LLVMdev] Building LLVM under Mingw. Part I: tools-only
BTW: I've also had to make this change when building tools.
(I'm building right now and noticed that it doesn't come up anymore, maybe
someone checked it in in the last week or so)
On Sat, 29 Apr 2006, Anton Korobeynikov wrote:
> Hello, Jeff.
>
> You wrote Saturday, April 29, 2006, 10:45:02 PM:
>
> JC> Yes, I know mingw doesn't support dbghelp. I can still rant
2011 Nov 14
2
[LLVMdev] Build LLVM as a DLL on Windows x86
> >> GNU make is essential to msys build. I guess msysdtk would have it.
> >
> > I could find a copy of msysDTK at
> >
> http://sourceforge.net/projects/mingw/files/Other/Unsupported/MSYS/msy
> > sDTK/, but not only is the 'latest' version a very old version
> > (2003!), but once installed I couldn't find a copy of gmake in it.
>
>
2008 May 30
4
[LLVMdev] Possibly Vista-related Windows/MinGW Compilation Issues
Hello, Jonathan
> I thought I'd messed up something related to the linker,
> but I couldn't explain why XP would work using the same steps.
The only thing comes to my mind seeing this: perl from msysDTK works
differently (somehow) on Vista, thus llvm-config is broken which leads
to missed libraries, broken dependencies, etc.
I'd suggest you to compare stuff on different
2006 Apr 29
2
[LLVMdev] Building LLVM under Mingw. Part I: tools-only
Hello, Jeff.
You wrote Saturday, April 29, 2006, 10:45:02 PM:
JC> Yes, I know mingw doesn't support dbghelp. I can still rant about it :)
;) Well. Maybe this library will be included in some next versions of
mingw's win32api package. Anyway, we can make such library just
"on-fly" from the corresponding .dll.
JC> This is what's already there. What changed?
Maybe
2007 Nov 28
5
[LLVMdev] LLVM on MinGW
Hello,
I'm trying to use LLVM on Windows, using the MinGW toolchain that comes
with Cygwin (gcc -mno-cygwin, not the standalone msys package). Has
anyone successfully built LLVM from sources with this toolchain?
The ./configure scripts automatically detects a Cygwin environment. I've
spent some time trying to let it know that it should compile for MinGW.
FWIW, here's what I've
2010 Apr 30
2
Windows Vista Client Fails to Connect to Ubuntu libvirtd
Requesting urgent assistance if I may?
Attempting to connect to an Ubuntu machine using an MinMG compiled virsh on
a Windows Vista machine. Using insecure TCP simply to prove a concept to a
client. However, cannot connect; situation as follows:
Edited /etc/libvirt/libvirt.conf as follows:
listen_tcp = 1
auth_tcp = "none"
Edited /etc/default//libvirt-bin as follows:
2008 Feb 05
1
[LLVMdev] Working on getting MingW32/native tools-only source build up
Hello, Kenneth
> Using MingW32/GCC 4.2.1 binary release, mix of Cygwin and MingW32
> auxilliary tools, ActivePerl's Perl 5.8.8; operating system Vista. I'm
> not going to worry about bootstrapping llvm-gcc until I know I can
> bootstrap gcc.
Don't do this. Use either pure cygwin or pure mingw (with msys + msysDTK)
installation. This will save bunch of time for you.
2009 Aug 06
3
[LLVMdev] Problems building on Msys/MingW
Hi,
I'm trying to build clang under MingW, but I'm getting a number of errors.
Could anyone provide some hints as to what you had to do? I got some tips
from
http://blogs.tedneward.com/2008/02/24/Building+LLVM+On+Windows+Using+MinGW32.aspx,
but using the newer packages, as it's a bit old.
The ./configure seems to run without errors.
The first run of make aborts with errors like:
2005 Mar 10
0
[LLVMdev] VC++ 2003
Vyacheslav Akhmechet wrote:
>Then add llvm/win32\tools folder to a list of executable
>search paths in VC options->directories.
>
Actually, this is not required and the projects are set up to work
without that directory being in the search path. That list of
directories is global to the whole machine, and it is bad form for LLVM
to have an impact on any other solutions that you
2005 Mar 10
2
[LLVMdev] VC++ 2003
I am currently playing around with llvm using Visual C++ Express
(beta). It works flawlessly. It takes a while to get started but once
you do, everything is perfect. Make sure to get the latest CVS
sources, the 1.4 release doesn't play nice with Visual Studio. Once
you do, extract the file I attach to this email into the llvm\win32
folder. Then add llvm/win32\tools folder to a list of
2007 Nov 28
0
[LLVMdev] LLVM on MinGW
SVN head LLVM and Clang built out of the box for me a week ago on MSYS/
MINGW, using the following files:
MinGW-5.1.3.exe
MSYS-1.0.10.exe
msysDTK-1.0.1.exe
bash-3.1-MSYS-1.0.11-1.tar.bz2
bison-2.3-MSYS-1.0.11.tar.bz2
coreutils-5.97-MSYS-1.0.11-snapshot.tar.bz2
flex-2.5.33-MSYS-1.0.11.tar.bz2
gawk-3.1.5-MSYS-1.0.11-snapshot.tar.bz2
regex-0.12-MSYS-1.0.11.tar.bz2
1. install these components
2.
2005 Jul 08
3
McLeod Integrated T1 - no PRI?
Hello everyone,
We have recently turned up a new T1 from McLeod (Midwestern CLEC). It
is configured like so:
/etc/zaptel.conf:
loadzone=us
defaultzone=us
span=1,0,0,esf,b8zs ;(also tried 1,1,0,esf,b8zs)
bchan=13-23
nethdlc=1-12
dchan=24
/etc/zapata.conf:
switchtype=national
context=pri-in
signalling=pri_cpe
group=1
channel => 13-23
I can get hdlc0 (and pvc0) up just fine after the
2008 May 30
0
[LLVMdev] Possibly Vista-related Windows/MinGW Compilation Issues
Anton Korobeynikov wrote:
> Hello, Jonathan
>
>
>> I thought I'd messed up something related to the linker,
>> but I couldn't explain why XP would work using the same steps.
>>
> The only thing comes to my mind seeing this: perl from msysDTK works
> differently (somehow) on Vista, thus llvm-config is broken which leads
> to missed libraries,
2009 Feb 12
9
Schedule oddity
I have the following set up:
schedule {nightly:
period => daily,
range => "18 - 23",
repeat => 1
}
define deadlypkg {
tag("package")
$pkgrepo="/staging/PRODUCTION/deadly"
package{"$name":
source => "$pkgrepo/$name.pkg",
ensure => latest,
adminfile
2010 Sep 27
2
[LLVMdev] Compiling LLVM 2.7 with MinGW GCC 4.5.0
> Could you post the errors message? Sounds like bug in mingw's gcc / ld.
It's very long, maybe I should just attach the log? I only remember the
first line saying: --export-dynamic is not supported for PE targets, do you
mean --export-all-symbols? *or something similar to this* then a bunch of
undefined references occur.
--
View this message in context: