From owner-freebsd-testing@FreeBSD.ORG Tue Mar 31 20:43:57 2015 Return-Path: Delivered-To: freebsd-testing@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B342735C; Tue, 31 Mar 2015 20:43:57 +0000 (UTC) Received: from mail-la0-x229.google.com (mail-la0-x229.google.com [IPv6:2a00:1450:4010:c03::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 20CC0349; Tue, 31 Mar 2015 20:43:57 +0000 (UTC) Received: by lajy8 with SMTP id y8so22003265laj.0; Tue, 31 Mar 2015 13:43:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=tgOg5TRSa9dHqz/NEIQiXU392nOIU7PEBS3Yg6oorJQ=; b=ldLIl8iggAtRgITy6sXVhOyMlmpxybuCXXtOiTZeAqyef3FsgtdfHdQHszgB7mv1My wkSOLiKe0gM+EIhgvOpt2cAdmoswZC52LAwU8ne77QyWs51zesAKO1skJpq9VnjvRKzz tyrIWV/xbFUIqA5+NfMPxlyjy+DLZQ4rNwrNEZNJqNkYCVKY2G0mWgQNm8hNMtrfBSkp az2rwf4VS9bFAYoc8x4kyTm8vDGY7leDc7G3/13R2LYykBIZWyGdGKmbVzQ5MUkZBsh8 4ZrazSRVj9zpqDiY/QdPtRz032ssDae3EZDeiKaT/3CElEI/onwAJNFRTPDbyTAckkcQ qyqA== MIME-Version: 1.0 X-Received: by 10.152.234.108 with SMTP id ud12mr32610584lac.81.1427834635120; Tue, 31 Mar 2015 13:43:55 -0700 (PDT) Sender: crodr001@gmail.com Received: by 10.112.108.168 with HTTP; Tue, 31 Mar 2015 13:43:55 -0700 (PDT) In-Reply-To: References: <5F90BE99-E82C-4444-9E4C-5963B40AA3B0@FreeBSD.org> <5B103C77-EA63-4C04-95FE-B138CF46F01C@FreeBSD.org> Date: Tue, 31 Mar 2015 13:43:55 -0700 X-Google-Sender-Auth: 572U2nCJfA2v5UaNLbAKHqEBVcY Message-ID: Subject: Re: CROSS_TOOLCHAIN=amd64-gcc fails to build after clang 3.6.0 import From: Craig Rodrigues To: Dimitry Andric Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: "freebsd-testing@freebsd.org" , FreeBSD Toolchain X-BeenThere: freebsd-testing@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Testing on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 Mar 2015 20:43:57 -0000 On Tue, Mar 31, 2015 at 1:41 PM, Dimitry Andric wrote: > On 31 Mar 2015, at 22:06, Craig Rodrigues wrote: > > > > On Tue, Mar 31, 2015 at 12:48 PM, Dimitry Andric > wrote: > > On 31 Mar 2015, at 21:38, Craig Rodrigues wrote: > > > > > > On Tue, Mar 31, 2015 at 11:20 AM, Dimitry Andric > wrote: > > > > > >> On 31 Mar 2015, at 20:13, Dimitry Andric wrote: > > >> ... > > >>> but then: > > >>> > > >>> + patch > > >>> Hmm... Looks like a unified diff to me... > > >>> The text leading up to this was: > > >>> -------------------------- > > >>> |Index: contrib/libc++/include/type_traits > > >>> |=================================================================== > > >>> |--- contrib/libc++/include/type_traits (revision 280762) > > >>> |+++ contrib/libc++/include/type_traits (working copy) > > >>> -------------------------- > > >>> Patching file contrib/libc++/include/type_traits using Plan A... > > >>> Reversed (or previously applied) patch detected! Assume -R? [y] > > >>> Hunk #1 succeeded at 842. > > >>> Hunk #2 succeeded at 877. > > >>> Hmm... Ignoring the trailing garbage. > > >>> done > > >>> > > >>> E.g., it undoes the change to type_traits that was merged in the > > >> subversion update. > > >> > > >> > > > OK, I undid the patch. Now the clang and libc++ parts build, but I'm > > > still getting problems building rescue: > > > > > > > https://jenkins.freebsd.org/job/FreeBSD_HEAD_external_toolchain_gcc/29/console > > > > Hm, that is strange. I have just completed a build with > > amd64-xtoolchain-gcc, and apart from boot2, everything worked... > > > > What does readelf say when you run it on the cat.lo file which is > > complained about in the log? And what happens if you delete it, and > > restart the build? > > > > See: > > > https://lists.freebsd.org/pipermail/freebsd-toolchain/2015-March/001545.html > > I'm suspecting this might have something to do with crunchide, or least, > the copy of crunchide that is run for this: > > --- cat.lo --- > /usr/local/x86_64-freebsd/bin/ld -dc -r -o cat.lo cat_stub.o > /builds/FreeBSD_HEAD_external_toolchain_gcc/obj/builds/FreeBSD_HEAD_external_toolchain_gcc/rescue/rescue//builds/FreeBSD_HEAD_external_toolchain_gcc/bin/cat/cat.o > crunchide -k _crunched_cat_stub cat.lo > > If I look at my own build logs, it seems to pick the crunchide > executable in /usr/bin, and Makefile.inc1 does *not* build it during the > cross-tools stage if ${TARGET_ARCH} is the same as ${MACHINE_ARCH}: > > .if ${TARGET_ARCH} != ${MACHINE_ARCH} > .if ${MK_RESCUE} != "no" || defined(RELEASEDIR) > _crunchide= usr.sbin/crunch/crunchide > .endif > > However, this does not explain why my /usr/bin/crunchide seems to not > screw up cat.lo, while yours does. As far as I can see, we're both > building this on a stable/10 amd64 box... > > Maybe, as a hack, you can force cross-tools to build crunchide, by > patching Makefile.inc1 to ignore the arch check, and see what that > results in? > Well my build host is 10.1-RELEASE, so maybe there are changes that went into 10-STABLE after 10.1 that prevent this from working. I'll give a shot at hacking things and let you know how far I get. -- Craig