From owner-freebsd-toolchain@freebsd.org Tue Feb 14 15:57:14 2017 Return-Path: Delivered-To: freebsd-toolchain@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 789A0CDF67E; Tue, 14 Feb 2017 15:57:14 +0000 (UTC) (envelope-from wolfgang.meyer@hob.de) Received: from hobex29.hob.de (hobex19.hob.de [212.185.199.31]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D5B0916D1; Tue, 14 Feb 2017 15:57:13 +0000 (UTC) (envelope-from wolfgang.meyer@hob.de) Received: from HOBEX12.hob.de (172.22.1.12) by hobex19.hob.de (172.25.1.31) with Microsoft SMTP Server (TLS) id 14.2.347.0; Tue, 14 Feb 2017 16:56:54 +0100 Received: from HOBEX11.hob.de ([fe80::b99f:1c54:7122:49b4]) by HOBEX12.hob.de ([::1]) with mapi id 14.02.0387.000; Tue, 14 Feb 2017 16:57:01 +0100 From: "Meyer, Wolfgang" To: "'freebsd-arm@FreeBSD.org'" , "'freebsd-toolchain@FreeBSD.org'" Subject: RE: How to get a crosscompile toolchain for aarch64 for use in poudriere[?] Thread-Topic: How to get a crosscompile toolchain for aarch64 for use in poudriere[?] Thread-Index: AdKDrhWkwDVgm5wmQJOmHv89OT16WQACrmdQAMgAHTA= Date: Tue, 14 Feb 2017 15:57:01 +0000 Message-ID: References: In-Reply-To: Accept-Language: de-DE, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [172.24.71.140] old-x-esetresult: clean, is OK old-x-esetid: 4EB48F3AB80C295018F1D5 x-esetresult: clean, is OK x-esetid: 4EB48F3AB80C295018F1D5 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.23 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, 14 Feb 2017 15:57:14 -0000 > -----Original Message----- > From: Meyer, Wolfgang > Sent: Freitag, 10. Februar 2017 17:19 > To: Meyer, Wolfgang; 'freebsd-arm@FreeBSD.org'; 'freebsd- > toolchain@FreeBSD.org' > Subject: RE: How to get a crosscompile toolchain for aarch64 for use in > poudriere[?] > > > Hello, > > > > > > To make the long story short, after comparing the verbose output of my > > compiling in the jails with that of a direct crosscompile I found out > > that it was able to correctly link some object files when providing > > absolute paths to the crt*.o files and correct library search path for = the > libgcc_something libraries. > > Which of course doesn't help when the linker is implicitly called by > > the compiler. Further research showed that I could crosscompile/link > > when providing the --sysroot=3D/ flag to overwrite the sysroot > > configuration from the build of the crosscompiler. Amending the lines > > > > CFLAGS+=3D--sysroot=3D/ > > CPPFLAGS+=3D--sysroot=3D/ (Don't know if needed) > > CXXFLAGS+=3D--sysroot=3D/ > > LDFLAGS+=3D--sysroot=3D/ > > > > to my poudriere make.conf file I finally was able to produce a working > > cross- compiled package for aarch64 in poudriere. And the gains are > > quite significant (around 21 minutes for building pkg package with > > qemu-user emulation vs 5 minutes using cross-compilation, native amd64 > > build in poudriere finishes in less than a minute). > > > > Still the creation of the cross-compiling toolchain seems to be quite > > cumbersome. Hence advice on getting such a toolchain in a cleaner way > > (ideally probably a working build for the xdev target) are greatly > appreciated. > > > > > After building some more packages besides of pkg it seems, I am still not > there yet. There is quite some fallout mainly during configure due to not > getting the right searchpath for the libraries. Maybe creating a symlink = on the > root directory at the path of the expected sysroot directory might heal t= his. In the meantime I figured out how to tweak the jail to get it to cross-buil= d the desired subset of ports without fallout. Some of the changes are mere= ly cosmetic but lead to a cleaner overall configuration in my point of view= . Changes to the previously described configuration include: - before starting the kernel-toolchain build make two nullfs-mounts: > mount -t nullfs //usr/src /usr/src > mount -t nullfs //usr/obj /usr/obj - after kernel-toolchain build and copying //usr/ob= j/usr/src/tmp/* to //usr/aarch64-freebsd delete //usr/obj/usr/src/tmp and create a symlink to / at //usr/obj/usr/src/tmp Now all tested ports cross-build fine with varying speed gains compared to = the qemu-user emulated (in the ballpark of two- to eightfold, but not analy= sed in detail). ________________________________ Follow HOB: - HOB: http://www.hob.de/redirect/hob.html - Xing: http://www.hob.de/redirect/xing.html - LinkedIn: http://www.hob.de/redirect/linkedin.html - HOBLink Mobile: http://www.hob.de/redirect/hoblinkmobile.html - Facebook: http://www.hob.de/redirect/facebook.html - Twitter: http://www.hob.de/redirect/twitter.html - YouTube: http://www.hob.de/redirect/youtube.html - E-Mail: http://www.hob.de/redirect/mail.html HOB GmbH & Co. KG Schwadermuehlstr. 3 D-90556 Cadolzburg Geschaeftsfuehrung: Klaus Brandstaetter, Zoran Adamovic AG Fuerth, HRA 5180 Steuer-Nr. 218/163/00107 USt-ID-Nr. DE 132747002 Komplementaerin HOB electronic Beteiligungs GmbH AG Fuerth, HRB 3416 From owner-freebsd-toolchain@freebsd.org Wed Feb 15 15:19:41 2017 Return-Path: Delivered-To: freebsd-toolchain@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 76B1BCE055C for ; Wed, 15 Feb 2017 15:19:41 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 65DB11DE for ; Wed, 15 Feb 2017 15:19:41 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v1FFJeB4014654 for ; Wed, 15 Feb 2017 15:19:41 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-toolchain@FreeBSD.org Subject: [Bug 216908] security/gnutls: does not build on 12-CURRENT aarch64 after llvm 3.9 toolchain integration Date: Wed, 15 Feb 2017 15:19:41 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: commit-hook@freebsd.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-toolchain@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Feb 2017 15:19:41 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D216908 --- Comment #4 from commit-hook@freebsd.org --- A commit references this bug: Author: emaste Date: Wed Feb 15 15:18:44 UTC 2017 New revision: 313773 URL: https://svnweb.freebsd.org/changeset/base/313773 Log: MFC r313458: lld: Allow arbitrary code alignment in .eh_frame According to the specification, CIE code alignment factor is an arbitrary unsigned LEB128 encoded value. PR: 216908 Changes: _U stable/11/ stable/11/contrib/llvm/tools/lld/ELF/EhFrame.cpp --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-toolchain@freebsd.org Wed Feb 15 15:20:00 2017 Return-Path: Delivered-To: freebsd-toolchain@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id F2D9FCE05A4 for ; Wed, 15 Feb 2017 15:20:00 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id E1A54211 for ; Wed, 15 Feb 2017 15:20:00 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v1FFK02U025230 for ; Wed, 15 Feb 2017 15:20:00 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-toolchain@FreeBSD.org Subject: [Bug 216908] security/gnutls: does not build on 12-CURRENT aarch64 after llvm 3.9 toolchain integration Date: Wed, 15 Feb 2017 15:20:00 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: bin X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: emaste@freebsd.org X-Bugzilla-Status: Closed X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: emaste@freebsd.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status version product resolution component assigned_to Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Feb 2017 15:20:01 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D216908 Ed Maste changed: What |Removed |Added ---------------------------------------------------------------------------- Status|New |Closed Version|Latest |CURRENT Product|Ports & Packages |Base System Resolution|--- |FIXED Component|Individual Port(s) |bin Assignee|freebsd-toolchain@FreeBSD.o |emaste@freebsd.org |rg | --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-toolchain@freebsd.org Fri Feb 17 08:14:51 2017 Return-Path: Delivered-To: freebsd-toolchain@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DDEA9CE2C98 for ; Fri, 17 Feb 2017 08:14:51 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-210-74.reflexion.net [208.70.210.74]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 8BB7C161A for ; Fri, 17 Feb 2017 08:14:51 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 14487 invoked from network); 17 Feb 2017 08:16:46 -0000 Received: from unknown (HELO mail-cs-01.app.dca.reflexion.local) (10.81.19.1) by 0 (rfx-qmail) with SMTP; 17 Feb 2017 08:16:46 -0000 Received: by mail-cs-01.app.dca.reflexion.local (Reflexion email security v8.30.0) with SMTP; Fri, 17 Feb 2017 03:14:44 -0500 (EST) Received: (qmail 24471 invoked from network); 17 Feb 2017 08:14:43 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (AES256-SHA encrypted) SMTP; 17 Feb 2017 08:14:43 -0000 Received: from [192.168.1.111] (c-67-170-167-181.hsd1.or.comcast.net [67.170.167.181]) by iron2.pdx.net (Postfix) with ESMTPSA id 316EDEC7B43; Fri, 17 Feb 2017 00:14:43 -0800 (PST) From: Mark Millard Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\)) Subject: arm64 libc.so.7.full link: Are the 8 "R_AARCH64_ABS64 used with TLS symbol . . ." notices a problem? Message-Id: Date: Fri, 17 Feb 2017 00:14:42 -0800 To: freebsd-arm , FreeBSD Toolchain X-Mailer: Apple Mail (2.3259) X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Feb 2017 08:14:52 -0000 [This happens to be a amd64 -> arm64 cross build context.] Context: # uname -paKU FreeBSD FreeBSDx64 12.0-CURRENT FreeBSD 12.0-CURRENT r313783M amd64 = amd64 1200020 1200020 In exploring how to investigate tsd_booted assert failures I noticed the following in: /usr/obj/pine64_clang/arm64.aarch64/usr/src/lib/libc/libc.so.7.full.meta # Meta data file = /usr/obj/pine64_clang/arm64.aarch64/usr/src/lib/libc/libc.so.7.full.meta CMD @echo building shared library libc.so.7 CMD @rm -f libc.so.7 libc.so CMD cc -B/usr/local/aarch64-freebsd/bin/ -mcpu=3Dcortex-a53 -target = aarch64-unknown-freebsd12.0 = --sysroot=3D/usr/obj/pine64_clang/arm64.aarch64/usr/src/tmp = -B/usr/local/aarch64-freebsd/bin/ -nodefaultlibs = -Wl,--version-script=3DVersion.map -shared -Wl,-x -Wl,--fatal-warnings = -Wl,--warn-shared-textrel -o libc.so.7.full -Wl,-soname,libc.so.7 = `NM=3D'/usr/local/aarch64-freebsd/bin/nm' NMFLAGS=3D'' lorder = bt_close.pico . . . (long list of .pico files) . . . wmemset.pico | tsort -q` -lcompiler_rt -lssp_nonshared CWD /usr/obj/pine64_clang/arm64.aarch64/usr/src/lib/libc TARGET libc.so.7.full -- command output -- building shared library libc.so.7 /usr/local/aarch64-freebsd/bin/ld: getutxent.pico(.debug_info+0x3b): = R_AARCH64_ABS64 used with TLS symbol udb /usr/local/aarch64-freebsd/bin/ld: getutxent.pico(.debug_info+0x58): = R_AARCH64_ABS64 used with TLS symbol uf /usr/local/aarch64-freebsd/bin/ld: utxdb.pico(.debug_info+0x5a): = R_AARCH64_ABS64 used with TLS symbol futx_to_utx.ut /usr/local/aarch64-freebsd/bin/ld: jemalloc_tsd.pico(.debug_info+0x3c): = R_AARCH64_ABS64 used with TLS symbol __je_tsd_tls /usr/local/aarch64-freebsd/bin/ld: = jemalloc_tsd.pico(.debug_info+0x146e): R_AARCH64_ABS64 used with TLS = symbol __je_tsd_initialized /usr/local/aarch64-freebsd/bin/ld: = cxa_thread_atexit_impl.pico(.debug_info+0x3b): R_AARCH64_ABS64 used with = TLS symbol dtors /usr/local/aarch64-freebsd/bin/ld: xlocale.pico(.debug_info+0x403): = R_AARCH64_ABS64 used with TLS symbol __thread_locale /usr/local/aarch64-freebsd/bin/ld: setrunelocale.pico(.debug_info+0x3c): = R_AARCH64_ABS64 used with TLS symbol _ThreadRuneLocale Are these R_AARCH64_ABS64 notices expected? Are they a problem? I also notice that the "filemon acquired metadata" does not list an entry to match up with: /usr/src/lib/libc/stdlib/jemalloc/Symbol.map So it would appear that changes to the Symbol.map file would not of themselves cause things to rebuild or relink. =3D=3D=3D Mark Millard markmi at dsl-only.net From owner-freebsd-toolchain@freebsd.org Fri Feb 17 14:07:34 2017 Return-Path: Delivered-To: freebsd-toolchain@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BC739CE3511; Fri, 17 Feb 2017 14:07:34 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from mail.soaustin.net (mail.soaustin.net [192.108.105.60]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.soaustin.net", Issuer "StartCom Class 2 IV Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 9FBC7120F; Fri, 17 Feb 2017 14:07:34 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from lonesome.com (bones.soaustin.net [192.108.105.22]) by mail.soaustin.net (Postfix) with ESMTPSA id A0B7C27F; Fri, 17 Feb 2017 08:07:32 -0600 (CST) Date: Fri, 17 Feb 2017 08:07:31 -0600 From: Mark Linimon To: Mark Millard Cc: freebsd-arm , FreeBSD Toolchain Subject: Re: arm64 libc.so.7.full link: Are the 8 "R_AARCH64_ABS64 used with TLS symbol . . ." notices a problem? Message-ID: <20170217140731.GA7285@lonesome.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Feb 2017 14:07:34 -0000 On Fri, Feb 17, 2017 at 12:14:42AM -0800, Mark Millard wrote: > Are these R_AARCH64_ABS64 notices expected? Are they a problem? Is the following post relevant? https://lists.freebsd.org/pipermail/svn-ports-all/2017-February/144857.html mcl