From owner-freebsd-current@freebsd.org Sun Dec 3 01:45:22 2017 Return-Path: Delivered-To: freebsd-current@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 A1374E6FE4B for ; Sun, 3 Dec 2017 01:45:22 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from vps-mail.nomadlogic.org (mail.nomadlogic.org [IPv6:2607:f2f8:a098::2]) (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 8038D63F80 for ; Sun, 3 Dec 2017 01:45:22 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from [192.168.1.208] (cpe-23-242-94-236.socal.res.rr.com [23.242.94.236]) by vps-mail.nomadlogic.org (OpenSMTPD) with ESMTPSA id c3c7993f TLS version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO; Sat, 2 Dec 2017 17:45:09 -0800 (PST) Subject: Re: Error attempting to link during buildworld To: Warner Losh Cc: FreeBSD Current References: <520eb756-6d01-23d2-3321-b3db6dc3438c@nomadlogic.org> <2e3d1848-81ed-6112-33c6-424b33a85fd6@nomadlogic.org> From: Pete Wright Message-ID: <23a00406-e318-7775-29a4-88f884a51f2a@nomadlogic.org> Date: Sat, 2 Dec 2017 17:45:17 -0800 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Dec 2017 01:45:22 -0000 On 12/02/2017 12:30, Warner Losh wrote: > On Sat, Dec 2, 2017 at 12:50 PM, Pete Wright wrote: > >> >> On 12/01/2017 11:43, Pete Wright wrote: >> >>> Hi All, >>> >>> I am running into this error when attempting to buildworld from a >>> checkout I made recently (git hash 76ca06b62f3bfb21f1f2e1295eb89e >>> 3c235bdda7) >>> >>> --- all_subdir_stand --- >>> /usr/home/pete/git/freebsd/stand/i386/libi386/libi386.a(bootinfo64.o): >>> In function `bi_checkcpu': >>> /usr/home/pete/git/freebsd/stand/i386/libi386/bootinfo64.c:149: >>> undefined reference to `read_eflags' >>> /usr/home/pete/git/freebsd/stand/i386/libi386/bootinfo64.c:150: >>> undefined reference to `write_eflags' >>> /usr/home/pete/git/freebsd/stand/i386/libi386/bootinfo64.c:151: >>> undefined reference to `read_eflags' >>> cc: error: linker command failed with exit code 1 (use -v to see >>> invocation) >>> *** [loader.sym] Error code 1 >>> >>> >>> Has anyone else seen this? I'm not sure if I have some stale files that >>> need to be purged, or if this is a bug due to me using ccache. I'm asking >>> here tho as I'd love to preserve my ccache and save some cycles rebuilding >>> LLVM :) >>> >> just following up on this thread - i assume others have been able to >> buildworld on amd64, and have not been getting this linker error? i have a >> fresh checkout from this morning, tested with and without ccache and am >> still getting this same error. my system is currently at this revision: >> >> $ uname -ar >> FreeBSD runner 12.0-CURRENT FreeBSD 12.0-CURRENT #1 63d5d6c71fb(master): >> Sat Nov 18 08:36:45 PST 2017 pwright@runner:/usr/obj/usr/ho >> me/pwright/git/freebsd/amd64.amd64/sys/GENERIC-EVDEV amd64 >> >> >> any tips on helping debug this as well would be appreciated - as i'm not >> %100 sure where to start (i.e. how to invoke the linker with the "-v" flag >> for buildworld :) > > With today's tree, I can both build the loader by hand and as part of > buildworld. I'm keen on fixing this, but I've no clue why it's failing for > you. > > Have any weird optimizer settings? Do you get any reports of functions not > declared? thanks for getting back to me Warner. I do not have any optimization flags, although while i do use ccache i am able to reproduce this by disabling it in src.conf. i also am not seeing any reports of functions not being declared, although i'm currently re-testing the build now with a single worker passed to make so that i can get clearer output to validate this. i'm also going to try on another box running current i have to see if this is just my laptop being silly or if there is a real issue. cheers, -pete -- Pete Wright pete@nomadlogic.org @nomadlogicLA