Alexander Pyhalov

``` $ abi-compliance-checker --test Using GCC 4.9.4 (i386-pc-solaris2.11, target: x86) verifying detectable C library changes ERROR: can't compile libsample_c v.1: 'libsample_c/libsample.v1/build-log.txt' $ cat libsample_c/libsample.v1/build-log.txt libsample.c: In function 'returnTypeBecameConst': libsample.c:13:64: warning:...

If I add these options to /usr/share/abi-compliance-checker/modules/Internals/RegTests.pm , I see $ abi-compliance-checker --testUsing GCC 4.9.4 (i386-pc-solaris2.11, target: x86) verifying detectable C library changes preparation, please wait ... Using GCC 4.9.4...

Looks better. I have binutils. ``` $ abi-compliance-checker --test Using GCC 4.9.4 (i386-pc-solaris2.11, target: x86) verifying detectable C library changes preparation, please wait ... Using GCC 4.9.4 (i386-pc-solaris2.11, target: x86)...

Hello. Seems to be even better (now I patched it to use exuberant-ctags): ``` --- abi-compliance-checker-31007a47094495e4e63edc5a226241ca3811701d/abi-compliance-checker.pl 2016-10-26 12:35:37.000000000 +0300 +++ abi-compliance-checker-31007a47094495e4e63edc5a226241ca3811701d/abi-compliance-checker.pl 2016-10-26 23:05:49.408976703 +0300 @@ -8170,6 +8170,13 @@ printMsg("WARNING", "can't...

Now I've tried on libXfont (update from 1.4.9 to 1.5.2), I know it's incompatible, as some symbols were removed. Unfortunately, abi-compliance-checker didn't detect it. ``` $ cat NEW.xml 1.5.2 /export/home/alp/srcs/tests/oi-userland/components/x11/libXfont/build/prototype/i386/usr/include...

``` $ abi-compliance-checker -test-dump -debug Using GCC 4.9.4 (i386-pc-solaris2.11, target: x86) verifying detectable C library changes executing perl /usr/bin/abi-compliance-checker -l libsample_c -old libsample_c/v1.xml -new libsample_c/v2.xml -cxx-incompatible -lang C -use-dumps -debug...

Xfont case debug is here: http://buildzone.oi-build.r61.net/compat/Xfont-debug.tar

@alarcher Are there any chances to migrate to 64-bit-by-default gcc till October?

Wanted to work on vagrant prerequirements, but so far it seems I've managed only to prepare Ruby build infrastructure to support multiple packages built from one source (like Python one)....

Using hostnames is default mode in our usage scenarios. This allows more flexibility - for example, they can be differently resolved in different VMs, this allows us, for example, to...