Bug#767323: LTO not working: File format not recognized
TL;DR The problem appears to be related to binutils and not clang. I am having the same problem as the submitter with Clang 3.5.0-9. Compiling the following simple hello world program: #include iostream int main() { std::cout Hello World\n; return 0; } $ clang++ -flto -c hello.cpp $ clang++ -v -flto hello.o -o hello Debian clang version 3.5.0-9 (tags/RELEASE_350/final) (based on LLVM 3.5.0) Target: x86_64-pc-linux-gnu Thread model: posix Found candidate GCC installation: /usr/bin/../lib/gcc/i586-linux-gnu/4.8 Found candidate GCC installation: /usr/bin/../lib/gcc/i586-linux-gnu/4.8.4 Found candidate GCC installation: /usr/bin/../lib/gcc/i586-linux-gnu/4.9 Found candidate GCC installation: /usr/bin/../lib/gcc/i586-linux-gnu/4.9.2 Found candidate GCC installation: /usr/bin/../lib/gcc/x86_64-linux-gnu/4.7 Found candidate GCC installation: /usr/bin/../lib/gcc/x86_64-linux-gnu/4.7.4 Found candidate GCC installation: /usr/bin/../lib/gcc/x86_64-linux-gnu/4.8 Found candidate GCC installation: /usr/bin/../lib/gcc/x86_64-linux-gnu/4.8.4 Found candidate GCC installation: /usr/bin/../lib/gcc/x86_64-linux-gnu/4.9 Found candidate GCC installation: /usr/bin/../lib/gcc/x86_64-linux-gnu/4.9.2 Found candidate GCC installation: /usr/lib/gcc/i586-linux-gnu/4.8 Found candidate GCC installation: /usr/lib/gcc/i586-linux-gnu/4.8.4 Found candidate GCC installation: /usr/lib/gcc/i586-linux-gnu/4.9 Found candidate GCC installation: /usr/lib/gcc/i586-linux-gnu/4.9.2 Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/4.7 Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/4.7.4 Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/4.8 Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/4.8.4 Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/4.9 Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/4.9.2 Selected GCC installation: /usr/bin/../lib/gcc/x86_64-linux-gnu/4.9 Candidate multilib: .;@m64 Selected multilib: .;@m64 /usr/bin/ld --hash-style=both --build-id --eh-frame-hdr -m elf_x86_64 -dynamic-linker /lib64/ld-linux-x86-64.so.2 -o hello /usr/bin/../lib/gcc/x86_64-linux-gnu/4.9/../../../x86_64-linux-gnu/crt1.o /usr/bin/../lib/gcc/x86_64-linux-gnu/4.9/../../../x86_64-linux-gnu/crti.o /usr/bin/../lib/gcc/x86_64-linux-gnu/4.9/crtbegin.o -L/usr/bin/../lib/gcc/x86_64-linux-gnu/4.9 -L/usr/bin/../lib/gcc/x86_64-linux-gnu/4.9/../../../x86_64-linux-gnu -L/lib/x86_64-linux-gnu -L/lib/../lib64 -L/usr/lib/x86_64-linux-gnu -L/usr/bin/../lib/gcc/x86_64-linux-gnu/4.9/../../.. -L/usr/lib/llvm-3.5/bin/../lib -L/lib -L/usr/lib -plugin /usr/lib/llvm-3.5/bin/../lib/LLVMgold.so -plugin-opt=mcpu=x86-64 hello.o -lstdc++ -lm -lgcc_s -lgcc -lc -lgcc_s -lgcc /usr/bin/../lib/gcc/x86_64-linux-gnu/4.9/crtend.o /usr/bin/../lib/gcc/x86_64-linux-gnu/4.9/../../../x86_64-linux-gnu/crtn.o hello.o: file not recognized: File format not recognized clang: error: linker command failed with exit code 1 (use -v to see invocation) It appears that the default linker is not the gold linker. $ ls -l /usr/bin/ld* lrwxrwxrwx 1 root root 6 Dec 25 16:33 /usr/bin/ld - ld.bfd -rwxr-xr-x 1 root root 1076192 Dec 19 13:30 /usr/bin/ld.bfd -rwxr-xr-x 1 root root5388 Nov 6 15:12 /usr/bin/ldd -rwxr-xr-x 1 root root 2642264 Dec 19 13:30 /usr/bin/ld.gold The following workaround fixed the problem for me. $ sudo rm /usr/bin/ld $ sudo ln -s ld.gold /usr/bin/ld $ clang++ -flto hello.o -o hello $ ./hello Hello World Perhaps this bug should be reassigned to binutils. $ dpkg -S /usr/bin/ld binutils: /usr/bin/ld $ dpkg -S /usr/bin/ld.gold binutils: /usr/bin/ld.gold -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#726368: (no subject)
Could you please post the contents of ~/.xsession-errors? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#667706: openssl 1.0.1 breaks wpa_supplicant
No luck on the openssl front, but a patch to wpa_supplicant that disables TLS session tickets does the trick for me. See http://w1.fi/bugz/show_bug.cgi?id=447 I've attached a debdiff against wpa. diff -Nru wpa-1.0/debian/changelog wpa-1.0/debian/changelog --- wpa-1.0/debian/changelog 2012-05-13 16:39:47.0 -0400 +++ wpa-1.0/debian/changelog 2012-07-23 13:34:13.0 -0400 @@ -1,3 +1,12 @@ +wpa (1.0-2.1) UNRELEASED; urgency=low + + * Non-maintainer upload. + * Disable TLS session tickets. Ever since the release of openssl-1.0.1, +session tickets have (apparently) prevented WPA2 enterprise authentication +against some (probably broken) access points. (Bug #667706) + + -- Benjamin Kay benja...@benkay.net Mon, 23 Jul 2012 13:33:49 -0400 + wpa (1.0-2) unstable; urgency=low * Really enable hardened build flags, thanks Simon Ruderich diff -Nru wpa-1.0/debian/patches/disable_session_tickets.patch wpa-1.0/debian/patches/disable_session_tickets.patch --- wpa-1.0/debian/patches/disable_session_tickets.patch 1969-12-31 19:00:00.0 -0500 +++ wpa-1.0/debian/patches/disable_session_tickets.patch 2012-07-23 13:33:32.0 -0400 @@ -0,0 +1,14 @@ +Disables TLS session tickets, thereby avoiding enterprise authentication +failures against some (probably broken) access points that had arisen since +the release of openssl-1.0.1. +See http://w1.fi/bugz/attachment.cgi?id=235action=diff +--- a/src/crypto/tls_openssl.c b/src/crypto/tls_openssl.c +@@ -926,6 +926,7 @@ + #ifdef SSL_OP_NO_COMPRESSION + options |= SSL_OP_NO_COMPRESSION; + #endif /* SSL_OP_NO_COMPRESSION */ ++ options |= SSL_OP_NO_TICKET; + SSL_set_options(conn-ssl, options); + + conn-ssl_in = BIO_new(BIO_s_mem()); diff -Nru wpa-1.0/debian/patches/series wpa-1.0/debian/patches/series --- wpa-1.0/debian/patches/series 2012-04-17 07:03:56.0 -0400 +++ wpa-1.0/debian/patches/series 2012-07-23 13:33:32.0 -0400 @@ -6,3 +6,4 @@ 12_wpa_gui_knotify_support.patch 13_human_readable_signal.patch libnl3-includes.patch +disable_session_tickets.patch
Bug#675205: openssh-client: openssh 1:6.0 should depend on libssl1.0.0 = 1.0.1
Package: openssh-client Version: 1:6.0p1-1 Severity: normal Dear Maintainer, openssh-client depends on libssl1.0.0 = 1.0.0, but is should depend on libssl1.0.0 = 1.0.1. With libssl1.0.0_1.0.0h-1 installed, attempts to login to a remote server using public key authentication produce the following error: OpenSSL version mismatch. Built against 1000103f, you have 108f Downgrading to openssh-client_5.9p1-5 serves as a workaround. I'm assuming that upgrading libssl1.0.0 (which I can't do due to an unrelated bug in that package) would also make the error go away. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages openssh-client depends on: ii adduser3.113+nmu2 ii debconf [debconf-2.0] 1.5.43 ii dpkg 1.16.3 ii libc6 2.13-32 ii libedit2 2.11-20080614-3 ii libgssapi-krb5-2 1.10.1+dfsg-1 ii libselinux12.1.9-4 ii libssl1.0.0none ii passwd 1:4.1.5.1-1 ii zlib1g 1:1.2.7.dfsg-11 Versions of packages openssh-client recommends: ii openssh-blacklist0.4.1 ii openssh-blacklist-extra 0.4.1 ii xauth1:1.0.7-1 Versions of packages openssh-client suggests: pn keychain none pn libpam-sshnone pn monkeysphere none pn ssh-askpass none -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#667706: openssl 1.0.1 breaks wpa_supplicant
On Monday, April 30, 2012 20:15:26 Raghav Krishnapriyan wrote: On Sun, Apr 29, 2012, at 07:26:11 pm +0200, Kurt Roeckx wrote: Can you please try with the 1.0.1b version? 1.0.1b still results in the same problem, unfortunately. FYI, 1.0.1c (the most current version at the time of this writing) also still results in the same problem. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#628822: gtk-redshift should depend on python-gtk2 but doesn't
Package: gtk-redshift Version: 1.6-1 Severity: important gtk-redshift does not start on my system. Running gtk-redshift from the commandline produces the following output: Traceback (most recent call last): File /usr/bin/gtk-redshift, line 22, in module from gtk_redshift.statusicon import run File /usr/lib/pymodules/python2.6/gtk_redshift/statusicon.py, line 33, in module import gtk, glib ImportError: No module named gtk Installing the package python-gtk 2.24.0-2 resolves this problem and allows gtk-redshift to start and function normally. (Earlier versions of python-gtk2 would probably work equally well.) Since python-gtk2 is necessary for gtk-redshift to work, gtk-redshift should probably depend on the python-gtk2 package. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.39-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages gtk-redshift depends on: ii python2.6.6-14 interactive high-level object- orie ii python-support1.0.13 automated rebuilding support for P ii python-xdg0.19-3 Python library to access freedeskt ii redshift 1.6-1 Adjusts the color temperature of y gtk-redshift recommends no packages. gtk-redshift suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org