search for: below

...Wed, Jul 23, 2008 at 10:39:38AM +0200, maximilian attems wrote: > > > klibc mount has only short options thus uses the following syntax > > Frankly, it seems like a klibc problem... well not directly, but right klibc-utils should have proper syntax. initramfs-tools currently uses belows syntax. before we unmounted and remounted, which is much uglier. or even better have the util-linux-ng mount compiled against klibc, haven't looked into that project yet. a hook script (live-initramfs) seems to add util-linux-ng mount for cifs support and thus belows error came to sight. &...

Hi, I tried to enable virtio-blk data plane feature for VMs in my openstack environment, the hypervisor is ubuntu 14.04, libvirt 1.2.2 and QEMU 2.0. As nova doesn't support that parameter yet, I did belows 1. nova boot a VM with raw disk image. 2. nova stop the VM. 3. run "virsh edit <instance-id>" on the hyprvisor node, and adding below into instance xml just before </domain>. However, the <qemu:commandline> part is ignored and not saved after closing virsh edit, seems...

hi see below's conversation. it seems the e100p card doesn't work with BT. Any idea how this'll work against Telenor (norway)? roy <RoyK> does anyone know if I can trust the E100P to do full PRI stuff in .no? <cypromis> dunno about no <cypromis> I cannot use it in UK <cypromis...

belows patch is a first step towards a mntent.h we'll need it anyways later for mdadm support. it allows to compile util-linux-ng mount against klibc. due to the missing features there is a severe size difference: text data bss dec hex filename 1507 0 40 1547...

Hi, Does anyone tried to get ipip or gre tunnel behind NAT environments. ? i''m trying to make both side tunneling with ipip or gre with private address just like belows.. A -------------------FIRWWAL -------------------INET ------------------- B PRIVATE PUBLIC PUBLIC (10.100.0.1) (211.xxx.xxx.xxx) ( 211.xxx.xxx.xxx) is it possible to make both side connections with IPIP or GRE tu...

Hi, all It seems PPC JIT does not recognize inline assembly. For example, when I give LLVM IR belows to PPC JIT, %0 = tail call i32* asm "", "={r10}"() nounwind ; <i32*> [#uses=1] it complaints that inline assembly is not a supported instruction. x86 JIT works fine, however. Is there a reason that makes PPC JIT not support inline assembly? Currently, we modif...

After upgrading from 1.1.3 to 1.1.4 the imap process crashes as soon as moving a mail to the Trash folder. Belows backtrace points to the expire plugin... Backtrace /usr/local/libexec/dovecot/imap: Program terminated with signal 11, Segmentation fault. #0 0x2adbeaa8 in expire_mailbox_transaction_commit (t=0x10045248, uid_validity_r=0x7fff77fc, first_saved_uid_r=0x7fff7800, last_saved_uid_r=0x7fff7804)...

...+ gene4 chr1 20 25 6 + gene5 chr1 30 40 11 + I just wondering is there an efficient way to find overlapped, upstream and downstream genes for each gene in the granges For example, assuming all_genes_gr is a ~50000 genes genomic range, the result I want like belows: gene_nameupstream_genedownstream_geneoverlapped_gene gene1NAgene2NA gene2gene1gene4gene3 gene3gene1gene4gene2 gene4gene3gene5NA Currently , the strategy I use is like that, library(GenomicRanges) find_overlapped_gene <- function(idx, all_genes_gr) { #cat(idx, "\n") curr_gene...

Hi, all What I want to do is to locate the range of a for-loop statement in a binary. For example, given a for-loop statement belows, for (stat1; stat2; stat3) { /* do something */ } Is it possible to get information about the range (binary address) of the above for-loop, say, 0x0100 - 0x0120. One idea comes up in my mind is adding passes to retrieve such information in LLVM, then use llvm-gcc to compile the code....

Hi, all On the dragonedd website, there is a line "It is a reimplementation of llvm-gcc that works with gcc-4.5 or later." I am trying to make gcc-4.6 work woth dragonegg, but I get an error belows, ------------------------------------------------------------------------ Compiling cache.c /tmp/chenwj/dragonegg-2.9/cache.c: In function 'llvm_set_cached': /tmp/chenwj/dragonegg-2.9/cache.c:101: warning: implicit declaration of function 'GGC_NEW' /tmp/chenwj/dragonegg-2.9/cache....

sparc still needs gcc-3.3 for a working run-init. belows makes use of the exported CC var. Signed-off-by: maximilian attems <maks@sternwelten.at> diff --git a/scripts/Kbuild.klibc b/scripts/Kbuild.klibc index 66e16e7..70e4071 100644 --- a/scripts/Kbuild.klibc +++ b/scripts/Kbuild.klibc @@ -72,7 +72,7 @@ KLIBCROSS := $(CROSS_COMPILE) #...

klibc doesn't currently build on s390 since commit 1e8e338325fa0f2bd5c1c800086e900cf188d2cd belows patch adds some kernel ifdef for the newly added section. Signed-off-by: maximilian attems <maks@sternwelten.at> --- linux-2.6.15/include/asm-s390/setup.h.orig 2006-02-01 11:27:00.000000000 +0100 +++ linux-2.6.15/include/asm-s390/setup.h 2006-02-01 11:31:54.000000000 +0100 @@ -67,6 +67,8...

...since the kbuild switch: In file included from include/sys/mman.h:11, from klibc/malloc.c:8: linux/include/asm/page.h:18:2: error: #error No page size specified in kernel configuration the current dirty build hack is to define CONFIG_SPARC64_PAGE_SIZE_8KB in the sparc64 MCONFIG. belows patch removes the asm/page.h include. another way to fix that would be to move the __KERNEL__ definition up in the asm-sparc64/page.h, i'm not sure which is preferrable. warning: belows patch is only compile and runtime tested on x86, but i didn't see any PAGE_SIZE usage in the klibc tree...

On Wed, Apr 05, 2006 at 10:45:51PM +0200, maximilian attems wrote: [Received a forward of this mail and I had deleted the original one. So your reply-chain is broken]. > > sparc still needed to build with gcc-3.3 > belows makes use of the exported CC variable. > > also export the binutils for consistency, > added the missing ones too for klcc. > > > diff --git a/Makefile b/Makefile > index bfae8de..640eec4 100644 > --- a/Makefile > +++ b/Makefile > @@ -19,6 +19,11 @@ export ARCH :=...

Hi 陳韋任, > It seems PPC JIT does not recognize inline assembly. > For example, when I give LLVM IR belows to PPC JIT, > > %0 = tail call i32* asm "", "={r10}"() nounwind ;<i32*> [#uses=1] > > it complaints that inline assembly is not a supported > instruction. x86 JIT works fine, however. I'm surprised this worked with the x86 JIT - I thought the JIT d...

...PPC backend, I am not sure why PPC JIT see all inline assembly IRs as an error. Ding-Yong On Thu, Mar 24, 2011 at 2:53 PM, Duncan Sands <baldrick at free.fr> wrote: > Hi 陳韋任, > > > It seems PPC JIT does not recognize inline assembly. > > For example, when I give LLVM IR belows to PPC JIT, > > > > %0 = tail call i32* asm "", "={r10}"() nounwind ;<i32*> [#uses=1] > > > > it complaints that inline assembly is not a supported > > instruction. x86 JIT works fine, however. > > I'm surprised this worked with...

...ne step A previously? >> It seems you are not compiling against the preconfigured linux headers >> otherwise the headers_install wouldn't fail. >> > Yes, step A is done. > But the Makefile in src/linux/usr doesn't contain any target > `headers_install' so the below command with -C to src/linux/usr fails: > > make -C /root/gen/trunk/knl/linux/usr/ ARCH=ppc > INSTALL_HDR_PATH=/tmp/klibc-install/lib/klibc/ headers_install > make[2]: *** No rule to make target `headers_install'. Stop. > make[1]: *** [header] Error 2 > Note that step B is w...

...buntu 14.04, libvirt 1.2.2 > > [I haven't tested the virtio-blk data plane myself.] > > This libvirt version seems a little old (from March 2014), you might > want to move to a bit newer. > > > and QEMU 2.0. > > As nova doesn't support that parameter yet, I did belows > > > > 1. nova boot a VM with raw disk image. > > 2. nova stop the VM. > > 3. run "virsh edit <instance-id>" on the hyprvisor node, and adding below > > into instance xml just before </domain>. > > You're modifying the guest definition...

Hi, trying to develop this idea of splitting c++ classes into real interface and implementation and to make a std isocpp proposal out of it. Need some help and info to make the proposal cover as many details as possible. The idea is to split the class declaration into a part that will stay in the header and will contain only the public members. (let's ignore protected for the moment). The

...n my T1 (Sangoma), and failed pretty badly. Seemingly everything worked -- Asterisk would see the incoming call (including CID and DID info), try to route it, and fail -- giving me a telco (not Asterisk) call failure message. My zapata.conf and zaptel.conf files are at http://pastebin.com/558349 Below's the log dump. Note that, because I was simply going from CAS to PRI, I don't believe the span definition line, itself, should have changed. If anyone has any ideas, I'd sure be interested... -- Accepting call from '1234567890' to '1630' on channel 0/1, span 1 Enable...