search for: compatible

...gnized 909198916 (as fourcc: DF16) WINED3DFORMAT! fixme:d3d:getFormatDescEntry Can't find format unrecognized(909198916) in the format lookup table err:d3d:getColorBits Unsupported format: WINED3DFMT_R32F err:d3d:getColorBits Unsupported format: WINED3DFMT_R32F err:d3d:IWineD3DImpl_IsPixelFormatCompatibleWithRenderFmt Unable to check compatibility for Format=WINED3DFMT_R32F err:d3d:getColorBits Unsupported format: WINED3DFMT_R32F err:d3d:IWineD3DImpl_IsPixelFormatCompatibleWithRenderFmt Unable to check compatibility for Format=WINED3DFMT_R32F err:d3d:getColorBits Unsupported format: WINED3DFMT_R32F...

Dear All, first of all I must admit I posted this problem on the CentOs forum yesterday, with 0 replies so far. :-( I'm googling this problem all weekend, and getting a bit desperate actually. I'm working on a new Dell Vostro 3460. It has a Atheros Communications Inc. AR8161 Gigabit Ethernet carc that I cannot get to work. There's no enty in

...nimplemented action: 59 (SPI_SETSTICKYKEYS) fixme:system:SystemParametersInfoW Unimplemented action: 53 (SPI_SETTOGGLEKEYS) fixme:system:SystemParametersInfoW Unimplemented action: 51 (SPI_SETFILTERKEYS) err:d3d:getColorBits Unsupported format: WINED3DFMT_R32_FLOAT err:d3d:IWineD3DImpl_IsPixelFormatCompatibleWithRenderFmt Unable to check compatibility for Format=WINED3DFMT_R32_FLOAT err:d3d:getColorBits Unsupported format: WINED3DFMT_R32_FLOAT err:d3d:IWineD3DImpl_IsPixelFormatCompatibleWithRenderFmt Unable to check compatibility for Format=WINED3DFMT_R32_FLOAT err:d3d:getColorBits Unsupported format: W...

Building OpenSSH without deprecated APIs compiled causes it to fail. Signed-off-by: Rosen Penev <rosenp at gmail.com> --- openbsd-compat/openssl-compat.h | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/openbsd-compat/openssl-compat.h b/openbsd-compat/openssl-compat.h index 9e0264c0..b4f0908f 100644 --- a/openbsd-compat/openssl-compat.h +++ b/openbsd-compat/openssl-compat.h @@

...heapsize=48067 gccas -o /tmp/ccppFGsT.o /tmp/ccb5CDSP.s gccld -o hello -L/home/yue/cfrontend/install/lib/gcc/i686-pc-linux-gnu/3.4-llvm -L/home/yue/cfrontend/install/lib/gcc/i686-pc-linux-gnu/3.4-llvm/../../.. /tmp/ccppFGsT.o -lstdc++ -lm -lc -lcrtend WARNING: Found global types that are not compatible: [16 x sbyte]* %_ZN9__gnu_cxx10messages_cE "struct.std::messages<char>"* %_ZN9__gnu_cxx10messages_cE WARNING: Found global types that are not compatible: [16 x sbyte]* %_ZN9__gnu_cxx10messages_wE "struct.std::messages<char>"* %...

Hy Jan, I'll put a copy on cran today. Thanks. stefano > > Get it from ftp://gifi.stat.ucla.edu in pub. > > This contains the base files plus the recommended packages (except > rpart, > which does not compile yet). > > It is compiled under MacOS X 10.1.2 with the December 2001 version > of > the Developer Tools, and with g77 from fink.sourceforge net.

On Wed, 19 Feb 2020 at 06:38, Val Baranov <val.baranov at duke.edu> wrote: > AIX 7.1 TL5, OpenSSL ver. 1.1.1d. "vac.C" version 11.0.1.23 > Compilation error " The indirection operator cannot be applied to a pointer to an incomplete struct or union " (see full log below) produced for " libressl-api-compat.c ". > No such error if compiled with OpenSSL

v3: Change the flag from --vdsm-compat-11 to --vdsm-compat=1.1 Also the --machine-readable output has changed. I have also added a test. Rich.

Package: xen Version: 4.6.0-1+nmu2 Severity: serious This package fails to build in unstable: > sbuild (Debian sbuild) 0.68.0 (15 Jan 2016) on dl580gen9-02.hlinux ... > mkdir -p compat > grep -v 'DEFINE_XEN_GUEST_HANDLE(long)' public/grant_table.h | \ > python /<<PKGBUILDDIR>>/debian/build/build-hypervisor_amd64_amd64/xen/tools/compat-build-source.py

Hi Jack, > It is interesting though that LLVMPolly.so shows the linkage... > > /sw/opt/llvm-3.2/lib/LLVMPolly.so: > /sw/lib/libisl.10.dylib (compatibility version 11.0.0, current version 11.0.0) > /sw/lib/gmp5/libgmp.10.dylib (compatibility version 11.0.0, current version 11.5.0) > /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 169.3.0) >

Hi, I recently ported OpenSSH to my hobbyist operating system. The portable release is very straightforward to work with, but it had a few minor issues where it assumes the existence of things that might not be on a POSIX 2008 system. This are the list of issues I encountered that I believe makes sense to upstream. * <sys/param.h> is included in many files and isn't a standard

Support for RHEV with RHEL 6 nodes required us to output the old style qcow2 compat=0.10 images. Since RHEV 3.6 GA, RHEL 6 has not been supported as a RHEV node type. Since RHV 4.1, compat=1.1 is supported. (Support for compat=1.1 is uncertain in RHV 4.0 even on RHEL 7 nodes.) There are significant downsides to using qcow2 compat=0.10 instead of the modern default (compat=1.1). Therefore this

...--- openbsd-compat/openssl-compat.c | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/openbsd-compat/openssl-compat.c b/openbsd-compat/openssl-compat.c index c1749210d586f..5b35253f1d19b 100644 --- a/openbsd-compat/openssl-compat.c +++ b/openbsd-compat/openssl-compat.c @@ -54,6 +54,10 @@ ssh_compatible_openssl(long headerver, long libver) return (headerver & mask) == (libver & mask); } + /* For versions > 3.0.0, we rely on upstream's ABI */ + if (headerver > 0x3000000f) + return 1; + /* * For versions >= 1.0.0, major,minor must match and library * fix version...

Hi! The Netfilter project proudly presents: iptables 1.6.0 This release includes accumulated fixes and enhancements for the following matches: * ah * connlabel * cgroup * devgroup * dst * icmp6 * ipcomp * ipv6header * quota * set * socket * string and targets: * CT * REJECT * SET * SNAT * SNPT,DNPT * SYNPROXY * TEE We also got rid of the very very old MIRROR and SAME targets and the

On Wednesday, 7 December 2016 10:02:49 CET Richard W.M. Jones wrote: > Support for RHEV with RHEL 6 nodes required us to output the old style > qcow2 compat=0.10 images. Since RHEV 3.6 GA, RHEL 6 has not been > supported as a RHEV node type. Since RHV 4.1, compat=1.1 is > supported. (Support for compat=1.1 is uncertain in RHV 4.0 even on > RHEL 7 nodes.) > > There are

Support for RHEV with RHEL 6 nodes required us to output the old style qcow2 compat=0.10 images. Since RHEV 3.6 GA, RHEL 6 has not been supported as a RHEV node type. Since RHV 4.1, compat=1.1 is supported. Support for compat=1.1 is uncertain in RHV 4.0 even on RHEL 7 nodes. There are significant downsides to using qcow2 compat=0.10 instead of the modern default (compat=1.1). Therefore this

...just a symlink to libSystem.dylib. This linkage shifts the failure to... % gcc-fsf-4.7 -fplugin=/sw/lib/gcc4.7/lib/dragonegg.so -fplugin-arg-dragonegg-llvm-option=-load:/sw/opt/llvm-3.2/lib/LLVMPolly.so -O3 himenoBMTxpa.c himenoBMTxpa.c: In function 'main': himenoBMTxpa.c:79:5: warning: incompatible implicit declaration of built-in function 'strcpy' [enabled by default] himenoBMTxpa.c: In function 'set_param': himenoBMTxpa.c:226:5: warning: incompatible implicit declaration of built-in function 'exit' [enabled by default] himenoBMTxpa.c: In function 'newMat': hi...

...k why upstream and CentOS provide no compat-openssl packages like Novell does in SUSE. We are trying to install binaries for gLite (a huge toolkit for grid computing linked against upstream v4 libraries) on CentOS 5. I was under the impression that this would be possible because v5 is "binary-compatible" with v4. But it seems this "binary compatibility" doesn't extend to OpenSSL. What, then, is the scope of the upstream and CentOS binary compatibility guarantees? (OpenSSL is not yet in the LSB; is this significant?) We will probably want to roll our own compat-openssl packages...

Hi, > maas34:openssh-2.9p2 {172} make > gcc -o ssh-keyscan ssh-keyscan.o -L. -Lopenbsd-compat/ -R/home/eedalf/lib -L/home/eedalf/lib -L/home/eedalf/lib -ldsocks -L/opt/local/zlib-1.1.2/lib -L/usr/local/lib -R/usr/local/lib -lssh -lopenbsd-compat -lz -lsocket -lnsl -lgen -lcrypto > Undefined first referenced > symbol in file

Hello, I need to run rsync on a mac (OS X 10.6.5) with the --detect-renamed option available. I therefore started to compile rsync with the 3 relevant patches (in my opinion) : - fileflags.diff - crtimes.diff - detect-renamed.diff Here are my exact compile instructions : patch -p1 <patches/fileflags.diff patch -p1 <patches/crtimes.diff patch -p1 <patches/detect-renamed.diff