search for: goobuntu

...asan_malloc_linux.cc:57:1: error: declaration of 'void free(void*)' has > a different exception specifier > /usr/include/malloc.h:66:13: error: from previous declaration 'void > free(void*) throw ()' Looking at /usr/include/malloc.h I don't see any instances of throw() (Goobuntu Lucid) Shouldn't we have the same set of standard headers?

...or: declaration of 'void free(void*)' > has > > a different exception specifier > > /usr/include/malloc.h:66:13: error: from previous declaration 'void > > free(void*) throw ()' > Looking at /usr/include/malloc.h I don't see any instances of throw() > (Goobuntu Lucid) > Shouldn't we have the same set of standard headers? > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev > -------------- next part...

Hello, On modern Linux installs, glibc has a very annoying practice: it adds an empty exception specifier to lots of libc functions as an optimization. It only does this if the compiler is modern and GCC-like, and we are compiling in C++ mode. This, however, causes GCC to complain about signature mismatches between the glibc functions declared in malloc.h and those defined as an alias in the

...void >> free(void*)' has >> > a different exception specifier >> > /usr/include/malloc.h:66:13: error: from previous declaration 'void >> > free(void*) throw ()' >> Looking at /usr/include/malloc.h I don't see any instances of throw() >> (Goobuntu Lucid) >> Shouldn't we have the same set of standard headers? >> _______________________________________________ >> LLVM Developers mailing list >> LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu >> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev >>...

...oid*)' has >>> > a different exception specifier >>> > /usr/include/malloc.h:66:13: error: from previous declaration 'void >>> > free(void*) throw ()' >>> Looking at /usr/include/malloc.h I don't see any instances of throw() >>> (Goobuntu Lucid) >>> Shouldn't we have the same set of standard headers? >>> _______________________________________________ >>> LLVM Developers mailing list >>> LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu >>> http://lists.cs.uiuc.edu/mailman/listin...

...listlibvirt-users@redhat.comhttps://www.redhat.com/mailman/listinfo/libvirt-users > > > > _______________________________________________ > libvirt-users mailing list > libvirt-users@redhat.com > https://www.redhat.com/mailman/listinfo/libvirt-users > -- Nikki VonHollen Goobuntu Team <https://goto.google.com/goobuntu> 540-553-1904

https://bugzilla.mindrot.org/show_bug.cgi?id=1990 Bug #: 1990 Summary: sftp segfaults when tab-completing a directory which contains umlauts Classification: Unclassified Product: Portable OpenSSH Version: 5.9p1 Platform: amd64 OS/Version: Linux Status: NEW Severity: normal

Thanks Dominique & Daniel. Looks like i need to upgrade my VMs kernel to make it aware of virtio. Found this information from this link: http://wiki.libvirt.org/page/Virtio#Disk_.28block.29_device_driver I tried without upgrading the Kernel and as soon as i start my VM it got into Kernel Panic. I will try using virtio after upgrading my VMs kernel. Thanks for all the responses and