From owner-freebsd-current@freebsd.org Mon Aug 7 04:32:42 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 91628DB5B2E for ; Mon, 7 Aug 2017 04:32:42 +0000 (UTC) (envelope-from aijazbaig1@gmail.com) Received: from mail-vk0-x229.google.com (mail-vk0-x229.google.com [IPv6:2607:f8b0:400c:c05::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 428F67ECC9; Mon, 7 Aug 2017 04:32:42 +0000 (UTC) (envelope-from aijazbaig1@gmail.com) Received: by mail-vk0-x229.google.com with SMTP id j189so5165713vka.0; Sun, 06 Aug 2017 21:32:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=gvOr04wqEHP9kef2Az11CxbbPOo8bxTGWeCGZn5Yd6M=; b=J6sWdG3MDfqKmjyCg2oSV6mR/mk230fa8f+Y7tkYkrteDwWh66zQii3A16ag3ZVGbI sVIbW28mFpeHQSiXIhZYw37ew1db+91wtrKxcJbxpNbAcKSY90Jj/p6VKCVN057VyzYr EwkZO1r8Ol+GgIUVMhPUbtwLF+SrBXiQlOw3lsZ4OBzLR2twJCIsn94ZIlJ5gxlwbwy7 9DPL8F8DQwlctaY24YW3Vqg0UfagcA6yjaErdVLwshlsNSPUUYySGrUdj/S3WrV1ur/Y 3CAhlcn+YiRMcf3CZ39nrVqt3si9uCN556GpIvB/c4ZJyihZvv0VBN7aFVCy25u12RGd BMtA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=gvOr04wqEHP9kef2Az11CxbbPOo8bxTGWeCGZn5Yd6M=; b=Vblqo2oaLzsetr/bPmFjmAOIPAP0v98D1UGr/WXroooRrq+FkAayKOecIBvBbYiOnW vk2D95jCukD+x7xlFU1yCs56b6SpStqmPmflVSxAOT96Euc1DNYQtnkev2mfMVQ1VqkE EYTCbsYakxc9C+dNuj5G7i7XZvM//FP70ru7JpWLPP6PTvBjDq0OfCYSTS5yl/GwrXyY t1LeIiuI0olawUcN7bb2Nro3y+Ay136Vs4ZlxG3HAZKs101ScEaVi1syMeZouvz5f0KX BpvZ0wPAhWepZpu+r2FcUR4ObygkT1heXoYkWqDAveklwKDEZS6uSRA8E+lwxXup5tNV 2YnQ== X-Gm-Message-State: AHYfb5gPSypoUSpNzhtfXxS6fdYAwJ5KS1pRfsNOoT8dGaoqPphxfB7d nlGi8k3Tw2qtGGurkEJfwqzmj6ZigSFhwpI= X-Received: by 10.31.50.137 with SMTP id y131mr6187331vky.181.1502080361015; Sun, 06 Aug 2017 21:32:41 -0700 (PDT) MIME-Version: 1.0 Received: by 10.31.55.198 with HTTP; Sun, 6 Aug 2017 21:32:40 -0700 (PDT) In-Reply-To: References: <9C14A21D-1C17-44F9-882B-4A01C311E164@FreeBSD.org> <37395FD6-09E5-4C11-A189-7B3050E9A541@FreeBSD.org> From: Aijaz Baig Date: Mon, 7 Aug 2017 10:02:40 +0530 Message-ID: Subject: Re: buildworld fails while building static clang library To: Ed Maste Cc: Dimitry Andric , FreeBSD Current Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 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: Mon, 07 Aug 2017 04:32:42 -0000 That was some pretty relevant information Ed. Thanks. However upon bumping up my RAM, I don't hit this error anymore perhaps I believe since the relatively large amount of RAM does not necessitate that much of swap space. Nonetheless, as I have indicated in my previous email, I hit an error quite late in the process now (stage 4.3) when it is apparently linking h_raw.o into h_raw.full ( is this linking by the way? what is the .full file there??) Keen to hear On Sun, Aug 6, 2017 at 3:04 PM, Ed Maste wrote: > On 5 August 2017 at 16:16, Dimitry Andric wrote: > > > > I remember there being an issue with ar and/or ranlib choking when the > > .a files become too big. Ed, does that ring any bells? > > Our ar (and ranlib, which is the same binary) will produce a corrupt > symbol table if the .a archive output is larger than 4GB, because we > support only 32-bit offsets in the older "/" symbol table format, not > the "/SYM64/" format and 64-bit offsets. > > As with GNU ar from binutils 2.17.50 we silently truncate if the > offset does not fit in 32 bits. I'll have a patch for review soon to > exit on error rather than produce corrupted output, and hope to look > at adding /SYM64/ support later on. > -- Best Regards, Aijaz Baig