search for: compatibility

...3DFORMAT! 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 err:d3d:IWineD3DImpl_IsPixelFormatCompatibl...

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

...YS) 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: WINED3DFMT_R32_FLOAT err:d3d:IWineD3DImpl_Is...

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 @@

hi, I try to build hello.cpp using both llvmg++ and GNU g++, the generate llvm bytecode's size is about 960K, and the size of binary code generated by g++ is only 13K. Could anyone explain the difference between the two result? BWT: I rebuild the cfrontend in RH linux9.0, but when I build the hello.cpp the llvmG++ reports warnings too, it shows: ----------------------------- [yue at RH9

...t uses the newest ATLAS from > fink. It > has two-level namespaces and has a libR.dylib included. > > For R,bin you need on your system (remember to set DYLD_LIBRARY_PATH, > or --better-- install fink and compile these things yourself) > > /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, > current > version 55.0.0) > /sw/lib/libz.1.dylib (compatibility version 1.1.3, current > version 1.1.3) > /sw/lib/libreadline.4.dylib (compatibility version 4.2.0, > current version 4.2.0) > /sw/lib/libdl.dylib (compatibility version...

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) > /usr/lib/libstdc++.6.dylib (compatibility version 7.0.0, current version 56...

...gs it might provide and I could just remove all its inclusions. The build system should just detect its absence and generate an empty header in openbsd-compat/. * bzero is used in deattack.c (and in regress/) instead of the standard memset. The code should be changed to use memset or the compatibility layer should provide its own bzero if absent. * misc.c uses gettimeofday but doesn't include <sys/time.h> to get it. * timerclear, timerisset and timercmp are used in misc.c and ssh-keyscan.c. They are non-standard BSD extensions from <sys/time.h>. The build system should de...

...e on the first VirtIO disk, and it cannot chainload an OS which is not in the first VirtIO disk. +=item B<--vdsm-compat=0.10> + +=item B<--vdsm-compat=1.1> + +If I<-o vdsm> and the output format is qcow2, then we add the qcow2 +I<compat=0.10> option to the output file for compatibility with RHEL 6 +(see L<https://bugzilla.redhat.com/1145582>). + +If I<--vdsm-compat=1.1> is used then modern qcow2 (I<compat=1.1>) +files are generated instead. + +Currently I<--vdsm-compat=0.10> is the default, but this will change +to I<--vdsm-compat=1.1> in a future ve...

From: Sebastian Andrzej Siewior <sebastian at breakpoint.cc> OpenSSL 3.1.0 uses the same ABI as OpenSSL 3.0.x series. Further 3.1.x release are just stable updates and no ABI change (is expected) just like the 3.0.x series. Relax the version check for OpenSSL 3+ and rely on ABI compatibility. Signed-off-by: Sebastian Andrzej Siewior <sebastian at breakpoint.cc> --- 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...

..._cb xtables: nft: display rule by number via -L nft: associate table configuration to handle via nft_init nft: fix family operation lookup nft: load only the tables of the current family nft: refactoring parse operations for more genericity xtables: bootstrap ARP compatibility layer for nftables xtables: nft-arp: implements is_same op for ARP family xtables: arp: add rule replacement support xtables: arp: add delete operation xtables: arp: zeroing chain counters nft: arp: initialize flags in nft_arp_parse_meta nft: arp: add parse_targe...

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

...fically, F</boot> must be on the first VirtIO disk, and it cannot chainload an OS which is not in the first VirtIO disk. +=item B<--vdsm-compat-11> + +If I<-o vdsm> and the output format is qcow2, then by default the +I<compat=0.10> option is added to the output file for compatibility +with RHEL 6 (see L<https://bugzilla.redhat.com/1145582>). However if +this flag is given, then I<compat=1.1> is used instead (which is the +default for all other output modes). This flag will become the +default in a future version of virt-v2v. + =item B<--vdsm-image-uuid> UUI...

...e that this is due to symbols defined in libcloog itself because I see this same issue if I build gcc-fsf-4.7 using --without-cloog and --without-ppl to disable graphite support such that cc1 is linked as... /sw/lib/gcc4.7/libexec/gcc/x86_64-apple-darwin12.2.0/4.7.2/cc1: /sw/lib/libintl.8.dylib (compatibility version 10.0.0, current version 10.1.0) /sw/lib/libiconv.2.dylib (compatibility version 7.0.0, current version 7.0.0) /sw/lib/libmpc.3.dylib (compatibility version 4.0.0, current version 4.0.0) /sw/lib/libmpfr.4.dylib (compatibility version 6.0.0, current version 6.1.0) /sw/lib/gmp5/libgmp.10.d...

...ges 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 to provide the relevant libssl and libcrypto .so files, usin...

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