libffi_3.0.5-2_i386.changes ACCEPTED
Accepted: lib64ffi-dev_3.0.5-2_i386.deb to pool/main/libf/libffi/lib64ffi-dev_3.0.5-2_i386.deb lib64ffi5_3.0.5-2_i386.deb to pool/main/libf/libffi/lib64ffi5_3.0.5-2_i386.deb libffi-dev_3.0.5-2_i386.deb to pool/main/libf/libffi/libffi-dev_3.0.5-2_i386.deb libffi5-dbg_3.0.5-2_i386.deb to pool/main/libf/libffi/libffi5-dbg_3.0.5-2_i386.deb libffi5_3.0.5-2_i386.deb to pool/main/libf/libffi/libffi5_3.0.5-2_i386.deb libffi_3.0.5-2.diff.gz to pool/main/libf/libffi/libffi_3.0.5-2.diff.gz libffi_3.0.5-2.dsc to pool/main/libf/libffi/libffi_3.0.5-2.dsc Override entries for your package: lib64ffi-dev_3.0.5-2_i386.deb - extra libdevel lib64ffi5_3.0.5-2_i386.deb - extra libs libffi-dev_3.0.5-2_i386.deb - extra libdevel libffi5-dbg_3.0.5-2_i386.deb - extra libdevel libffi5_3.0.5-2_i386.deb - extra libs libffi_3.0.5-2.dsc - source libs Announcing to [EMAIL PROTECTED] Closing bugs: 480208 Thank you for your contribution to Debian. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#480208: marked as done (libffi-dev: amd64 headers inconsistent with actual binaries)
Your message dated Tue, 13 May 2008 07:02:13 + with message-id <[EMAIL PROTECTED]> and subject line Bug#480208: fixed in libffi 3.0.5-2 has caused the Debian Bug report #480208, regarding libffi-dev: amd64 headers inconsistent with actual binaries to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 480208: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=480208 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems --- Begin Message --- Package: libffi-dev Version: 3.0.5-1.0 Severity: critical Justification: causes serious data loss Because all the builds (native and bi-/tri-arch) install headers into /usr/include, /usr/include/ffi.h may wind up failing to correspond to the actual architecture of interest. In particular, on amd64, /usr/include/ffi.h winds up #define-ing X86 rather than the correct X86_64, breaking anything that builds against it. (ctypes catches the problem thanks to its test suite, but other reverse dependencies will require binNMUs.) The best way to fix this problem would arguably be to arrange for the non-native versions of ffi.h to wind up in /usr/include/$(host_triplet); however, that approach turns out to be somewhat cumbersome, particularly given that the top-level makefile neglects to propagate includedir or includesdir. :-/ Alternatively, it suffices to edit src/x86/ffitarget.h to honor __x86_64__ unconditionally, either by flipping the target specification (as it already does for the combination of X86_64 and __i386__) or by deconditionalizing the existing check for __x86_64__ further down: --- libffi-3.0.5.orig/src/x86/ffitarget.h +++ libffi-3.0.5/src/x86/ffitarget.h @@ -74,7 +74,7 @@ #define FFI_TYPE_SMALL_STRUCT_1B (FFI_TYPE_LAST + 1) #define FFI_TYPE_SMALL_STRUCT_2B (FFI_TYPE_LAST + 2) -#if defined (X86_64) || (defined (__x86_64__) && defined (X86_DARWIN)) +#if defined (X86_64) || (defined (__x86_64__) /* && defined (X86_DARWIN) */) #define FFI_TRAMPOLINE_SIZE 24 #define FFI_NATIVE_RAW_API 0 #else In principle, this issue could also affect other architectures, but AFAICT configure doesn't actually set different target names for any of them at present. (You could also simply install the native build last rather than first, but that would break builds for amd64 on i386 in the same fashion that native amd64 builds currently break unless you also fix ffitarget.h as described above.) At any rate, could you please fix the bug and (once a fixed build has hit the archive) request binNMUs for libffi5's reverse dependencies on amd64? Thanks! -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.25.0 (SMP w/2 CPU cores) Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/dash Versions of packages libffi-dev depends on: ii libffi5 3.0.5-1.0 Foreign Function Interface library libffi-dev recommends no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: libffi Source-Version: 3.0.5-2 We believe that the bug you reported is fixed in the latest version of libffi, which is due to be installed in the Debian FTP archive: lib64ffi-dev_3.0.5-2_i386.deb to pool/main/libf/libffi/lib64ffi-dev_3.0.5-2_i386.deb lib64ffi5_3.0.5-2_i386.deb to pool/main/libf/libffi/lib64ffi5_3.0.5-2_i386.deb libffi-dev_3.0.5-2_i386.deb to pool/main/libf/libffi/libffi-dev_3.0.5-2_i386.deb libffi5-dbg_3.0.5-2_i386.deb to pool/main/libf/libffi/libffi5-dbg_3.0.5-2_i386.deb libffi5_3.0.5-2_i386.deb to pool/main/libf/libffi/libffi5_3.0.5-2_i386.deb libffi_3.0.5-2.diff.gz to pool/main/libf/libffi/libffi_3.0.5-2.diff.gz libffi_3.0.5-2.dsc to pool/main/libf/libffi/libffi_3.0.5-2.dsc A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Matthias Klose <[EMAIL PROTECTED]> (supplier of updated libffi package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 13 May 2008 04:49:49 + Source: libffi Binary: libffi-dev lib32ffi-dev lib64ffi-dev libn32ffi-dev libffi5 lib32ffi5 lib64ffi5 libn32ffi5 libffi5-dbg Architecture: sourc
Results for 4.2.4 20080512 (prerelease) (Debian 4.2.3-6) testsuite on i486-pc-linux-gnu
LAST_UPDATED: Mon May 12 23:03:55 UTC 2008 (revision 135236) Target: i486-linux-gnu gcc version 4.2.4 20080512 (prerelease) (Debian 4.2.3-6) Native configuration is i486-pc-linux-gnu === g++ tests === Running target unix === g++ Summary for unix === # of expected passes13655 # of expected failures 67 # of unsupported tests 74 Running target unix/-fstack-protector === g++ Summary for unix/-fstack-protector === # of expected passes13655 # of expected failures 67 # of unsupported tests 74 Running target unix/-m64 === g++ Summary for unix/-m64 === # of expected passes13565 # of expected failures 67 # of unsupported tests 106 === g++ Summary === # of expected passes40875 # of expected failures 201 # of unsupported tests 254 /scratch/packages/gcc/4.2/gcc-4.2-4.2.3/build/gcc/testsuite/g++/../../g++ version 4.2.4 20080512 (prerelease) (Debian 4.2.3-6) === gcc tests === Running target unix UNRESOLVED: gcc.c-torture/execute/mayalias-2.c execution, -O3 -g === gcc Summary for unix === # of expected passes42620 # of expected failures 116 # of unresolved testcases 1 # of untested testcases 28 # of unsupported tests 295 Running target unix/-fstack-protector UNRESOLVED: gcc.c-torture/execute/mayalias-2.c execution, -O3 -g === gcc Summary for unix/-fstack-protector === # of expected passes42620 # of expected failures 116 # of unresolved testcases 1 # of untested testcases 28 # of unsupported tests 295 Running target unix/-m64 UNRESOLVED: gcc.c-torture/execute/mayalias-2.c execution, -O3 -g FAIL: gcc.dg/invalid-call-1.c non-compatible type (test for warnings, line 16) FAIL: gcc.dg/invalid-call-1.c (test for excess errors) UNRESOLVED: gcc.dg/torture/fp-int-convert-float128-timode.c -O0 compilation failed to produce executable UNRESOLVED: gcc.dg/torture/fp-int-convert-float128-timode.c -O1 compilation failed to produce executable UNRESOLVED: gcc.dg/torture/fp-int-convert-float128-timode.c -O2 compilation failed to produce executable UNRESOLVED: gcc.dg/torture/fp-int-convert-float128-timode.c -O3 -fomit-frame-pointer compilation failed to produce executable UNRESOLVED: gcc.dg/torture/fp-int-convert-float128-timode.c -O3 -g compilation failed to produce executable UNRESOLVED: gcc.dg/torture/fp-int-convert-float128-timode.c -Os compilation failed to produce executable UNRESOLVED: gcc.dg/torture/fp-int-convert-float128.c -O0 compilation failed to produce executable UNRESOLVED: gcc.dg/torture/fp-int-convert-float128.c -O1 compilation failed to produce executable UNRESOLVED: gcc.dg/torture/fp-int-convert-float128.c -O2 compilation failed to produce executable UNRESOLVED: gcc.dg/torture/fp-int-convert-float128.c -O3 -fomit-frame-pointer compilation failed to produce executable UNRESOLVED: gcc.dg/torture/fp-int-convert-float128.c -O3 -g compilation failed to produce executable UNRESOLVED: gcc.dg/torture/fp-int-convert-float128.c -Os compilation failed to produce executable FAIL: gcc.misc-tests/linkage.c link FAIL: gcc.target/i386/pr30961-1.c scan-assembler-not movapd === gcc Summary for unix/-m64 === # of expected passes42442 # of unexpected failures4 # of expected failures 127 # of unresolved testcases 13 # of untested testcases 28 # of unsupported tests 407 === gcc Summary === # of expected passes127682 # of unexpected failures4 # of expected failures 359 # of unresolved testcases 15 # of untested testcases 84 # of unsupported tests 997 /scratch/packages/gcc/4.2/gcc-4.2-4.2.3/build/gcc/xgcc version 4.2.4 20080512 (prerelease) (Debian 4.2.3-6) === gfortran tests === Running target unix XPASS: gfortran.dg/csqrt_2.f -O0 execution test XPASS: gfortran.dg/csqrt_2.f -O1 execution test XPASS: gfortran.dg/csqrt_2.f -O2 execution test XPASS: gfortran.dg/csqrt_2.f -O3 -fomit-frame-pointer execution test XPASS: gfortran.dg/csqrt_2.f -O3 -fomit-frame-pointer -funroll-loops execution test XPASS: gfortran.dg/csqrt_2.f -O3 -fomit-frame-pointer -funroll-all-loops -finline-functions execution test XPASS: gfortran.dg/csqrt_2.f -O3 -g execution test XPASS: gfortran.dg/csqrt_2.f -Os execution test FAIL: gfortran.dg/stat_1.f90 -O0 execution test FAIL: gfortran.dg/stat_1.f90 -O1 execution test FAIL: gfortran.dg/stat_1.f90 -O2 execution test FAIL: gfortran.dg/stat_1.f90 -O3 -fomit-frame-pointer execution test FAIL: gfortran.dg/stat_1.f90 -O3 -fomit-frame-pointer -funroll-loops execution test FAIL: gfortran.dg/stat_1.f90 -O3 -fomit-frame-pointer -funroll-all-loops -finlin
Bug#480203: In the end
In the end it wasn't hardware problem. It was debian mirror problem. I have changed it and reinstalled gcc and libc6-dev, and it started working normally. mirror was deb http://http.us.debian.org/debian/ unstable main now it is deb http://nl.arm.mirror.debian.net/debian unstable main -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
