From owner-freebsd-toolchain@freebsd.org Sun Mar 25 23:19:30 2018 Return-Path: Delivered-To: freebsd-toolchain@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C8C07F51259 for ; Sun, 25 Mar 2018 23:19:30 +0000 (UTC) (envelope-from marklmi26-fbsd@yahoo.com) Received: from sonic310-15.consmr.mail.bf2.yahoo.com (sonic310-15.consmr.mail.bf2.yahoo.com [74.6.135.125]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 685B67EBA9 for ; Sun, 25 Mar 2018 23:19:30 +0000 (UTC) (envelope-from marklmi26-fbsd@yahoo.com) X-YMail-OSG: 42AyFwwVM1n5mxJ7cSRhFcv67GnI0L.cr2jA0zbd6C2jaWxYB7GZHy3yt3ks0dN GR7MLeJf5GKFxPDqoERyCC1YHFjkraZdMCgyabhFH1gzUYrsbdnk5Bjo.nh.GNyHog9Q2Xj9c2q_ 2hQH3pVCEsJDAGb_4FdZlI4_lP72xjSZDXKNm2d.58ELyQC_vgfTFQD3HmRt00b7hAprlNd.ZlLa 0y5vYVc4UDrByTpK2jpZFpjsoqRGqBDt3sdfEJFW.w8svYPFaLwu6ceM.OsJX.iSc4csKZt5kUan Uu2Qx9pLGrrAyY7.EUyQwuAssvG83FGLVDGWuFSp3EzTy8M4jPpcEfdNtF15t.1BZ53PjDkvLTzo thPVdnDAaQ86vmpNft_zFPzDk1Vn6.oOTV9G53.h.RbpzWaYubGrXxrTnRZ6cBcHBpiKirlBVLb4 Ie.vHCGvT.XPWyNblmRIiCyRwcowMWPdL.M.t8oE9ifsGpPmB8Ud2NBl.RWFrMs6eBYJeTfwK6Vn dMXcUPDfKXljtZKo578IEQqXbrCJSLndYYB5B Received: from sonic.gate.mail.ne1.yahoo.com by sonic310.consmr.mail.bf2.yahoo.com with HTTP; Sun, 25 Mar 2018 23:19:22 +0000 Received: from c-76-115-7-162.hsd1.or.comcast.net (EHLO [192.168.1.25]) ([76.115.7.162]) by smtp420.mail.bf1.yahoo.com (Oath Hermes SMTP Server) with ESMTPA ID fb5803c1b483f2c7f72354c01f96aa91; Sun, 25 Mar 2018 23:19:20 +0000 (UTC) From: Mark Millard Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\)) Subject: aarch64-none-elf-gcc V6.3.0_2 from -r465491 fails to package because of 3 referenced-but-missing include-fixed files (amd64 context) Message-Id: <0C5C8C85-7569-4B64-895E-ABA0C4FAA3B3@yahoo.com> Date: Sun, 25 Mar 2018 16:19:18 -0700 To: freebsd-ports@freebsd.org, "freebsd-toolchain@FreeBSD.org" , freebsd-arm@FreeBSD.org X-Mailer: Apple Mail (2.3445.5.20) X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Mar 2018 23:19:31 -0000 # svnlite info /usr/ports/ | grep "^Re[plv]" Relative URL: ^/head Repository Root: svn://svn.freebsd.org/ports Repository UUID: 35697150-7ecd-e111-bb59-0022644237b5 Revision: 465491 via a poudrirere-devel bulk -a run: =3D=3D=3D> Building package for aarch64-none-elf-gcc-6.3.0_2 pkg-static: Unable to access file = /wrkdirs/usr/ports/devel/aarch64-none-elf-gcc/work/stage/usr/local/lib/gcc= /aarch64-none-elf/6.3.0/include-fixed/README:No such file or directory pkg-static: Unable to access file = /wrkdirs/usr/ports/devel/aarch64-none-elf-gcc/work/stage/usr/local/lib/gcc= /aarch64-none-elf/6.3.0/include-fixed/limits.h:No such file or directory pkg-static: Unable to access file = /wrkdirs/usr/ports/devel/aarch64-none-elf-gcc/work/stage/usr/local/lib/gcc= /aarch64-none-elf/6.3.0/include-fixed/syslimits.h:No such file or = directory *** Error code 1 Context: # uname -apKU FreeBSD FBSDHUGE 12.0-CURRENT FreeBSD 12.0-CURRENT r331499M amd64 = amd64 1200060 1200060 =3D=3D=3D Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) From owner-freebsd-toolchain@freebsd.org Tue Mar 27 02:15:01 2018 Return-Path: Delivered-To: freebsd-toolchain@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id F3235F645B8; Tue, 27 Mar 2018 02:15:00 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: from mail-it0-x231.google.com (mail-it0-x231.google.com [IPv6:2607:f8b0:4001:c0b::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 90DDC84F39; Tue, 27 Mar 2018 02:15:00 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: by mail-it0-x231.google.com with SMTP id h143-v6so5498929ita.4; Mon, 26 Mar 2018 19:15:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:from:date:message-id:subject:to; bh=vERJlQCInH5avX7G0mt4XuzWHKG2QRQA8VXjgP0l5L8=; b=l/xvyjVgtyZDv6pI6/6Diz3TutpPv7wKoTc0oSN8Oovu2oxOsQz9LureuP2tGiC7la AfsJwy2vgaEnFzNiFHMcnGq4xvtynScYVEVQUKUnVj9tQI0QRtR9a7rqVNNXEvgkqmk/ fUf3+Bw9bxAGOB7M7J5p1V8D8MDjYrLoaWsfciAlU5Ro6wu94erHT7v7LsLeKl2UnXaK jwz8rr3hwC25+SmWHVy1/5X0jIQOKCKbW8hAx35Of3RFMVlr8O+ri+nd2AfT4MQwYpEz vY/4IWgf6a9tMGLM+rWYLy0/Iq+ZjqjCOJt4Yhx7t5xzLQVEHQ+C4DQ5jrkCcH1B5CA1 Nihw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:from:date:message-id:subject :to; bh=vERJlQCInH5avX7G0mt4XuzWHKG2QRQA8VXjgP0l5L8=; b=lf+83CSL/wO9pXIMic1LccdWu/XFS9M2GkBd44nnhS76LdPmEUXXpdePLqIYd4xC9z 3VzwqlEUWCBxSHMILV9ZxUGEP07dRz5P7AOYm/b64EU7r16lWBB03GYH6BTcgWrpV7wE K4V8mbqDcI3V2hapv0TITiWM8vNvJq9P81b4zWNA0CzCZHRMSQYAlBkAzZbGmdGRCURE d7W31po/8egzcYr0QqEP35W84fXxiyj8LBf6zUOfF7iNo5B5RrVP6GuzEAthyUQSCBB+ 3WPnBPbFP5Nv2OJ9X8omZqNKHEM5A/j3U7nUzpxTQTA+Ps8Sg4fIzu0ZaYZVVbXvrYAt obvQ== X-Gm-Message-State: AElRT7EfIXG8+ZCdEZpIhaA0SL0kQ3l3iCWJFcRB4DPt/qB8K0zLY9q9 fDn+0wHO8YQul5aWvsaGgjKhi7Fx1swYbqDm6w4F113Q X-Google-Smtp-Source: AIpwx4/mZ4zDrob1gSNupGbUEOb0/iJUVxeUFcHBWXGoQRvQBZK8XfsmWRbJlZw6AI2yZD1CV3udUOcd60OBOyKLDNU= X-Received: by 2002:a24:dfc3:: with SMTP id r186-v6mr137905itg.114.1522116899786; Mon, 26 Mar 2018 19:14:59 -0700 (PDT) MIME-Version: 1.0 Sender: carpeddiem@gmail.com Received: by 10.107.20.200 with HTTP; Mon, 26 Mar 2018 19:14:33 -0700 (PDT) From: Ed Maste Date: Mon, 26 Mar 2018 22:14:33 -0400 X-Google-Sender-Auth: 30nkv9Im5Z22rzvi_0aqPBa-HJQ Message-ID: Subject: Heads-up: linker (lld) changes for amd64 coming soon To: FreeBSD Current , "freebsd-toolchain@FreeBSD.org" Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Mar 2018 02:15:01 -0000 Some changes related to the amd64 linker are nearly ready to be committed (within a week or three), so I'm sending this notice to request any final comments or concerns before these changes are made. 1. Kostik (kib@) has a patch to start using kernel ifunc, with the first use being Supervisor Mode Access Prevention (SMAP) on amd64. This relies on linker support that is available in the in-tree lld and in contemporary binutils ld.bfd from ports, but not in the in-tree ld.bfd 2.17.50. Right now we use lld as the default bootstrap linker for amd64 in -CURRENT -- that is, the kernel, and userland libraries and binaries are linked with lld. To revert to ld.bfd for amd64 the build-time knob WITHOUT_LLD_BOOTSTRAP=yes can currently be added to src.conf. When the ifunc changes get committed WITHOUT_LLD_BOOTSTRAP=yes will not work for amd64 kernels (and will be added to BROKEN_OPTIONS). 2. WITH_LLD_IS_LD controls whether /usr/bin/ld is ld.bfd or ld.lld, and thus the linker used for linking ports. I plan to switch this to default on. Most ports build just fine when lld is the system linker, but a few encounter trouble: some of the ports rely on options not supported by lld, rely on specific quirks of ld.bfd's implementation, or have a buggy linker invocation that is silently ignored by ld.bfd. The majority of such ports have now been adapted to work with lld or configured to use ld.bfd as the linker, but there are a small number of failing ports that do not provide a way to use other than the default system linker /usr/bin/ld. The outstanding issues can be found in the ports exp-run for lld as /usr/bin/ld, PR214864. Please follow up if you have any concerns or comments about these upcoming changes. From owner-freebsd-toolchain@freebsd.org Tue Mar 27 06:20:26 2018 Return-Path: Delivered-To: freebsd-toolchain@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 63544F52718; Tue, 27 Mar 2018 06:20:26 +0000 (UTC) (envelope-from antoine.brodin.freebsd@gmail.com) Received: from mail-io0-x229.google.com (mail-io0-x229.google.com [IPv6:2607:f8b0:4001:c06::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E4FF47011A; Tue, 27 Mar 2018 06:20:25 +0000 (UTC) (envelope-from antoine.brodin.freebsd@gmail.com) Received: by mail-io0-x229.google.com with SMTP id e79so26128554ioi.7; Mon, 26 Mar 2018 23:20:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=nb7Jy7OgVHCe4frKAsG25iTI51e2alPw0lIjwtXa/jk=; b=tvoqwCmXcUmoHWM5y7ayCoCkrvbQWeB8X356po9GbTN7BXEStO2elfV1Ob+50xzmTy bzXQHDkVL43Y1xK4xs0E7saPrFQVDwdIGiT5c+ZFplEgPA2VezJ4glftBP6sHHxrL1M8 8WI3oq8bYXdpcxx6Uq2Medolcd/h2cKlBE+VcA4Tx+WM9IlwAyHPwjQcmzVZhaDAgl8Y 8CyGBXNj4FfpK9XGKgjXohWfWGnplaWQe3kTacJMUOUXs0A1PYam9yVEUw7jLnMQN1A1 vfMgM1TN2ctLp/4SxuPwT5nn0SoOViwXFEM8hFT9i2eBknf0nbpw2yWNhMFZOOknGn0U baog== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=nb7Jy7OgVHCe4frKAsG25iTI51e2alPw0lIjwtXa/jk=; b=Y+H8o0vsjoSaBGzEZTBEV52oU2dik5CWTK4fqG9GYTDdzq36PBzRJELi4Fd3O+7r0N wSWYchTRTJzRJwihI+0apizVsuaAAvy9U3miP67mWUphqEAxURfUyOEq9oV4YQln+SC+ Z/liBGbCvK6q1b6t/SDiw3kJ25kV5nbqMFxPg6rtGPgp6QSb4hYOeqqTnFzxkcWc9Hoc 1JihfWGedz9WePF/Xu9v127JFNObh9BMp+HHdwc5hA1C5I7HJ5QTjybgCbKcZ1IuLdg1 TjIf+YuF5K63Ao5bBEll2OOg8q2otil8vezRtY/wCQSdWy3XQsgEXUARzX3FZw/d/gqj eQ+A== X-Gm-Message-State: AElRT7EKSpV25rSWeiNKfqBubfuh5Q+NFM/wjnoUGFRw1JcmDdPBnIiR Yh+uEjfiUnvLnXUEXRcXzS5e4FdoRYnsdnjDnMs= X-Google-Smtp-Source: AG47ELtCh6zZpL9YsPRhAdd3ahVB97M7xvU3uGlPI9yuWneQINPvhp9trN+2erWZihzL73vFYfaKA8FwhHJTRLkDPfQ= X-Received: by 10.107.59.8 with SMTP id i8mr42476822ioa.110.1522131625220; Mon, 26 Mar 2018 23:20:25 -0700 (PDT) MIME-Version: 1.0 Sender: antoine.brodin.freebsd@gmail.com Received: by 10.107.184.135 with HTTP; Mon, 26 Mar 2018 23:20:24 -0700 (PDT) In-Reply-To: References: From: Antoine Brodin Date: Tue, 27 Mar 2018 08:20:24 +0200 X-Google-Sender-Auth: GeK0p40amV14kuHzEkoJhRy3g18 Message-ID: Subject: Re: Heads-up: linker (lld) changes for amd64 coming soon To: Ed Maste Cc: FreeBSD Current , "freebsd-toolchain@FreeBSD.org" Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Mar 2018 06:20:26 -0000 On Tue, Mar 27, 2018 at 4:14 AM, Ed Maste wrote: > Some changes related to the amd64 linker are nearly ready to be > committed (within a week or three), so I'm sending this notice to > request any final comments or concerns before these changes are made. > > 1. Kostik (kib@) has a patch to start using kernel ifunc, with the > first use being Supervisor Mode Access Prevention (SMAP) on amd64. > This relies on linker support that is available in the in-tree lld and > in contemporary binutils ld.bfd from ports, but not in the in-tree > ld.bfd 2.17.50. > > Right now we use lld as the default bootstrap linker for amd64 in > -CURRENT -- that is, the kernel, and userland libraries and binaries > are linked with lld. To revert to ld.bfd for amd64 the build-time knob > WITHOUT_LLD_BOOTSTRAP=yes can currently be added to src.conf. When the > ifunc changes get committed WITHOUT_LLD_BOOTSTRAP=yes will not work > for amd64 kernels (and will be added to BROKEN_OPTIONS). > > 2. WITH_LLD_IS_LD controls whether /usr/bin/ld is ld.bfd or ld.lld, > and thus the linker used for linking ports. I plan to switch this to > default on. > > Most ports build just fine when lld is the system linker, but a few > encounter trouble: some of the ports rely on options not supported by > lld, rely on specific quirks of ld.bfd's implementation, or have a > buggy linker invocation that is silently ignored by ld.bfd. > > The majority of such ports have now been adapted to work with lld or > configured to use ld.bfd as the linker, but there are a small number > of failing ports that do not provide a way to use other than the > default system linker /usr/bin/ld. The outstanding issues can be found > in the ports exp-run for lld as /usr/bin/ld, PR214864. > > Please follow up if you have any concerns or comments about these > upcoming changes. Hi, I have no concerns about 1. About 2., I am concerned that changes breaking a large number of ports are committed without portmgr@ approval. If WITH_LLD_IS_LD is committed as is on amd64, packages for head won't be published as it doesn't meet our current criteria for publication. Antoine From owner-freebsd-toolchain@freebsd.org Tue Mar 27 17:15:27 2018 Return-Path: Delivered-To: freebsd-toolchain@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4F8CBF6C5AF; Tue, 27 Mar 2018 17:15:27 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: from mail-io0-x231.google.com (mail-io0-x231.google.com [IPv6:2607:f8b0:4001:c06::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D35DA72D7B; Tue, 27 Mar 2018 17:15:26 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: by mail-io0-x231.google.com with SMTP id v13so158338iob.6; Tue, 27 Mar 2018 10:15:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=KTkmPFAan1r46/P9C+Y7T9LIgNNnZREVZJ8KGHARyz8=; b=C59DSrs0QQd/czQ1PBlIi1Z8EJce/ggSFuMKBKPK+sJ0jVmAGQSnaD3sEOU5fS5KWz Ka7lfjbulyqQSJujaokHnSGD+w74mcQAjnseZGFbMUsa4+lXndfCZpYs3CsDf9pxRuOG HT9IwFyIOR6+mav896PSBGCVa7YjV6pMlV8ttJuKDWeP2NEmBj0vB8jdDnj3+ssq0Prx kUcjLzrUoRuIN/+63JrkzxEqkqm28UfGsFj6kfnEfwxZIUJPh1Ui1cHM2g3uxG2HofBV I5ABS3zC/7cEoOWGDZLpKxpRbZddR8iaT868tbCP9KVMiriN7YvF/ER2sVnXSmUADwpD S0VQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=KTkmPFAan1r46/P9C+Y7T9LIgNNnZREVZJ8KGHARyz8=; b=dVTzTlwRRfVRwXUaWuLQ+PttwhqKgSweZ+DJFNj39PPT5M67br456U9lGuRBbkDwlT eKtsOBegXEPdzYDaOfTMJCrvfeHZvaEYFBc6mFGUq+jWIa/inqImTyBQf/MsYAvr6mkh otz9DyARG8lgHa8qBrpyzozLovhkuXIGBUBX5hrcR/wm6KZ9uqm+3TVseYv52Jchgdug zv/zh0u+stRXoudI34md+LWj3JzHFmQKvE3tlg2facQAYErqSux/Yq+oJytuFBbIeQ5H dlNsl+23xVfb65rihc9XN7nvkYnLWEwUCdfYY4AGlBqfYSbciyBRI1ChvQ/PJ3HUvKiy r51Q== X-Gm-Message-State: AElRT7Hgv3dDR6lvPX6rW+K7toX3d4iiuYAKhC0x86Sd5HApdnQ0bqLN bthiNmTO/Umo2W+kF6wMZ5hpkO1aRkhNQTKx8BfzPwOm X-Google-Smtp-Source: AG47ELsvBh7+qaUoaEmdZvFj/ClzwuOPMpUK9w4H5eSJm2nFrFYY7+ldrbKQMJDOUP48VM6ZBchPksq+tqGVI92qxhc= X-Received: by 10.107.20.213 with SMTP id 204mr42522645iou.239.1522170926126; Tue, 27 Mar 2018 10:15:26 -0700 (PDT) MIME-Version: 1.0 Sender: carpeddiem@gmail.com Received: by 10.107.130.197 with HTTP; Tue, 27 Mar 2018 10:15:05 -0700 (PDT) In-Reply-To: References: From: Ed Maste Date: Tue, 27 Mar 2018 13:15:05 -0400 X-Google-Sender-Auth: sektya6LYFVR1ieeDT__ysn16kU Message-ID: Subject: Re: Heads-up: linker (lld) changes for amd64 coming soon To: Antoine Brodin Cc: FreeBSD Current , "freebsd-toolchain@FreeBSD.org" Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Mar 2018 17:15:27 -0000 On 27 March 2018 at 02:20, Antoine Brodin wrote: >> 1. Kostik (kib@) has a patch to start using kernel ifunc, with the >> first use being Supervisor Mode Access Prevention (SMAP) on amd64. >> This relies on linker support that is available in the in-tree lld and >> in contemporary binutils ld.bfd from ports, but not in the in-tree >> ld.bfd 2.17.50. > > I have no concerns about 1. OK. My guess is I won't get any other feedback on this one until it makes it into a release. I suspect kib will commit this part later this week or early next week. >> 2. WITH_LLD_IS_LD controls whether /usr/bin/ld is ld.bfd or ld.lld, >> and thus the linker used for linking ports. I plan to switch this to >> default on. >> > > About 2., I am concerned that changes breaking a large number of > ports are committed without portmgr@ approval. > If WITH_LLD_IS_LD is committed as is on amd64, packages for head > won't be published as it doesn't meet our current criteria for > publication. Fair enough - this was the reason I sent the email. I've now gone through and submitted a PR for for each failure that did not already have one. I've also added LLD_UNSAFE to a few ports where where it was straightforward. In this batch of PRs I noticed four main issues: 1. Ports that pass compiler flags, such as -fPIC, to the linker. lld has more strict command-line parsing and rejects these invalid invocations, while ld.bfd happily creates bogus output (e.g. a shared library with a DT_AUXILIARY entry of "PIC"). PR 221808 has a reasonable discussion of this issue. 2. lld has no built-in search paths (/lib, /usr/lib). Normally the linker is invoked from the compiler driver, which provides default search paths. If lld is invoked directly then library search paths must be specified explicitly with -L/lib -L/usr/lib. 3. Shared library protected visibility symbol preemption. 4. lld does not have a built-in default output target. For the common use of the linker (linking individual .o objects into an executable or shared object) lld infers the target from the first object file. However, when the linker is used to convert an arbitrary binary file into an ELF ojbect (via -r -b binary) lld needs the output target to be specified explicitly with -m. The vast majority of skipped ports in the exp-run come from two failures: lang/ghc (PR226872) and lang/fpc (222172). The PR for lang/ghc reports that the current released version of ghc mentions improved lld support; I hope the port update will solve this issue. I submitted a bug report upstream for lang/fpc about one fpc bug that affected lld, and that issue has now been resolved upstream. We'll need to check again once the port is updated. From owner-freebsd-toolchain@freebsd.org Tue Mar 27 22:21:38 2018 Return-Path: Delivered-To: freebsd-toolchain@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 88369F649D9; Tue, 27 Mar 2018 22:21:38 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: from mail-io0-x22f.google.com (mail-io0-x22f.google.com [IPv6:2607:f8b0:4001:c06::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1B95986322; Tue, 27 Mar 2018 22:21:38 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: by mail-io0-x22f.google.com with SMTP id q84so1119324iod.10; Tue, 27 Mar 2018 15:21:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=C5okqPpCN6Vy6lfZ+2Si8dSZovPG6UVeDRk7RRbc+4U=; b=XdQInpDhib4KYkjWO7kyJ4cI0S7a+RL3XDQz+27aF/uFvCnAeyzDw6EWjXXMBnuZWq fLHiEHoHyDobhMUpgG7Vull54yCTnFb8Iz3ZlaIZ8TW4a+faCUde8hX9OnyrAPOCkWPr sYhiEeWY4dDQIzdTItA3Q0r5BUeelMCFDVGvqO2kJrQbXg8b/hmrXAJSac7aPGKyN+G4 RSwVBxSQ391J50lLCupbHdycCWT/AK/kk0zrV1+kkJ3IpKsNKyChshc+SUaRQF0wn90x V/LU0Y2NU3sKZzxR3voICeibNwK0s+TU0HpiZpz9XhcdK5zrO7uycaQ8OFAAsqhBQknA gCmA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=C5okqPpCN6Vy6lfZ+2Si8dSZovPG6UVeDRk7RRbc+4U=; b=W9J1MX7651pGFpW6xClcRiHOcHkWPoXKe/pfDc2Y3SSOIi9o3FsPGDN1h3NL1ThilC w4xZZyf/D5j8kJ0/rzCKgPReMgg9NGO9RLzUQ9FwKWdbR6HTes2tBNWfbAjZJgukZf2F 5oziaU5xxY+Nj5kmsmGXQMJOmbzISO9v7eryjzltx6UVXat7VScNCbtVwnKeL0xIym1t a8231VBDvqN/vsxYBglWIqh47tHs4oYtb5oKvfzAKEgJtBegvldn5ZVT4EjTiS2oaeFs hR+x83H96tDNpOP1unTIpdTR4++wk5XXLqkMCAw/QsWVia7hsUXVR/6Zqh7x6LonngPf rAwg== X-Gm-Message-State: AElRT7GfFs2pd3kP5CMSK1DYLMbYD03xIHTddflg1EDBLOipeEbXQdRl KrazB/UUyewJuXP6WTta8unC9Wp4cwCIYpp2812nE+Wx X-Google-Smtp-Source: AIpwx48Jc1EcR1Ef7/lfyByFnxObQL6hyXe93hUj3k195IqtVbcXabBLoHbAzbnfMFaWFBKwSezlG6512SAD41eOt28= X-Received: by 10.107.178.14 with SMTP id b14mr14150120iof.294.1522189297416; Tue, 27 Mar 2018 15:21:37 -0700 (PDT) MIME-Version: 1.0 Sender: carpeddiem@gmail.com Received: by 10.107.130.197 with HTTP; Tue, 27 Mar 2018 15:21:16 -0700 (PDT) In-Reply-To: References: From: Ed Maste Date: Tue, 27 Mar 2018 18:21:16 -0400 X-Google-Sender-Auth: LbqtM0Nwt5v0L9q3Yiin9bwl9ow Message-ID: Subject: Re: Heads-up: linker (lld) changes for amd64 coming soon To: Antoine Brodin Cc: "freebsd-toolchain@FreeBSD.org" , FreeBSD Ports Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Mar 2018 22:21:38 -0000 (Moved from -current to -ports) On 27 March 2018 at 13:15, Ed Maste wrote: > > Fair enough - this was the reason I sent the email. I've now gone > through and submitted a PR for for each failure that did not already > have one. I've also added LLD_UNSAFE to a few ports where where it was > straightforward. Via tobik's commit to lang/myrddin (r465725) I discovered BINARY_ALIAS=ld=ld.bfd, which is a usable workaround for some ports which don't honour $LD or -fuse-ld=bfd in CFLAGS. As you point out in reply to my r465755 BINARY_ALIAS alone is not sufficient, because arm64 does not provide ld.bfd by default and LLD_UNSAFE automatically brings in ports binutils if /usr/bin/ld.bfd does not exist. So we need both LLD_UNSAFE and BINARY_ALIAS. Should we just have LLD_UNSAFE also set BINARY_ALIAS=ld=ld.bfd? From owner-freebsd-toolchain@freebsd.org Thu Mar 29 17:14:47 2018 Return-Path: Delivered-To: freebsd-toolchain@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 815D6F63ED0; Thu, 29 Mar 2018 17:14:47 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: from mail-it0-x22b.google.com (mail-it0-x22b.google.com [IPv6:2607:f8b0:4001:c0b::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 13F9B7927A; Thu, 29 Mar 2018 17:14:47 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: by mail-it0-x22b.google.com with SMTP id m134-v6so9044426itb.3; Thu, 29 Mar 2018 10:14:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=EIYxdhL19uauO3A0xCVX7Mr95IUSD6M9fhaMXo1RZP4=; b=AZfL/kjegsC2WKQp+PQI2wqVBZfNxzMUdgpxU5qIBa0bFRtwxzIaoE7C2dpJn+xtgc XWDFSQA4bUDt/EU4Jmn76GCPRO29n21JlRYZbtyULWZnKUQyqp+ZxYvHJFFE7uy/oVf3 WmRQ76d69yZzoGWVC6P/hGma+lUV2gRsG9e3BVHUM9mEPvcVWHdi7rrvCUunz5jSNTVj c8pCq+yAh6rEK7MKHR36jTAJpSsiqwDAhvJXAKkxxz9fgS8ehSDh6N0CMBorKvd59cU8 UqiXda/EPkjNmW4GaPLlm6zwHvqf6frT6DUagzHGxZV+5QPGO3m29kg3r5tzBG8iL3u7 RLnQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=EIYxdhL19uauO3A0xCVX7Mr95IUSD6M9fhaMXo1RZP4=; b=kcmkOgv3sxkw4yKOcTEbkbnAdsx3rY9QBi9gqKkepDClICZAzP8i4tk0/isRTS2y4i 1MOrzQxaoYxL4ZJC7uTP1cA0y9aozVL8yuBpOOdSmjeg7tL1V62DAZ2PqIu20gV4/TfA ATQn3JQe9UY78xYrN3unIBMJmAbVFASZUdU2RPGpKcW+Hkf9FM7trNQcjVF84siCKrcr fTV/ijUoZSsO70Rl+124ze46NCl8b968ZKcbxx0o4T43V/84cMLb1WqvnNkJZUVhsSkC CwxUhCRRm5m0PnfaGYTbkfVBrLDPqgXPaxJ+WozD1Y9HKaU550Gz65WC5oeQXoW+2OXD O6aQ== X-Gm-Message-State: AElRT7G/dX4FlIl9Q1DWLO5JysnXLM3HOLRY1V9LSRTVHEg8dC0VpHp8 vjkzJDtocg+oPhUM99VK3QNcT+aesaZBxfvwUuQIlA== X-Google-Smtp-Source: AIpwx49AgorUEiX/LBk+TitT6z+e0N3vncxnMTkdqPlc/aPjMSiuu5J7I/YPCU6LxSsjkIm/V7SgsLDdNufg3WA4rGY= X-Received: by 2002:a24:230a:: with SMTP id u10-v6mr8257211itu.49.1522343686071; Thu, 29 Mar 2018 10:14:46 -0700 (PDT) MIME-Version: 1.0 Sender: carpeddiem@gmail.com Received: by 10.107.130.197 with HTTP; Thu, 29 Mar 2018 10:14:25 -0700 (PDT) In-Reply-To: References: From: Ed Maste Date: Thu, 29 Mar 2018 13:14:25 -0400 X-Google-Sender-Auth: LGUeForAkE3sOIg-cZiE1sbJHwg Message-ID: Subject: Re: Heads-up: linker (lld) changes for amd64 coming soon To: Antoine Brodin Cc: "freebsd-toolchain@FreeBSD.org" , FreeBSD Ports Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Mar 2018 17:14:47 -0000 On 27 March 2018 at 18:21, Ed Maste wrote: > (Moved from -current to -ports) > > On 27 March 2018 at 13:15, Ed Maste wrote: >> >> Fair enough - this was the reason I sent the email. I've now gone >> through and submitted a PR for for each failure that did not already >> have one. I've also added LLD_UNSAFE to a few ports where where it was >> straightforward. > > Via tobik's commit to lang/myrddin (r465725) I discovered > BINARY_ALIAS=ld=ld.bfd, which is a usable workaround for some ports > which don't honour $LD or -fuse-ld=bfd in CFLAGS. As of ports r465900 BINARY_ALIAS is now set automatically if LLD_UNSAFE is set. There are now 14 PRs open for failures when lld is /usr/bin/ld. Thanks to recent commits from krion@ all unmaintained ports that had issues have been addressed, except for print/openprinting (PR221809) and some openal-related failures (PR226980). I'll try to take a look at the openal issues; it's likely that the interim solution will be just to set LLD_UNSAFE in all of the dependent ports. The remaining 12 PRs are all for maintained ports. I believe that now the only port responsible for a significant number of skipped dependent ports is lang/ghc (PR226872).