From owner-freebsd-ports@FreeBSD.ORG Sun Nov 8 01:47:24 2009 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 951B6106566B for ; Sun, 8 Nov 2009 01:47:24 +0000 (UTC) (envelope-from alexanderchuranov@gmail.com) Received: from mail-bw0-f213.google.com (mail-bw0-f213.google.com [209.85.218.213]) by mx1.freebsd.org (Postfix) with ESMTP id 29DBA8FC1B for ; Sun, 8 Nov 2009 01:47:23 +0000 (UTC) Received: by bwz5 with SMTP id 5so2457133bwz.3 for ; Sat, 07 Nov 2009 17:47:23 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=+fiuffrJ9jQn1K+08bybxw/oZzYMCusIPT2uh36tf1k=; b=L50Om5dnxU0B6mKwnEkdKh3ikXJYvGECXCpfTOWXpLDzd3dBuCa8/Ez3hIRIuJXyHR Bmk7yUFSWm11uXFn9YEIy53uyxGC8Fan1szBQvCWssbBNY5zE3yI3xovimU8uGt3a2MV Lx2WMl6rH4cOhN1hvQdVzMix34Mn1+FPgnLJ0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=oJvLrFYfwqw7lHICNXAYvRYi2YrO2p287vRbB3gTkrExbB0scQ9+HeFD03siyvys7O omUmXENRUamAqcSdlba+VFjy0oxLQHY9+1R6rbC9KMsSQ1eO88sLcXorfF28tD2XVnJx Reh6ir8OdxrGqatxlReF7eZ+ZSzEdWOAREB3g= MIME-Version: 1.0 Received: by 10.204.150.66 with SMTP id x2mr1658086bkv.9.1257644843139; Sat, 07 Nov 2009 17:47:23 -0800 (PST) Date: Sun, 8 Nov 2009 04:47:23 +0300 Message-ID: <3cb459ed0911071747y11e5ace3gca92c9814a11d139@mail.gmail.com> From: Alexander Churanov To: ports@freebsd.org, Mark Linimon Content-Type: text/plain; charset=ISO-8859-1 Cc: Subject: Issues with devel/boost-* on Sparc64 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Nov 2009 01:47:24 -0000 HI folks! As I know, currently devel/boost-libs port fails to build on sparc64. I had a discussion of this in September. The root cause is unknown for me. To investigate into this further I need either access to a sparc64 box or a person who has access and whom I may instruct with the actions to perform. Are there any plans to fix ports for sparc64 before the release? Sincerely, Alexander Churanov, maintainer of devel/boost-*