From owner-freebsd-current@freebsd.org Fri Jan 20 08:39:08 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 9C766CB8070 for ; Fri, 20 Jan 2017 08:39:08 +0000 (UTC) (envelope-from andrnils@gmail.com) Received: from mail-vk0-x22e.google.com (mail-vk0-x22e.google.com [IPv6:2607:f8b0:400c:c05::22e]) (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 53B531547; Fri, 20 Jan 2017 08:39:08 +0000 (UTC) (envelope-from andrnils@gmail.com) Received: by mail-vk0-x22e.google.com with SMTP id r136so47287484vke.1; Fri, 20 Jan 2017 00:39:08 -0800 (PST) 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=3/GixdTaxozaYwMISw2UMMdynfQxhJRsUiWSaezW7FY=; b=gBGSaOIE3pTH9g7NLqK8hh9SqG4E6RiXFhAiZlOFYm5j3QQtxYZJSv07uy4IjC95Fr 4LK6IjF14ICDln7BcdtIzuUaJtAjbj0M/TOkMBxELYSXp9pE/jPw3G+brNhV05EF1J3M OsSJYht50DAe0rnQSUDUNuJiu3v0iVp4wuPPHKjBj1t43Y6YNRSZGCGJ71gS7Qau1O8u JaqHYtPZ0nfnanTT3UEpgV4oWLM/WZbzL4/gOhuuiQ3AM0ZjrT0FQOohmSfvLYho9s1C 8ko3j7U4xjQhmGhi/QstlHLprBQEvWzSR9On5WojWcbnHbXMNQbJs23eQLFF0ZO6pD07 A6ng== 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=3/GixdTaxozaYwMISw2UMMdynfQxhJRsUiWSaezW7FY=; b=G3MRb+qbuhmBxPrvDdluOd/IijGcLH9dvE98vAzjR0rlPCI+Jhlj6vXE4OHAWDP6Iq 4oCdXsV0qm6HnJMCB8Pt2W2XG1Kllnt7bGCpomBCeAdO83w5PEN0Fi8/DYPLE6n7jcrV PYC1gfRB5qEMh2FuEDAe3FLpO1F5QLJuNwK25Fd4o1ulJoQ97v+3yv6ykT4ot0e6yMf7 mNd0963yNyoqGzosCeVb9/Ni0mf0V+Du9SfParW0lebuKhZoiCmb4OCucpy2UozNP8On pSFPMv6yx0oAEKPY+zdsgwebbp+sHZeRCdN3fTEayZExKMNkFRa+6KBlrO7QOusYLXM/ jVFA== X-Gm-Message-State: AIkVDXIrWLnVxQZAQM+xezz+G27xDp9qb6tsCWKNoQWnDthZeY/U0x5bCLSiGjIIRKwUx3+E6Z38n1KHvAqB8w== X-Received: by 10.31.94.204 with SMTP id s195mr6725684vkb.76.1484901547383; Fri, 20 Jan 2017 00:39:07 -0800 (PST) MIME-Version: 1.0 Received: by 10.176.5.200 with HTTP; Fri, 20 Jan 2017 00:39:06 -0800 (PST) In-Reply-To: <20170119195843.GI1451@FreeBSD.org> References: <20170118101915.523d7d7b@freyja.zeit4.iv.bundesimmobilien.de> <20170118123515.GE58505@zxy.spb.ru> <20170118160801.229b4134@freyja.zeit4.iv.bundesimmobilien.de> <20170118153832.GA6905@c720-r292778-amd64> <20170118203726.7dea0515@thor.intern.walstatt.dynvpn.de> <20170119055816.GA2184@c720-r292778-amd64> <20170119101636.5537f4fd@freyja.zeit4.iv.bundesimmobilien.de> <20170119191000.GG1451@FreeBSD.org> <20170119195843.GI1451@FreeBSD.org> From: Andreas Nilsson Date: Fri, 20 Jan 2017 09:39:06 +0100 Message-ID: Subject: Re: ISO image: where is the CLANG compiler? To: Glen Barber Cc: "O. Hartmann" , Matthias Apitz , Current FreeBSD 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: Fri, 20 Jan 2017 08:39:08 -0000 On Thu, Jan 19, 2017 at 8:58 PM, Glen Barber wrote: > On Thu, Jan 19, 2017 at 08:50:34PM +0100, Andreas Nilsson wrote: > > On Thu, Jan 19, 2017 at 8:10 PM, Glen Barber wrote: > > > I do want to weigh in here and inform I am actively watching this > > > thread. clang(1) is not in disc1.iso or bootonly.iso because the > > > MK_TOOLCHAIN knob is disabled in the targets that generate them. This > > > has actually been the case for quite some time for these images. > > > > > > dvd1.iso does contain clang, but very rarely (if ever, actually) are > > > there dvd1.iso images produced for development snapshots. This is, in > > > part, solely because of the additional space/bandwidth required on the > > > mirrors (not just mirrors controlled by the Project, but third-party > > > mirrors as well). > > > > > > I am working on splitting out how the memstick.img and disc1.iso images > > > are produced, but ran into a problem which I'm looking into a > workaround > > > that is backwards-compatible. Since for USB images, a 700MB limit does > > > not make sense, and right now it just so happens that the memstick.img > > > is created from the same contents of disc1.iso. > > > > > > I know this does not help with the immediate issue, but wanted to chime > > > in with I do see and understand the larger issue, and am working on > > > a more long-term resolution instead of a one-line workaround. > > > > > > > > Good to see discussion, but my 5c is: do not enlarge regular install > media, > > it is hefty enough. I'd rather see it shrink, although without the > > limitations of old cd's rescue-env. > > > > Install media is install media, not live image. Live usb-sticks are so > easy > > to do on your own, why waste the Projects storage and bandwidth on it? > > > > For cases like what initiated this thread, actually. But, I'm not > looking to increase the disc1.iso size, but separate the disc1.iso and > memstick.img targets, which then can be created from different userland > environments (one with /usr/bin/clang and one without, for example). > > But, I do agree with you that keeping the downloadable installer medium > as small as possible (while still being usable for "rescue" cases like > this) is ideal. > > Glen > > Good good. I am in no way opposed to the "infrastructure" change of separating the targets, sounds like a bit of makefile-fun actually. And having tools to create memsticks from ones preferred environment would be sweet. Maybe someone could add a target in the makefiles for a rescue image, which basically would be the complete FreeBSD system one would get after untaring base, kernel and src? Best regards Andreas