Re: toolchain/50866: starting firefox crashes the X server

[christos%zoulas.com@localhost (Christos Zoulas)]

The following reply was made to PR toolchain/50866; it has been noted by GNATS.

From: christos%zoulas.com@localhost (Christos Zoulas)
To: Martin Husemann <martin%duskware.de@localhost>
Cc: gnats-bugs%NetBSD.org@localhost, joerg%NetBSD.org@localhost
Subject: Re: toolchain/50866: starting firefox crashes the X server
Date: Wed, 9 Mar 2016 09:02:04 -0500

 On Mar 9, 12:08pm, martin%duskware.de@localhost (Martin Husemann) wrote:
 -- Subject: Re: toolchain/50866: starting firefox crashes the X server
 
 | So the differenc is:
 | 
 | with new binutils, the only thing under usr/X11R7/lib that gets a libgcc_s
 | NEEDED entry is:
 | 
 | 	modules/dri/gallium_dri.so.0
 | 
 | while with old binutils the list is quite lengthy:
 | 
 | 	libFS.so.7.0
 | 	libGLw.so.2.0
 | 	X11/locale/lib/common/ximcp.so.2.0
 | 	X11/locale/lib/common/xlcDef.so.2.0
 | 	X11/locale/lib/common/xlcUTF8Load.so.2.0
 | 	X11/locale/lib/common/xlibi18n.so.2.0
 | 	X11/locale/lib/common/xomGeneric.so.2.0
 | 	libICE.so.7.0
 | 	libSM.so.7.0
 | 	libX11-xcb.so.1.0
 | 	libX11.so.7.0
 | 	libXRes.so.2.0
 | 	libXTrap.so.7.0
 | 	libXau.so.7.0
 | 	libXaw6.so.7.0
 | 	libXaw7.so.10.0
 | 	libXcomposite.so.2.0
 | 	libXcursor.so.2.0
 | 	libXdamage.so.2.0
 | 	libXdmGreet.so.0.0
 | 	libXdmcp.so.7.0
 | 	libXevie.so.2.0
 | 	libXext.so.7.1
 | 	libXfixes.so.4.0
 | 	libXfont.so.3.0
 | 	libXfontcache.so.2.0
 | 	libXft.so.3.0
 | 	libXi.so.7.1
 | 	libXinerama.so.2.0
 | 	libXmu.so.7.0
 | 	libXmuu.so.2.0
 | 	libXpm.so.5.0
 | 	libXpresent.so.1.0
 | 	libXrandr.so.3.2
 | 	libXrender.so.2.0
 | 	libXss.so.2.0
 | 	libXt.so.7.0
 | 	libXtst.so.7.0
 | 	libXv.so.2.0
 | 	libXvMC.so.2.0
 | 	libXvMCW.so.1.0
 | 	libXxf86dga.so.2.0
 | 	libXxf86misc.so.2.0
 | 	libXxf86vm.so.2.0
 | 	libdrm.so.3.3
 | 	libdrm_radeon.so.0.0
 | 	libfontconfig.so.2.2
 | 	libfontenc.so.2.0
 | 	libfreetype.so.18.0.12
 | 	libgbm.so.1.0
 | 	libxcb-glx.so.0.1
 | 	libpciaccess.so.0.3
 | 	libxcb-composite.so.0.1
 | 	libpixman-1.so.2.2
 | 	libxcb-atom.so.1.0
 | 	libxcb-aux.so.0.0
 | 	libxcb-damage.so.0.1
 | 	libxcb-dpms.so.0.1
 | 	libxcb-dri2.so.0.1
 | 	libxcb-dri3.so.0.1
 | 	libxcb-randr.so.1.0
 | 	libxcb-event.so.1.0
 | 	libxcb-icccm.so.1.0
 | 	libxcb-image.so.0.0
 | 	libxcb-keysyms.so.1.0
 | 	libxcb-present.so.0.1
 | 	modules/dri/gallium_dri.so.0
 | 	modules/drivers/ag10e_drv.so.0
 | 	modules/drivers/ati_drv.so.6
 | 	modules/drivers/glint_drv.so.1
 | 	modules/drivers/kbd_drv.so.1
 | 	modules/drivers/mach64_drv.so.6
 | 	modules/drivers/mga_drv.so.1
 | 	modules/drivers/mouse_drv.so.1
 | 	modules/drivers/r128_drv.so.6
 | 	modules/drivers/radeon_drv.so.6
 | 	modules/drivers/suncg6_drv.so.1
 | 	modules/drivers/sunffb_drv.so.1
 | 	modules/drivers/sunleo_drv.so.1
 | 	modules/drivers/ws_drv.so.1
 | 	modules/drivers/wsfb_drv.so.0
 | 	modules/extensions/libdbe.so.0
 | 	modules/extensions/libdri.so.0
 | 	modules/extensions/libdri2.so.0
 | 	modules/extensions/libextmod.so.0
 | 	modules/extensions/libglx.so.0
 | 	modules/extensions/librecord.so.0
 | 	modules/extensions/libshadow.so.0
 | 	modules/libexa.so.0
 | 	modules/libfb.so.0
 | 	modules/libshadowfb.so.0
 | 	modules/libvbe.so.0
 | 	modules/libvgahw.so.0
 | 	modules/libxaa.so.0
 | 	libxcb-property.so.1.0
 | 	libxcb-record.so.0.1
 | 	libxcb-render-util.so.0.0
 | 	libxcb-render.so.0.1
 | 	libxcb-screensaver.so.0.1
 | 	libxcb-reply.so.1.0
 | 	libxcb-res.so.0.1
 | 	libxcb-shape.so.0.1
 | 	libxcb-shm.so.0.1
 | 	libxcb-xfixes.so.0.1
 | 	libxcb-sync.so.1.0
 | 	libxcb-xevie.so.0.1
 | 	libxcb-xf86dri.so.0.1
 | 	libxcb-xinerama.so.0.1
 | 	libxcb-xkb.so.1.0
 | 	libxcb-xtest.so.0.1
 | 	libxcb-xv.so.0.1
 | 	libxkbfile.so.2.0
 | 	libxcb-xvmc.so.0.1
 | 	libxcb.so.2.0
 | 	libxkbui.so.2.0
 | 
 | 
 | This used to cause libgcc_s.so to be loaded quite early in the X server,
 | and be searched earlier when resolving __clzdi2.
 | 
 | Now is this a bug in old or new binutils?
 
 What is different in the way we build gallium?
 
 christos