From owner-freebsd-hackers@freebsd.org Tue Aug 11 07:02:06 2015 Return-Path: Delivered-To: freebsd-hackers@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 F3F9D99E1BA for ; Tue, 11 Aug 2015 07:02:05 +0000 (UTC) (envelope-from dieterbsd@gmail.com) Received: from mail-ig0-x233.google.com (mail-ig0-x233.google.com [IPv6:2607:f8b0:4001:c05::233]) (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 C187E1FFF for ; Tue, 11 Aug 2015 07:02:05 +0000 (UTC) (envelope-from dieterbsd@gmail.com) Received: by igbpg9 with SMTP id pg9so85065183igb.0 for ; Tue, 11 Aug 2015 00:02:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=A1h4bUa47qvmptVa5/E2mgeNwoy+U8ymmSqK2NZdSJ8=; b=q/LWmmD0MOnL/Z6OtNedG6vmaWUpzanx0p1itKtiq2IcGqog2Kb+EU1ZOMx0sAnfaF tNsWdU9hXryRmVCpC9lMfgxJ+UCM44fxDLtA4YE3fe7a+hTij1uvpjz7V2CHHRIE/+3V AWke6WBlbYgmAkGJ6gYSXYDu+ENMRg6Mb0gF40uElWmQYBVtQk5EPS9BzSwpbb5q8//I Y4+mlnwVf8Uhak1oN8H/zNkrQF+Ih7R4K6dBJ0SbffcRGECoGnFs0L/ovn/samr0VcYz cmrQbJY13S0zuRKMliQM6eNmvZDM+8ngLiPhk9vzBKR6RcB9TOn+HvDn+YxhyMg+CQeN CErA== MIME-Version: 1.0 X-Received: by 10.50.79.197 with SMTP id l5mr15213102igx.67.1439276524859; Tue, 11 Aug 2015 00:02:04 -0700 (PDT) Received: by 10.64.2.132 with HTTP; Tue, 11 Aug 2015 00:02:04 -0700 (PDT) Date: Tue, 11 Aug 2015 00:02:04 -0700 Message-ID: Subject: Re: Sparc64 support From: Dieter BSD To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Aug 2015 07:02:06 -0000 Jordan: >take this opportunity to clean things up with the build process Tim: > If someone would chime in on this thread with the actual [deleted] > make [deleted] incantations that should work for each architecture, > you might find some volunteers. I keep seeing the same issues over and over. Cross builds don't work. Some people hate gcc for whatever reason and insist on ripping it out in hopes that someone will wave their magic wand and make some other compiler take over. Sort of like injuring a bunch of people in hopes that someone will improve emergency rooms. Oh, if only we could add this special feature in base then we could use it in lots of ports without having another dependency. NASA_BSD got the cross-arch cross-OS building stuff working *years* ago. Is there some valid reason that FreeBSD can't do it the same way? NIH is not a valid reason. There seems to be an assumption that all arches have to use the same toolchain. That's just silly. Build arches A & B with gcc, arches C & D with klang, arch E with pcc, arch F with Sally-Jo's code-cruncher, and so one. And go a step further. The 'base' compiler can be different for different arches. Probably easier if the toolchain is separate from the 'base' package. (like NASA_BSD did it) Lots of ports have *way* too many dependencies. Adding yet another is bad, but probably isn't going to kill us. Adding a bunch of garbage to base is worse. I see a lot of hatred towards the less popular, "weird" arches. Having a variety of arches has a *lot* of value. Jordan: > I have a lab (several actually). I have engineers. How can we help. In addition to the suggestions above, there are open PRs that need fixing.