similar to: Re: How about this replacement of WINE.

Has the wine project team pondered whether to move WINE into the kernel?

Dan Kegel wrote: > On Sun, Apr 6, 2008 at 6:55 AM, bussuser <wineforum-user at winehq.org> wrote: > > > Has the wine project team pondered whether to move WINE into the kernel? > > > > Yes, it's been discussed many times. > It turns out it's not worth the effort yet. > There are many lower-hanging fruit. > - Dan but Mao the leader of the

http://www.reactos.org/forum/viewtopic.php?t=5240 It is based on WINE and ReactOS . The project is sponsored by a chinese company.

Dan Kegel wrote: > On Sun, Apr 6, 2008 at 8:09 PM, bussuser <wineforum-user at winehq.org> wrote: > > > but ... http://translate.google.com/translate?u=http%3A%2F%2Flinux.insigma.com.cn%2Fjszl.asp%3Fdocid%3D122805676&langpair=zh%7Cen&hl=en&ie=UTF-8 > > > > Sadly, it looks like they used ReactOS code. This might be > a problem, since some of the

I got through with reactos.org using proxy.org! however, silly ISP won't offer support still... I'm going to give them a piece of mind soon... anyway back on topic now. I can finally find this thingy...

Just finished the compiling llvm without llvm-gcc from svn. Tried it out. Got g++ -o hlvm.o -c -I/farhome/hendrik/dv/llvm/llvm/include -D_DEBUG -D_GNU_SOURCE -D__STDC_LIMIT_MACROS -g -Woverloaded-virtual hlvm.cpp In file included from /farhome/hendrik/dv/llvm/llvm/include/llvm/DerivedTypes.h: 21, from hlvm.cpp:1: /farhome/hendrik/dv/llvm/llvm/include/llvm/Type.h:19:31: error:

Hendrik, You could also just "touch ~/.cvspass" to create the file which should eliminate the warning. However, since you did a login, and it seemed successful, chances are the file now exists (containing the blank password for anon at llvm.org). Reid. On Mon, 2006-08-07 at 09:14 -0500, John Criswell wrote: > Hendrik Boom wrote: > > I tried to access the latest LLVM, since

I took the first two lines of the sample program in the tutorial: hendrik at lovesong:~/dv/lang/hlvm$ cat broken.cpp #include "llvm/DerivedTypes.h" #include "llvm/Module.h" hendrik at lovesong:~/dv/lang/hlvm$ and tried to compile them using the llvm-dev in Debian testing: hendrik at lovesong:~/dv/lang/hlvm$ g++ -o broken.o -c broken.cpp In file included from

On Mon, 07 Aug 2006 09:26:07 -0700, Reid Spencer wrote: > Hendrik, > > You could also just "touch ~/.cvspass" to create the file which should > eliminate the warning. However, since you did a login, and it seemed > successful, chances are the file now exists (containing the blank > password for anon at llvm.org). Indeed, the file is there. > > Reid. >

I tried to access the latest LLVM, since several messages here so far have referred me to it. Now I have no experience with CVS-over-the-net. My previous experiences with versoin control have been RCS and Monotone. Brief summary: hendrik at lovesong:~/dv$ mkdir llvm hendrik at lovesong:~/dv$ cd llvm hendrik at lovesong:~/dv/llvm$ cvs -d :pserver:anon at llvm.org:/var/cvs/llvm login Logging in

You need to use the script 'llvm-config' to pass correct arguments to g ++: g++ -o broken.o `llvm-config --cxxflags` broken.cpp On Jun 2, 2008, at 9:43 AM, Hendrik Boom wrote: > I took the first two lines of the sample program in the tutorial: > > > hendrik at lovesong:~/dv/lang/hlvm$ cat broken.cpp > #include "llvm/DerivedTypes.h" > #include

Hello, by suggestion from linux-btrfs I post this to samba at lists.samba.org. I think, thiss is a bug in Samba. Can you confirm and suggest a workaround? Regards, Hendrik ------ Weitergeleitete Nachricht ------ Von: "Hendrik Friedel" <hendrik at friedels.name> An: "Btrfs BTRFS" <linux-btrfs at vger.kernel.org> Gesendet: 12.05.2019 13:27:00 Betreff: Btrfs Samba

Hendrik Boom wrote: > I tried to access the latest LLVM, since several messages here so far have > referred me to it. Now I have no experience with CVS-over-the-net. My > previous experiences with versoin control have been RCS and Monotone. > > Brief summary: > > hendrik at lovesong:~/dv$ mkdir llvm > hendrik at lovesong:~/dv$ cd llvm > hendrik at lovesong:~/dv/llvm$

On Mon, 02 Jun 2008 09:52:16 -0700, Thomas Hudson wrote: > You need to use the script 'llvm-config' to pass correct arguments to g > ++: > > g++ -o broken.o `llvm-config --cxxflags` broken.cpp > > Interesting. When I type the command as you provided it (using cut-and-paste) I get: hendrik at lovesong:~/dv/lang/hlvm$ g++ -o broken.o `llvm-config --cxxflags`

Hi, I just read the thread http://lists.samba.org/archive/rsync/2004-June/009678.html which describes how --keep-dirlinks came to be. My use case is similar, but I?d like a similar option for files as well. Setup: in my public_html I have some symlinks which I send over as files, with -L (for various reasons: partly, because they are copies of current work which is done elsewhere, or

Hello, I am trying to set sieve up on a Centos 7 server. It's a configuration with postfix, Maildir, MySQL and virtual domains which works fine. I have created a simple .dovecot.sieve in the user's directory: # cat /home/mail/domain.com/user/.dovecot.sieve require "fileinto"; redirect "other_address at other_domain.com"; Here are the logs: dovecot: lda(user at

There wouldn't happen to be an index telling one which libraries define which symbols, would there? For example, if I'm told alvm.o: In function `llvm::Function::Create(llvm::FunctionType const*, llvm::GlobalValue::LinkageTypes, std::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, llvm::Module*)':

On Tue, 03 Jun 2008 18:48:09 +0200, Matthijs Kooijman wrote: > Hi Hendrik, > >> -rw-r--r-- 1 hendrik sbox 1328 2008-06-03 10:00 iterator -rw-r--r-- >> 1 hendrik sbox 2418 2008-06-03 10:00 iterator.h.in > Did you run AutoGen.sh (not sure about case). I think that's needed when > compiling from svn, and it should generate the makefiles for building >

On 28.05.2014 15:27, Laine Stump wrote: > On 05/27/2014 09:07 AM, Jianwei Hu wrote: >> Hi All, >> >> I have one netcf question, please help me to resolve it, thanks. >> >> I can set a IFF_RUNNING flag to a bridge device which are no interface device attached. What status of a flag on a bridge device in current kernel?(w/o interface), is this a new change in kernel

On Sat, 05 Aug 2006 15:25:28 -0700, Reid Spencer wrote: > On Sat, 2006-08-05 at 14:45 -0400, Hendrik Boom wrote: >> The hardware requirements claim that there is no native code generation >> for the AMD 64. Is anyone working toward this? >> >> -- hendrik >> > Unfortunately, no. There is a scant beginning for x86_64 support, an > initial (read slow)