Re: Fixing the armhf linker path
On 16/12/15 23:30, Aurelien Jarno wrote: > At the beginning of the armhf port the hard-float dynamic linker has > been chosen to be '/lib/arm-linux-gnueabihf/ld-linux.so.3'. However it > has been standardized later as '/lib/ld-linux-armhf.so.3' [1]. We have > changed it in Debian, and added a patch to the glibc [2] to temporarily > support both paths, until all the packages have been rebuilt with the > new path. > > However we failed to do it for Wheezy. We also failed to do it for > Jessie. So let's do it for Stretch, so that we can drop the glibc > patches in Buster, and ensure binary compatibility with other > distributions. > > For that we first need to binNMU the packages which have not been > rebuilt since the dynamic linker change in unstable (see the list at > the end of the mail). Then we can have a look at getting all of them > migrated to testing. > > Any comments or objections? No problem for me, but let's wait for the rebuilds at least until after the Perl transition. Cheers, Emilio
Bug#808181: libc6: Upgrade can make the linker unusable
On 2015-12-16 13:15, Dima Kogan wrote: > Package: libc6 > Severity: normal > > Hi. I had > > libc6= 2.19-22 > binutils = 2.25-4 > > and all was well. Then I upgraded to libc6 = 2.21-4 (currently latest in > sid). As a result, even the most basic build-time linking would fail. > For instance, with a trivial hello-world program: > > $ gcc-5 -o tst tst.c > > /usr/bin/ld: > /usr/lib/gcc/x86_64-linux-gnu/5/../../../x86_64-linux-gnu/crti.o: > unrecognized relocation (0x2a) in section `.init' > /usr/bin/ld: final link failed: Bad value > collect2: error: ld returned 1 exit status > > This would happen with gcc-5 and with gcc-4.9. Downgrading libc6 would > fix it. After some fiddling I realized that upgrading to binutils = > 2.25.90.20151209-1 (currently latest in sid) fixes it. I.e. with the > latest libc6 and the latest binutils packages things work. The problem is not introduced by the glibc, but just by the fact that it has been built with a recent binutils version which adds new relocation types on i386 and amd64. This means that ALL static libraries are affected by this problem. > Can the broken combination be prevented with some Conflicts: tags? > Currently this is a trap for the unwary. I therefore don't think we need to fix that at the glibc level. Either we just ignore the problem saying we don't support partial upgrades or we try to find a global way to fix the dependencies for all libraries. Aurelien -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://www.aurel32.net
Fixing the armhf linker path
At the beginning of the armhf port the hard-float dynamic linker has been chosen to be '/lib/arm-linux-gnueabihf/ld-linux.so.3'. However it has been standardized later as '/lib/ld-linux-armhf.so.3' [1]. We have changed it in Debian, and added a patch to the glibc [2] to temporarily support both paths, until all the packages have been rebuilt with the new path. However we failed to do it for Wheezy. We also failed to do it for Jessie. So let's do it for Stretch, so that we can drop the glibc patches in Buster, and ensure binary compatibility with other distributions. For that we first need to binNMU the packages which have not been rebuilt since the dynamic linker change in unstable (see the list at the end of the mail). Then we can have a look at getting all of them migrated to testing. Any comments or objections? Aurelien [1] https://sourceware.org/ml/libc-ports/2012-04/msg00060.html [2] https://anonscm.debian.org/viewvc/pkg-glibc/glibc-package/trunk/debian/patches/arm/unsubmitted-soname-hack.diff?view=markup&pathrev=5184 4g8_1.0-3 aa3d_1.0-8 abootimg_0.6-1 abr2gbr_1:1.0.2-2 aconnectgui_0.9.0rc2-1-9 acorn-fdisk_3.0.6-8 aegis_4.24.3-3 aes2501-wy_0.1-5 aespipe_2.4c-1 aj-snapshot_0.9.6-1 alleyoop_0.9.8-1 alltray_0.71b-1 alsamixergui_0.9.0rc2-1-9.1 alsoft-conf_1.4.3-1 altermime_0.3.10-7 amideco_0.31e-3.1 and_1.2.2-4.1 apf_0.8.4-1 apg_2.2.3.dfsg.1-2 apparix_07-261-1 apt-spy_3.2.2-1 apwal_0.4.5-1 argus_1:2.0.6.fixes.1-16.3 argus-client_2.0.6.fixes.1-3 aribas_1.64-5 arp-scan_1.8.1-2 arptables_0.0.3.4-1 as31_2.3.1-6 ascd_0.13.2-5 ascii2binary_2.14-1 asmix_1.5-4.1 asmixer_0.5-14 asp_1.8-8 aspic_1.05-4 astronomical-almanac_5.6-4 athena-jot_9.0-5 atlc_4.6.1-1 atp_1.2-11 atsar_1.7-2 attal_1.0~rc2-2 autoclass_3.3.6.dfsg.1-1 autolog_0.40-13.1 automoc_1.0~version-0.9.88-5 aview_1.3.0rc1-9 avinfo_1.0.a15+20090102-1 avr-evtd_1.7.7-2 avrp_1.0beta3-7 awardeco_0.2-3.1 awesfx_0.5.1a-1.1 bam_0.4.0-3 bandwidthcalc_0.2-1 bchunk_1.2.0-12 bfbtester_2.0.1-7.1 bibclean_2.11.4.1-4 bibutils_4.12-5 bidiv_1.5-4 biff_1:0.17.pre2412-5 binfmtc_0.17-1 bing_1.1.3-2 blacs-pvm_1.1-21 bld_0.3.4.1-4 blobandconquer_1.11-dfsg+20-1 bluemon_1.4-6 bootp_2.4.3-18 bootpc_0.64-7 bopm_3.1.3-3 bottlerocket_0.05b3-14.1 bplay_0.991-10 brightside_1.4.0-4.1 btyacc_3.0-5 buildtorrent_0.8-4 bwbar_1.2.3-2 bwbasic_2.20pl2-11 byacc-j_1.15-1 cairo-clock_0.3.4-2 cal_4.0-3 calife_1:3.0.1-4 cbmplugs_1.2.2-1 ccontrol_1.0-1 cd5_0.1-3 cdbackup_0.7.0-5 cdcd_0.6.6-13.1 cdde_0.3.1-1 cdpr_2.4-1 cgiemail_1.6-37 chase_0.5.2-4 choosewm_0.1.6-3 chrootuid_1.3-6 chuck_1.2.0.8.dfsg-1.4 cksfv_1.3.14-2 cldump_0.11~dfsg-1 cliquer_1.21-1 coala_1.0.1-5 codfis_0.4.7-2 comgt_0.32-2 compartment_1.1.0-4 cone_0.89-1 connect-proxy_1.101-1 console-braille_1.3 convlit_1.8-1 cookietool_2.5-5 coolmail_1.3-11 cpipe_3.0.1-1 crack_5.0a-9.3 crack-attack_1.1.14-9.1 c-repl_0.0.20071223-1 cronolog_1.6.2+rpk-1 cstream_3.0.0-1 cuba_3.0+2024-2 cue2toc_0.4-5 cutechess_2014+0.4.2+0.0.1-1 cutecom_0.22.0-2 cvstrac_2.0.1-3 cycfx2prog_0.47-1 cyclades-serial-client_0.92 cyrus-imspd_1.8-3 d52_3.4.1-1.1 daa2iso_0.1.7e-1 dact_0.8.42-4 daemon_0.6.4-1 daemonfs_1.1-1 dancer-xml_0.8.2.1-3 darksnow_0.6.1-3 dbar_0.0.20100524-3 dbench_4.0-2 dbview_1.0.4-1 dealer_0.20040530-4 desklaunch_1.1.8 deskmenu_1.4.5 desktopnova_0.8.1-1 desproxy_0.1.0~pre3-8 devio_1.2-1 dhcpdump_1.8-2 dhis-client_5.5-4 dhis-dns-engine_5.3-1 dhis-server_5.3-2.1 dhis-tools-dns_5.0-6.1 dia2code_0.8.3-4 dis51_0.5-1.1 djbdns_1:1.05-8 dmitry_1.3a-1 dnsproxy_1.16-0.1 dnstracer_1.9-4 doschk_1.1-6 dossizola_1.0-8.3 dot-forward_1:0.71-2 dsbltesters_0.9.5-4 dssi_1.1.1~dfsg0-1 dtaus_0.9-1 dv4l_1.0-5 dvbstream_0.6+cvs20090621-1 dvdisaster_0.72.4-1 dvhtool_1.0.1-5 dvidvi_1.0-8etch2 dynamite_0.1.1-2 e00compr_1.0.1-2 e2tools_0.0.16-6.1 easyh10_1.5-1 efax_1:0.9a-19 empire-hub_1.0.2.1 enum_1.1-1 epwutil_1.1-8.1 eqonomize_0.6-7 esekeyd_1.2.7-1 etherpuppet_0.3-2 evolver_2.30c.dfsg-3 exonerate_2.2.0-6 ezmlm-browse_0.10-3 ezstream_0.5.6~dfsg-1 f2c_20100827-1 fair_0.5.3-1 fake_1.1.11-1 fakepop_11 falselogin_0.3-4 fapg_0.41-1 fastdnaml_1.2.2-10 fastforward_1:0.51-3 fastlink_4.1P-fix95-3 file-kanji_1.1-16 fileschanged_0.6.5-1.2 filter_2.6.3-1 filtergen_0.12.4-5.1 fische_3.2.2-3 flake_0.11-2 flexloader_0.03-2 flex-old_2.5.4a-10 floatbg_1.0-28 flog_1.8-3 fluidsynth-dssi_1.0.0-6 flvstreamer_2.1c1-1 fprint-demo_20080303git-5 francine_0.99.8orig-6 freecdb_0.75 fso-gpsd_0.8-3.1 fso-gsm0710muxd_0.9.3.1-3 fspanel_0.7-13 fspy_0.1.1-1 fteqcc_3343+svn3400-3 ftjam_2.5.2-1.1 ftpcopy_0.6.7-3 ftplib_3.1-1-9 fusedav_0.2-3.1 fuse-posixovl_1.2.20120215+gitf5bfe35-1 fuzz_0.6-14 fxload_0.0.20081013-1 g15composer_3.2-2 g15macro_1.0.3-3 gadmin-bind_0.2.5-2 gadmin-openvpn-client_0.1.2-4 gadmin-openvpn-server_0.1.5-3.1 gadmin-proftpd_1:0.4.2-1 gadmin-rsync_0.1.7-1 gadmin-samba_0.2.9-3 garlic_1.6-1.1 gbase_0.5-2.2 gbatnav_1.0.4cvs20051004-5 gcc-m68hc1x_1:3.3.6+3.1+dfsg-3 gcolor2_0.4-2.1 gcx_1.3-1.1 gemanx-gtk2_0.1.0.3-2 gems_1.1.1-2 genext2fs_1.4.1-4 genromfs_0.5.2-2 gerbv_2.6
Bug#808180: libc6: does not start qtcreator v3.5 and v3.6 "Segmentation fault."
Hello, lukash, on Wed 16 Dec 2015 23:49:47 +0300, wrote: > (gdb) run > Starting program: ~/Qt5.5.1/Tools/QtCreator/bin/qtcreator > [Thread debugging using libthread_db enabled] > Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". > [New Thread 0x7fffec5cb700 (LWP 1282)] > [New Thread 0x7fffd831b700 (LWP 1285)] > > Program received signal SIGSEGV, Segmentation fault. > 0x77de72c6 in ?? () from /lib64/ld-linux-x86-64.so.2 Could you install libc6-dbg so we get much better feedback from gdb? Thanks, Samuel
Bug#808181: libc6: Upgrade can make the linker unusable
Package: libc6 Severity: normal Hi. I had libc6= 2.19-22 binutils = 2.25-4 and all was well. Then I upgraded to libc6 = 2.21-4 (currently latest in sid). As a result, even the most basic build-time linking would fail. For instance, with a trivial hello-world program: $ gcc-5 -o tst tst.c /usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/5/../../../x86_64-linux-gnu/crti.o: unrecognized relocation (0x2a) in section `.init' /usr/bin/ld: final link failed: Bad value collect2: error: ld returned 1 exit status This would happen with gcc-5 and with gcc-4.9. Downgrading libc6 would fix it. After some fiddling I realized that upgrading to binutils = 2.25.90.20151209-1 (currently latest in sid) fixes it. I.e. with the latest libc6 and the latest binutils packages things work. Can the broken combination be prevented with some Conflicts: tags? Currently this is a trap for the unwary.
Bug#808180: libc6: does not start qtcreator v3.5 and v3.6 "Segmentation fault."
Package: libc6 Version: 2.19-22 Severity: normal Tags: upstream Dear Maintainer, run with gdb: $ gdb qtcreator (gdb) run Starting program: ~/Qt5.5.1/Tools/QtCreator/bin/qtcreator [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [New Thread 0x7fffec5cb700 (LWP 1282)] [New Thread 0x7fffd831b700 (LWP 1285)] Program received signal SIGSEGV, Segmentation fault. 0x77de72c6 in ?? () from /lib64/ld-linux-x86-64.so.2 -- System Information: Debian Release: stretch/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.2.0-1-amd64 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages libc6 depends on: ii libgcc1 1:5.2.1-23 libc6 recommends no packages. Versions of packages libc6 suggests: ii debconf [debconf-2.0] 1.5.58 pn glibc-doc ii locales2.19-22 -- debconf information excluded
Displays with a smile
This e-mail contains graphics, if you don't see them » view it online. ( http://www.expofun.be/index.php?option=com_acymailing&ctrl=archive&task=view&mailid=29&key=sPV0Y8X3&subid=88859-PN9zyFi7GIjcPA&tmpl=component ) Nieuwsbrief ExpoFun 16 december 2015 Beste Rossignol M-R, Op zoek naar displays om te exposeren ? Ontdek ze in onze onlineshop ook outlet + 2e handsmateriaal ( http://www.expofun.be ) www.expofun.be ( http://www.expofun.be ) | Contact ( mailto:i...@expofun.be ) If you're not interested any more » unsubscribe ( http://www.expofun.be/index.php?subid=88859&option=com_acymailing&ctrl=user&task=out&mailid=29&key=PN9zyFi7GIjcPA )
Bug#808143: bg_BG locale should use colon as time separator, not comma
On 2015-12-16 12:43, Damyan Ivanov wrote: > Package: locales > Version: 2.21-4 > Severity: normal > Tags: upstream patch > > The time format specified in the bg_BG locale is: > > $ locale -k t_fmt t_fmt_ampm date_fmt > t_fmt="%k,%M,%S" > t_fmt_ampm="%l,%M,%S" > date_fmt="%a %b %e %H:%M:%S %Z %Y" > > t_fmt[_ampm] should use colons instead of commas, like date_fmt already does. Do you have a source saying the format you suggest is the correct one? Is it something that has changed recently? The format you suggest was the one in use prior to commit fa13c459, so I would like to understand why it has been changed at that time. Ideally it would be nice if you can send the patch upstream, so that you can give the arguments for the change directly there, instead of having us to proxy them. Aurelien -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://www.aurel32.net
Bug#808143: bg_BG locale should use colon as time separator, not comma
Package: locales Version: 2.21-4 Severity: normal Tags: upstream patch The time format specified in the bg_BG locale is: $ locale -k t_fmt t_fmt_ampm date_fmt t_fmt="%k,%M,%S" t_fmt_ampm="%l,%M,%S" date_fmt="%a %b %e %H:%M:%S %Z %Y" t_fmt[_ampm] should use colons instead of commas, like date_fmt already does. An example of the badly formatted time can be seen in empathy chat windows when using 'Boxes' or 'Planet GNOME' themes. Trivial patch attached. -- dam -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'oldstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.3.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=bg_BG.UTF-8, LC_CTYPE=bg_BG.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages locales depends on: ii debconf [debconf-2.0] 1.5.58 ii libc-bin 2.21-4 ii libc-l10n 2.21-4 locales recommends no packages. locales suggests no packages. -- debconf information: * locales/default_environment_locale: bg_BG.UTF-8 * locales/locales_to_be_generated: bg_BG.UTF-8 UTF-8 >From bf384da5916495f08207f61d48a3e7bb4bfea36e Mon Sep 17 00:00:00 2001 From: Damyan Ivanov Date: Wed, 16 Dec 2015 12:40:21 + Subject: [PATCH] Fix time separator in bg_BG locale Use colons instead of commas --- localedata/locales/bg_BG | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/localedata/locales/bg_BG b/localedata/locales/bg_BG index 74e5ad4..ed12e25 100644 --- a/localedata/locales/bg_BG +++ b/localedata/locales/bg_BG @@ -185,9 +185,9 @@ LC_TIME d_t_fmt"/ " d_fmt "" -t_fmt "" +t_fmt "" am_pm "";"" -t_fmt_ampm "" +t_fmt_ampm "" date_fmt "/ / " -- 2.6.4
