From owner-freebsd-ports@freebsd.org Sat Mar 5 20:22:34 2016 Return-Path: Delivered-To: freebsd-ports@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 37713A097FE for ; Sat, 5 Mar 2016 20:22:34 +0000 (UTC) (envelope-from kubito@gmail.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 174C7107 for ; Sat, 5 Mar 2016 20:22:34 +0000 (UTC) (envelope-from kubito@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id 11D35A097FD; Sat, 5 Mar 2016 20:22:34 +0000 (UTC) Delivered-To: ports@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 1161AA097FC for ; Sat, 5 Mar 2016 20:22:34 +0000 (UTC) (envelope-from kubito@gmail.com) Received: from mail-wm0-x233.google.com (mail-wm0-x233.google.com [IPv6:2a00:1450:400c:c09::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 9E6CD106 for ; Sat, 5 Mar 2016 20:22:33 +0000 (UTC) (envelope-from kubito@gmail.com) Received: by mail-wm0-x233.google.com with SMTP id p65so61059070wmp.1 for ; Sat, 05 Mar 2016 12:22:33 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:from:to:cc:subject:references:date:in-reply-to:message-id :user-agent:mime-version:content-transfer-encoding; bh=PqUlCkYqAmkCYKszjgHcHoMGjQUwf3GLuBMYVWfeN1Y=; b=CkC76xvvRZdVlAFq6hbk8USa8XtwzFZ+M80jwiLLYmHTe2ds77PM5IQrK31IXCFjp4 S61VD0O0KG9uq3LhZ40klRg6W2sx7ywq5dx/dj4LzB5uQfJ8IcY2+OhX+8b5z2gsxFEH 5OZQ1jwXjB3TwfQU+/UM33/ztlnMpBxd+pwbbz2JXYhbL1cFNyJmjto/XFwlql24jMV1 LDba6f/D9IDjgBRoD4q2sMb/Yq6a4sZcS6/9sHnNrhzyZ3MrRMv8yceETiUq2UUUCCLG 0Y6CCXL2Expk6OSzqW2kx6h/Ewp5hhvIb+49OJrgSzr/RYl9pVYUypVrI88ynglYiHeh sn9A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:sender:from:to:cc:subject:references:date :in-reply-to:message-id:user-agent:mime-version :content-transfer-encoding; bh=PqUlCkYqAmkCYKszjgHcHoMGjQUwf3GLuBMYVWfeN1Y=; b=TUNU+c6QSdsOrlFouFtDSFI+wUE8ejX/8gWXdI7DMivEajOVaAw2UT37+gUbR2FtrT ug5111pZfWTEu8VRd7HASkt7MuQJlrKC2UrLAPZhVcdwvuiMgiGDB7xPOyCzSUd7y/MR N+TX26aOhlqDTPpstgh4G6Ynu3N4B0e1PPp1nkpGj7nBMPhHSIsdJQnHi7WcLOdOe0I/ VUk67tQE78fQO3ASBxJJs5zuiosuQR5Ah2wB7qKoh5U288WIE6mYsoskYY0nEY7aHXEr MwXA2TEtxXRQXb3Id90zF3gzt4QCwynuUYK6htJo65TxCjdHtngt4guakCHwEIaNK/OG 0N/Q== X-Gm-Message-State: AD7BkJJUNlOR5si8MTr8rre68vMBR8EbDKeRdHQAa6MOkW6xf980dNGCKCl9ur7kDj3Bsg== X-Received: by 10.28.87.65 with SMTP id l62mr5374347wmb.102.1457209352076; Sat, 05 Mar 2016 12:22:32 -0800 (PST) Received: from orwell.gmail.com (dhcp-077-248-147-050.chello.nl. [77.248.147.50]) by smtp.gmail.com with ESMTPSA id w136sm5401725wmw.0.2016.03.05.12.22.31 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 05 Mar 2016 12:22:31 -0800 (PST) Sender: Raphael Kubo da Costa From: Raphael Kubo da Costa To: Andrew Reilly Cc: ports@freebsd.org Subject: Re: openblas 0.2.15,1 port broke build for BARCELONA AMD core References: <7251C627-A9CC-49F8-A12D-1412D77493EF@bigpond.net.au> Date: Sat, 05 Mar 2016 21:22:21 +0100 In-Reply-To: <7251C627-A9CC-49F8-A12D-1412D77493EF@bigpond.net.au> (Andrew Reilly's message of "Sat, 27 Feb 2016 12:30:33 +1100") Message-ID: <86d1r87k02.fsf@FreeBSD.org> User-Agent: Gnus/5.130016 (Ma Gnus v0.16) Emacs/24.5 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Mar 2016 20:22:34 -0000 Andrew Reilly writes: > Hi there, > > My portmsaster run just broke on the recent openblas upgrade, with version > stamp in head/math/openblas/Makefile 409114 26-02-18 16:35:48Z rakuco. No= w that > I=E2=80=99ve hacked on this to make it build, I remember having done some= thing like > this the last time, so perhaps nothing has actually changed in this respe= ct, > there=E2=80=99s just been a version increase that still doesn=E2=80=99t k= now about my CPU. > > My build/target machine is, according to sysctl: > hw.machine: amd64 > hw.model: AMD A6-3500 APU with Radeon(tm) HD Graphics > hw.ncpu: 3 > > The auto-config system for openblas has determined that this is (in confi= g.h): > #define AMD_UNKNOWN > but also > #define CORE_BARCELONA > #define CHAR_CORENAME =E2=80=9CBARCELONA=E2=80=9D > > So on the assumption that the AMD_UNKNOWN should be BARCELONA, I have twe= aked > cpuid_x86.c to add case 3 along with case 1 and case 10 in the switch(exf= amily) > to return CPUTYPE_BARCELONA. > > I=E2=80=99m not sure if it wouldn=E2=80=99t have been better to slide tha= t in with case 6, > because model=3D1 and support_avx()->0, so that would have worked too. > > the full set of get_cputype() values for my machine are: > family=3D0xf, exfamily=3D0x3, model=3D0x1, exmodel=3D0x0, support_avx=3D0 > > The code in cpuid_x86.c thinks that NUM_CORES is 1, despite the sysctl > information above, so I guess that only one core is going to be used, but= since > this is not a high performance machine and is generally thermally challen= ged, > I=E2=80=99m not too concerned about that. Just want it to build at all. > > With this couple of tweaks the math/openblas port seems to have built OK,= so I > hope that this change can be included in the port or the up-stream so tha= t I > don=E2=80=99t have to remember to do this all again next time! Hi Andrew, I don't maintain the openblas port, I just committed a patch for it that was sent to Bugzilla. This looks like a problem that should be reported upstream (https://github.com/xianyi/OpenBLAS/issues), it's even possible it's already been fixed in their git repository. You can also file a bug in our bug tracker so the port maintainer can take a look at this, but I don't think there's much he can do besides relaying that information upstream.