From owner-freebsd-ppc@freebsd.org Sun Apr 23 01:54:38 2017 Return-Path: Delivered-To: freebsd-ppc@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 B68D7D40A85; Sun, 23 Apr 2017 01:54:38 +0000 (UTC) (envelope-from jaguar.darocha@yandex.com) Received: from forward8j.cmail.yandex.net (forward8j.cmail.yandex.net [IPv6:2a02:6b8:0:1630::183]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "forwards.mail.yandex.net", Issuer "Yandex CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3D5BB29A; Sun, 23 Apr 2017 01:54:37 +0000 (UTC) (envelope-from jaguar.darocha@yandex.com) Received: from mxback13j.mail.yandex.net (mxback13j.mail.yandex.net [IPv6:2a02:6b8:0:1619::88]) by forward8j.cmail.yandex.net (Yandex) with ESMTP id 2131121F26; Sun, 23 Apr 2017 04:54:34 +0300 (MSK) Received: from web27o.yandex.ru (web27o.yandex.ru [95.108.205.127]) by mxback13j.mail.yandex.net (nwsmtp/Yandex) with ESMTP id v75AW9WLMi-sXemsxMS; Sun, 23 Apr 2017 04:54:33 +0300 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.com; s=mail; t=1492912473; bh=oi0GOsHZnHkIJaWZpwnrYDx+U3Lmy0PQ5qBwYkAw2Ts=; h=From:To:Cc:In-Reply-To:References:Subject:Message-Id:Date; b=NzwzF7q9rwnBsWuLK69IkVhnhisb7O2YF71N/6VJ/NTkLKiJ6BfDdHFJdWAd08I2d bHp+f9zbBNDk3lbok66EgqSFdfYV3Gk5NydJlX7fgUWY5Y0kGQi9cuLmlWdpmu7Rl/ XcvOolaI/o8Cs/NJ4iQ0qSqhMsVt9uEO30B98u4U= Authentication-Results: mxback13j.mail.yandex.net; dkim=pass header.i=@yandex.com Received: by web27o.yandex.ru with HTTP; Sun, 23 Apr 2017 04:54:33 +0300 From: Jaguar DaRocha Envelope-From: jaguar-darocha@yandex.com To: Ben Goren , Joe Nosay , "baptiste.daroussin@gmail.com" Cc: "ppc@openbsd.org" , FreeBSD PowerPC ML , "advocacy@freebsd.org" , "advocacy@openbsd.org" In-Reply-To: 161848111608627431 References: <30331.1492386038@cvs.openbsd.org> <46960885-A4AB-4095-9A40-C06035A8A493@trumpetpower.com> Subject: Re: powerpc packages? Message-Id: <5903021492912473@web27o.yandex.ru> X-Mailer: Yamail [ http://yandex.ru ] 5.0 Date: Sat, 22 Apr 2017 19:54:33 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Apr 2017 01:54:38 -0000 From owner-freebsd-ppc@freebsd.org Sun Apr 23 18:02:36 2017 Return-Path: Delivered-To: freebsd-ppc@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 7AAEFD4D218 for ; Sun, 23 Apr 2017 18:02:36 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4FE4768F for ; Sun, 23 Apr 2017 18:02:36 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by freefall.freebsd.org (Postfix) id 7CDAD3F1A; Sun, 23 Apr 2017 18:02:35 +0000 (UTC) Delivered-To: freebsd-powerpc@localmail.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mx1.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by freefall.freebsd.org (Postfix) with ESMTPS id 694DD3F18 for ; Sun, 23 Apr 2017 18:02:35 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id AD63168B for ; Sun, 23 Apr 2017 18:02:34 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v3NI2YIw014013 for ; Sun, 23 Apr 2017 18:02:34 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-powerpc@FreeBSD.org Subject: [Bug 217215] graphics/argyllcms broken on powerpc64 Date: Sun, 23 Apr 2017 18:02:34 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: jbeich@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: kwm@FreeBSD.org X-Bugzilla-Flags: maintainer-feedback? X-Bugzilla-Changed-Fields: attachments.mimetype attachments.ispatch Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Apr 2017 18:02:36 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D217215 Jan Beich changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #180129|text/x-chdr |text/plain mime type| | Attachment #180129|0 |1 is patch| | --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-ppc@freebsd.org Wed Apr 26 16:22:32 2017 Return-Path: Delivered-To: freebsd-ppc@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 9C1C0D51369 for ; Wed, 26 Apr 2017 16:22:32 +0000 (UTC) (envelope-from david.smith@cs-reports.com) Received: from mailer57.gate93.rs.smtp.com (mailer57.gate93.rs.smtp.com [74.91.93.57]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 5816B1E46 for ; Wed, 26 Apr 2017 16:22:32 +0000 (UTC) (envelope-from david.smith@cs-reports.com) X-MSFBL: 7P6QaiPdfUPS+KVHGKeO6svrYJ7coi+VnuAIfbXlZ1k=|eyJyIjoiZnJlZWJzZC1 wcGNAZnJlZWJzZC5vcmciLCJiIjoiNzRfOTFfOTNfNTciLCJnIjoiQ29tbW9kaXR 5SW5zaWRlX2RlZGljYXRlZF9wb29sIn0= Received: from [192.168.80.22] ([192.168.80.22:56402] helo=rs-ord-mta02-in2.smtp.com) by rs-ord-mta02-out1.smtp.com (envelope-from ) (ecelerity 4.2.1.55028 r(Core:4.2.1.12)) with ESMTP id 52/5B-06480-284C0095; Wed, 26 Apr 2017 16:02:10 +0000 DKIM-Signature: v=1; a=rsa-sha256; d=smtpserver.email; s=smtpcustomer; c=relaxed/simple; q=dns/txt; i=@smtpserver.email; t=1493222530; h=From:Subject:To:Date:MIME-Version:Content-Type; bh=D1rL3FiteQjqQ0ER/Qw5owqYYjhM4qxmVIXIkdpwG2s=; b=qKdxnofaTbJfT9plwqseinFUikW84Qt6ld23Q1y36KgO80M67/e4ozbExdMOId7q 0WYwTw3ryg3G8X4hInSBoiAuACkQB8oPDgZ5KQIxZPO4OMTZXIdaDPxfD2jwMrec 5KBffmgXwGjnZX+gbUjohxML/0sv4jgrJ2oWpSnoMnUKtELiRduWlX7hHKyPfPjg DktPx7P7ND0qGMSNO7DDLtGK3YCMi+6vuJ3qvfmYFI2ofTZi2LlgQhF885p0Aelt 2DoeItCDL81rolRiAtHEo/kpjI7fKCSNYvppOI7Xl3r3s8NwrJI3jQVazPPi21/O YIBnMllow8Ss9C3PJtyHkQ==; Received: from [86.4.116.225] ([86.4.116.225:36912] helo=cpc90280-cove16-2-0-cust224.3-1.cable.virginm.net) by rs-ord-mta02-in2.smtp.com (envelope-from ) (ecelerity 4.1.0.46749 r(Core:4.1.0.4)) with ESMTPA id CA/7D-26331-284C0095; Wed, 26 Apr 2017 16:02:10 +0000 MIME-Version: 1.0 From: "David Smith" Reply-To: david.smith@cs-reports.com To: freebsd-ppc@freebsd.org Subject: Global Automotive Cyber Security Market outlook to 2027 X-Mailer: Smart_Send_2_0_138 Date: Wed, 26 Apr 2017 17:02:08 +0100 Message-ID: <85803751366162842316572@Saket> X-Report-Abuse: SMTP.com is an email service provider. Our abuse team cares about your feedback. Please contact abuse@smtp.com for further investigation. X-SMTPCOM-Tracking-Number: ad4bc587-ac86-4c05-bd92-9a3690157be3 X-SMTPCOM-Sender-ID: 5012537 Feedback-ID: 5012537:SMTPCOM Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Apr 2017 16:22:32 -0000 Global Automotive Cyber Security Market outlook to 2027 (Report) =20 Report Information: Release Date: March 2017 Number of Pages/Slides: 95 Tables and Figures: 45 Report Overview: The automotive sector will see significant changes over the next ten years = where connectivity will be one of the pivotal attributes changing the face = of the sector. With the rise in connected cars, the level of automation wil= l also grow in tandem. Connectivity will become a norm and provide renewed = growth to the automotive sector, though at the same time it will make vehic= les vulnerable to cyber attacks. Vehicles are increasingly becoming vulnerable to hacking as they are intera= cting with others vehicles and devices. Consequently, this has opened new v= enues for cyber security companies, and they are penetrating quite rapidly = in the automotive market. Hacking a vehicle can stake human lives as well a= s brand reputations. One of the prominent examples was Fiat Chrysler when i= t recalled 1.4 million vehicles in 2015 after its Jeep was hacked remotely = through the entertainment system. The global automotive cyber security market is expected to see robust growt= h over the next ten years. Some of the major drivers behind the growth will= be stringent security and safety regulations, increased demand for connect= ivity and development of autonomous vehicles. Meanwhile, growth is likely t= o shift from the US to China. Commodity Inside understands that demand for automotive cyber security is a= t its nascent stage and has an enormous growth potential. The automotive cy= ber security technology will enhance existing security features and help de= veloping new secure solutions. Automakers are planning to introduce fully a= utonomous vehicles by 2021, which will take the demand for automotive cyber= security to the zenith. We expect high M&A activity and emergence of new c= yber security companies in the market. In the meantime, the expected high growth and rising adoption of autonomous= vehicle technologies have also opened new opportunities for high-tech comp= anies. Intel has recently acquired Mobileye, an automotive advanced driver = assistance and collision avoidance technology company. Both have already be= en collaborating with BMW on driverless cars. The acquisition shows Intel= =92s plans for the automotive sector, particularly autonomous vehicles. Int= el has already penetrated into the automotive cyber security through the ac= quisition of McAfee in 2011. Why this report is unique, and a must read for the automotive cyber securit= y and automotive industry as a whole=3F Global Automotive Cyber Security Market out to 2027 is a valuable resource = necessary for examining the global automotive cyber security market. We hav= e employed a very sophisticated and robust approach to assessing the automo= tive market by taking into account various demand and supply dynamics as we= ll as technological developments. The report covers the following key aspec= ts: How will the automotive cyber security market perform over the next ten yea= rs=3F What will be the major factors driving the automotive cyber security market= and how they will impact the industry=3F How will the increasing use of communications and safety technology benefit= the automotive cyber security industry=3F Detailed analysis of the current status of automotive cyber security and te= chnology developers. What will be the major drivers for each type of security and vehicle type a= nd what will be their implications=3F Ten-year projections for ADAS markets and sensor shipments. The current and future demand dynamics for vehicles with different levels o= f automation. Detailed discussion on competitive landscapes and product offerings. Analysis of the present and future performance of matured and developing ma= rkets. Detailed analysis and forecasts of major markets in terms of supplying cybe= r security solutions. Why should you read this report=3F Global Automotive Cyber Security Market out to 2027 provides you with the f= ollowing in-depth analysis: The automotive cyber security market is analysed by security segments and b= y vehicle type. Discussion on the main drivers and restraints of the market and major geogr= aphy. The full coverage of automotive cyber security market in terms of sales val= ue. Coverage of the main countries which are providing cyber security solutions. Market projections for ADAS market, sensor shipments and vehicle sales by t= he level of automation. 45 tables, figures and charts All supportive data provided in Excel Who should buy this report=3F Conventional car manufacturers Electric vehicle manufacturers Hybrid and plug-in hybrid vehicles manufacturers Component manufacturers Suppliers of materials to automotive Automotive technology vendors Software and cyber security companies Mobile network operators Smartphone manufacturers Mobility service providers Utility companies Financial institutions Industry consultants, researchers and analysts Government bodies. Why our analyses are robust and authoritative=3F We constantly consult industry experts and incorporate their views in our a= nalysis.=20 We employ both quantitative and qualitative methods to derive robust analys= is.=20 All our forecast data were also supported by our proprietary econometric an= d excel based models.=20 We are completely independent and represent our own views. =20 Table of Contents Chapter 1- Executive Summary 1.1 Developments in the automotive cyber security 1.2 Methodology Chapter 2 =96 Market Structure 2.1 General overview 2.2 Vehicles automation 2.3 Cybersecurity markets by demand side Chapter 3 =96 Automotive Cyber Security Market by Segments 3.1 Automotive cyber security market by security type 3.1.1 Hardware security 3.1.2 Software security 3.1.3 Network security 3.1.4 Cloud security 3.2 Automotive cyber security market by vehicle type 3.2.1 Passenger car 3.2.2 Commercial vehicle Chapter 4 =96 Key automotive Cyber Security Markets by Supply Side 4.1 China 4.2 France 4.3 Germany 4.4 Israel 4.5 Japan 4.6 Russia 4.7 South Korea 4.8 UK 4.9 US Chapter 5 =96 Competitive Landscape 5.1 Argus 5.2 Cisco 5.3 Harman 5.4 IBM 5.5 Infineon 5.6 Intel 5.7 NXP 5.8 Symantec 5.9 Trillium List of Tables: Table 1.1 Global automotive cyber security market by security type 2016-202= 7 ($ millions, %) Table 1.2 Global passenger car and commercial vehicle cyber security market= 2016-2027 ($ millions) Table 2.1 List of hackable cars by manufacturer, model and year make 2006-2= 016 Table 2.2 ADAS sensors shipment 2017-2027 (million units) Table 2.3 Security content by level of automation ($) Table 2.4 Autonomous vehicle R&D spending by top players in 2016 ($ million= s) Table 2.5 Global automotive cyber security demand side market by regions Table 2.6 Expected Vehicle automation level introduction by major OEMs Table 3.1 Global hardware security market 2016-2027 ($ millions, %) Table 3.2 Global software security market 2016-2027 ($ millions, %) Table 3.3 Global network security market 2016-2027 ($ millions, %) Table 3.4 Global cloud security market 2016-2027 ($ millions, %) Table 3.5 Global passenger car and commercial vehicle cyber security market= 2016-2027 ($ millions) Table 4.1 Chinese automotive cyber security supply-side market 2016-2027 ($= millions, %) Table 4.2 French automotive cyber security supply-side market 2016-2027 ($ = millions, %) Table 4.3 German automotive cyber security supply-side market 2016-2027 ($ = millions, %) Table 4.4 Israeli automotive cyber security supply-side market 2016-2027 ($= millions, %) Table 4.5 Japanese automotive cyber security supply-side market 2016-2027 (= $ millions, %) Table 4.6 Russian automotive cyber security supply-side market 2016-2027 ($= millions, %) Table 4.7 South Korean automotive cyber security supply-side market 2016-20= 27 ($ millions, %) Table 4.8 UK automotive cyber security supply-side market 2016-2027 ($ mill= ions, %) Table 4.9 US automotive cyber security supply-side market 2016-2027 ($ mill= ions, %) =20 List of Figures: Figure 1.1 Global automotive cyber security market by security type 2016-20= 27 ($ millions, %) Figure 1.2 Global passenger car and commercial vehicle cyber security marke= t 2016-2022 ($ millions) Figure 2.1 Global ADAS revenue by application 2017-2027 ($ billions) Figure 2.2 Vehicle sales by level of automation 2015-2027 (%) Figure 2.3 Global automotive cyber security demand side market by regions Figure 3.1 Global hardware security market 2016-2027 ($ millions) Figure 3.2 Global software security market 2016-2027 ($ millions) Figure 3.3 Global network security market 2016-2027 ($ millions) Figure 3.4 Global cloud security market 2016-2027 ($ millions) Figure 3.5 Global passenger car and commercial vehicle cyber security marke= t 2016-2027 ($ millions) Figure 4.1 Chinese automotive cyber security supply-side market 2016-2027 (= $ millions) Figure 4.2 French automotive cyber security supply-side market 2016-2027 ($= millions) Figure 4.3 German automotive cyber security supply-side market 2016-2027 ($= millions) Figure 4.4 Israeli automotive cyber security supply-side market 2016-2027 (= $ millions) Figure 4.5 Japanese automotive cyber security supply-side market 2016-2027 = ($ millions) Figure 4.6 Russian automotive cyber security supply-side market 2016-2027 (= $ millions) Figure 4.7 South Korean automotive cyber security supply-side market 2016-2= 027 ($ millions) Figure 4.8 UK automotive cyber security supply-side market 2016-2027 ($ mil= lions) Figure 4.9 US automotive cyber security supply-side market 2016-2027 ($ mil= lions) =20 List of charts: Chart 1.1 Upside and downside risks in automotive cyber security market Chart 2.1 Mechanisms of cyber attacks Chart 2.2 Connected car product portfolio breakdown by major OEM and connec= tivity type Chart 2.3 Automation level requirements =20 Report Pricing Single User License: =A31695 Departmental License (up to 5 Users): =A32995 Global License: =A34995 =20 Ordering process Please contact David Smith on david.smith@cioutlookreports.com And provide the following information: Report Title - Report License - (Single User/Departmental/Global) Name - Email - Job Title - Company - Invoice Address VAT number (EU Only) Please contact me if you have any questions, or wish to purchase a copy I look forward to hearing from you. Kind Regards David Smith Business Intelligence Executive To Unsubscribe send an email with Unsubscribe in the subject line to info@c= s-reports.com Remove From owner-freebsd-ppc@freebsd.org Fri Apr 28 11:01:12 2017 Return-Path: Delivered-To: freebsd-ppc@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 0A12AD53813 for ; Fri, 28 Apr 2017 11:01:12 +0000 (UTC) (envelope-from luciano@vespaperitivo.it) Received: from baobab.bilink.net (baobab.bilink.net [212.45.144.44]) by mx1.freebsd.org (Postfix) with ESMTP id AB977112A for ; Fri, 28 Apr 2017 11:01:11 +0000 (UTC) (envelope-from luciano@vespaperitivo.it) Received: from localhost (localhost [127.0.0.1]) by baobab.bilink.it (Postfix) with ESMTP id 3wDrGB02lPzRRrq for ; Fri, 28 Apr 2017 12:51:14 +0200 (CEST) X-Virus-Scanned: amavisd-new at mcs.it Received: from baobab.bilink.net ([127.0.0.1]) by localhost (baobab.mcs.it [127.0.0.1]) (amavisd-new, port 11027) with ESMTP id Dz5D0o-+apbc for ; Fri, 28 Apr 2017 12:51:13 +0200 (CEST) Received: from hermes.mcs.it (hermes.mcs.it [192.168.132.21]) by baobab.bilink.it (Postfix) with ESMTP id 3wDrG96NhDzRRrV for ; Fri, 28 Apr 2017 12:51:13 +0200 (CEST) Received: from mordeus (unknown [192.168.45.6]) by hermes.mcs.it (Postfix) with ESMTP id 999E91B7515 for ; Fri, 28 Apr 2017 12:51:12 +0200 (CEST) Date: Fri, 28 Apr 2017 12:51:12 +0200 From: Luciano Mannucci To: freebsd-ppc@freebsd.org Subject: llvm 4.0 on PPC64 X-Mailer: Claws Mail 3.14.1 (GTK+ 2.24.29; amd64-portbld-freebsd10.3) X-Face: 4qPv4GNcD; h<7Q/sK>+GqF4=CR@KmnPkSmwd+#%\F`4yjKO3"C]p'z=(oWRnsYBQGM\5g:4skqQY0NnV'dM:Mm:^/_+I@a"; [-s=ogufdF"9ggQ'=y MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Message-Id: <3wDrG96NhDzRRrV@baobab.bilink.it> X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Apr 2017 11:01:12 -0000 It seems it doesn't compile on 11.0-RELEASE-p1. Is it a known bug? I'm getting this from make install clean: /usr/ports/devel/llvm40/work/llvm-4.0.0.src/tools/lldb/source/Host/common/FileSpec.cpp: In function 'bool {anonymous}::GetFileStats(const lldb_private::FileSpec*, stat*)': /usr/ports/devel/llvm40/work/llvm-4.0.0.src/tools/lldb/source/Host/common/FileSpec.cpp:92:22: error: 'PATH_MAX' was not declared in this scope char resolved_path[PATH_MAX]; ^ /usr/ports/devel/llvm40/work/llvm-4.0.0.src/tools/lldb/source/Host/common/FileSpec.cpp:93:26: error: 'resolved_path' was not declared in this scope if (file_spec->GetPath(resolved_path, sizeof(resolved_path))) ^ /usr/ports/devel/llvm40/work/llvm-4.0.0.src/tools/lldb/source/Host/common/FileSpec.cpp: In member function 'bool lldb_private::FileSpec::ResolvePath()': /usr/ports/devel/llvm40/work/llvm-4.0.0.src/tools/lldb/source/Host/common/FileSpec.cpp:675:17: error: 'PATH_MAX' was not declared in this scope char path_buf[PATH_MAX]; ^ /usr/ports/devel/llvm40/work/llvm-4.0.0.src/tools/lldb/source/Host/common/FileSpec.cpp:676:16: error: 'path_buf' was not declared in this scope if (!GetPath(path_buf, PATH_MAX, false)) ^ /usr/ports/devel/llvm40/work/llvm-4.0.0.src/tools/lldb/source/Host/common/FileSpec.cpp:679:11: error: 'path_buf' was not declared in this scope SetFile(path_buf, true); ^ /usr/ports/devel/llvm40/work/llvm-4.0.0.src/tools/lldb/source/Host/common/FileSpec.cpp: In member function 'bool lldb_private::FileSpec::IsSymbolicLink() const': /usr/ports/devel/llvm40/work/llvm-4.0.0.src/tools/lldb/source/Host/common/FileSpec.cpp:718:22: error: 'PATH_MAX' was not declared in this scope char resolved_path[PATH_MAX]; ^ /usr/ports/devel/llvm40/work/llvm-4.0.0.src/tools/lldb/source/Host/common/FileSpec.cpp:719:16: error: 'resolved_path' was not declared in this scope if (!GetPath(resolved_path, sizeof(resolved_path))) ^ /usr/ports/devel/llvm40/work/llvm-4.0.0.src/tools/lldb/source/Host/common/FileSpec.cpp:733:15: error: 'resolved_path' was not declared in this scope if (::lstat(resolved_path, &file_stats) != 0) ^ /usr/ports/devel/llvm40/work/llvm-4.0.0.src/tools/lldb/source/Host/common/FileSpec.cpp: In member function 'size_t lldb_private::FileSpec::ReadFileContents(off_t, void*, size_t, lldb_private::Error*) const': /usr/ports/devel/llvm40/work/llvm-4.0.0.src/tools/lldb/source/Host/common/FileSpec.cpp:874:22: error: 'PATH_MAX' was not declared in this scope char resolved_path[PATH_MAX]; ^ /usr/ports/devel/llvm40/work/llvm-4.0.0.src/tools/lldb/source/Host/common/FileSpec.cpp:875:15: error: 'resolved_path' was not declared in this scope if (GetPath(resolved_path, sizeof(resolved_path))) { ^ /usr/ports/devel/llvm40/work/llvm-4.0.0.src/tools/lldb/source/Host/common/FileSpec.cpp: In member function 'lldb::DataBufferSP lldb_private::FileSpec::ReadFileContents(off_t, size_t, lldb_private::Error*) const': /usr/ports/devel/llvm40/work/llvm-4.0.0.src/tools/lldb/source/Host/common/FileSpec.cpp:906:22: error: 'PATH_MAX' was not declared in this scope char resolved_path[PATH_MAX]; ^ /usr/ports/devel/llvm40/work/llvm-4.0.0.src/tools/lldb/source/Host/common/FileSpec.cpp:907:15: error: 'resolved_path' was not declared in this scope if (GetPath(resolved_path, sizeof(resolved_path))) { ^ /usr/ports/devel/llvm40/work/llvm-4.0.0.src/tools/lldb/source/Host/common/FileSpec.cpp: In member function 'lldb::DataBufferSP lldb_private::FileSpec::ReadFileContentsAsCString(lldb_private::Error*)': /usr/ports/devel/llvm40/work/llvm-4.0.0.src/tools/lldb/source/Host/common/FileSpec.cpp:925:22: error: 'PATH_MAX' was not declared in this scope char resolved_path[PATH_MAX]; ^ /usr/ports/devel/llvm40/work/llvm-4.0.0.src/tools/lldb/source/Host/common/FileSpec.cpp:926:15: error: 'resolved_path' was not declared in this scope if (GetPath(resolved_path, sizeof(resolved_path))) { ^ /usr/ports/devel/llvm40/work/llvm-4.0.0.src/tools/lldb/source/Host/common/FileSpec.cpp: In member function 'size_t lldb_private::FileSpec::ReadFileLines(STLStringArray&)': /usr/ports/devel/llvm40/work/llvm-4.0.0.src/tools/lldb/source/Host/common/FileSpec.cpp:945:13: error: 'PATH_MAX' was not declared in this scope char path[PATH_MAX]; ^ /usr/ports/devel/llvm40/work/llvm-4.0.0.src/tools/lldb/source/Host/common/FileSpec.cpp:946:15: error: 'path' was not declared in this scope if (GetPath(path, sizeof(path))) { ^ /usr/ports/devel/llvm40/work/llvm-4.0.0.src/tools/lldb/source/Host/common/FileSpec.cpp:946:15: note: suggested alternative: In file included from /usr/ports/devel/llvm40/work/llvm-4.0.0.src/tools/lldb/source/Host/common/FileSpec.cpp:44:0: /usr/ports/devel/llvm40/work/llvm-4.0.0.src/include/llvm/Support/Path.h:25:16: note: 'llvm::sys::path' namespace path { ^ At global scope: cc1plus: warning: unrecognized command line option '-Wno-vla-extension' cc1plus: warning: unrecognized command line option '-Wno-deprecated-register' ninja: build stopped: subcommand failed. *** Error code 1 Stop. make[1]: stopped in /usr/ports/devel/llvm40 *** Error code 1 Stop. make: stopped in /usr/ports/devel/llvm40 Thanks to all, Luciano. -- /"\ /Via A. Salaino, 7 - 20144 Milano (Italy) \ / ASCII RIBBON CAMPAIGN / PHONE : +39 2 485781 FAX: +39 2 48578250 X AGAINST HTML MAIL / E-MAIL: posthamster@sublink.sublink.ORG / \ AND POSTINGS / WWW: http://www.lesassaie.IT/ From owner-freebsd-ppc@freebsd.org Fri Apr 28 14:27:26 2017 Return-Path: Delivered-To: freebsd-ppc@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 C0101D531D5 for ; Fri, 28 Apr 2017 14:27:26 +0000 (UTC) (envelope-from chmeeedalf@gmail.com) Received: from mail-qk0-x22b.google.com (mail-qk0-x22b.google.com [IPv6:2607:f8b0:400d:c09::22b]) (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 6F6831F2E for ; Fri, 28 Apr 2017 14:27:26 +0000 (UTC) (envelope-from chmeeedalf@gmail.com) Received: by mail-qk0-x22b.google.com with SMTP id f76so54110504qke.2 for ; Fri, 28 Apr 2017 07:27:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=6l09n3V8AWJshF1ldzdVcyE3VwmgjeYs0Z9PGEt2iXc=; b=fOIQpNFH3Hj3aH4z8c8LndmhZhjgIRnwSiYakybZdkUG62v1kYCyv9SC8gYkQ/euXY KIO0ipj01JI8VRm7CV8iPH+4nwCgb8uG9Y7sl40+NGGmrupx63kr0PN/iDhwQJ7prcJO +00O2fMYm233S5uGktAJMwgajolJjgbQqJuSGWlqDUiPE9NAYIx6Jmv3j1FQe0zlKgQ7 e5+NCPz7plbrMr9Dva30cmvklWwqFjHNd8coFxOtDf63ixQgC7LtZS3RzNVi/P0/1cup F8GLqgpQcnTgyMIR/avnsB6l9djLWL+De+go27XU2+i7AS3cyMXKGxHtkQruopCK8iO4 kj6A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=6l09n3V8AWJshF1ldzdVcyE3VwmgjeYs0Z9PGEt2iXc=; b=Z0pIb88yqGY+PFKLKA+vjGwyxg6T/4o/b9vUFpVo/z/UejtMmMFHDwdskUgSBA6ai8 iSrj3EgGJIgtAuSJriEUbO7gvfJpvj4gEK/lL7ipIm07UCSJtGwqyFyJXmpZ2iyIh/Ez B8Fnn7lGbi1OajSC0Z+VVpKlNDejN3ZteiK52Xze8nmf07AfxwNqej+v5Tsy9SdxHxJl io1DKxphGFSS909JeOoyKZolm1pm2zmwe24Lq5Y6Uy3cpI2YUw/1vW8Wwfxo2L2XFfpu c3SI4ODvWMStJzEusSfxGRwNkrV0NtQrjQh4nLy1vexfuPOyHS9oEu+o21+rKG9IkgMZ 8wBw== X-Gm-Message-State: AN3rC/5vHYoMLnsjqoixUYq7AqD8YPA0uFviGxArFJYuoS/oevsU/hc4 pgtceiEcb1MRxKKcNGCrFb9TtYX2nw== X-Received: by 10.55.165.130 with SMTP id o124mr9445255qke.306.1493389644158; Fri, 28 Apr 2017 07:27:24 -0700 (PDT) MIME-Version: 1.0 Sender: chmeeedalf@gmail.com Received: by 10.12.150.44 with HTTP; Fri, 28 Apr 2017 07:27:23 -0700 (PDT) In-Reply-To: <3wDrG96NhDzRRrV@baobab.bilink.it> References: <3wDrG96NhDzRRrV@baobab.bilink.it> From: Justin Hibbits Date: Fri, 28 Apr 2017 09:27:23 -0500 X-Google-Sender-Auth: vXednJp7OHydMdCVTQKapmtx39M Message-ID: Subject: Re: llvm 4.0 on PPC64 To: Luciano Mannucci Cc: "freebsd-ppc@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Apr 2017 14:27:26 -0000 Hi Luciano, On Friday, April 28, 2017, Luciano Mannucci wrote: > > It seems it doesn't compile on 11.0-RELEASE-p1. Is it a known bug? > I'm getting this from make install clean: > > /usr/ports/devel/llvm40/work/llvm-4.0.0.src/tools/lldb/ > source/Host/common/FileSpec.cpp: In function 'bool > {anonymous}::GetFileStats(const lldb_private::FileSpec*, stat*)': > /usr/ports/devel/llvm40/work/llvm-4.0.0.src/tools/lldb/ > source/Host/common/FileSpec.cpp:92:22: error: 'PATH_MAX' was not declared > in this scope > char resolved_path[PATH_MAX]; > ^ > /usr/ports/devel/llvm40/work/llvm-4.0.0.src/tools/lldb/ > source/Host/common/FileSpec.cpp:93:26: error: 'resolved_path' was not > declared in this scope > if (file_spec->GetPath(resolved_path, sizeof(resolved_path))) > ^ > ... > ninja: build stopped: subcommand failed. > *** Error code 1 > > Stop. > make[1]: stopped in /usr/ports/devel/llvm40 > *** Error code 1 > > Stop. > make: stopped in /usr/ports/devel/llvm40 > > Thanks to all, > > Luciano. > Yup, I see this, too. I haven't dug deep (or even shallow, for that matter) to try to fix it. I did look at lldb trunk, and it no longer has PATH_MAX anywhere, so might be fixed relative. If nothing else, we may have to wait for devel/llvm50, unless someone wants to try to fix it locally, or someone wants to get the necessary changes backported for llvm41. This blocks Mesa ports, so I added to my poudriere make.conf a "MESA_LLVM_VER=39" to get things to build. - Justin From owner-freebsd-ppc@freebsd.org Fri Apr 28 15:11:54 2017 Return-Path: Delivered-To: freebsd-ppc@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 7F540D546BB for ; Fri, 28 Apr 2017 15:11:54 +0000 (UTC) (envelope-from luciano@vespaperitivo.it) Received: from baobab.bilink.net (baobab.bilink.net [212.45.144.44]) by mx1.freebsd.org (Postfix) with ESMTP id 4311C362 for ; Fri, 28 Apr 2017 15:11:53 +0000 (UTC) (envelope-from luciano@vespaperitivo.it) Received: from localhost (localhost [127.0.0.1]) by baobab.bilink.it (Postfix) with ESMTP id 3wDy2x19sJzRRrr; Fri, 28 Apr 2017 17:11:53 +0200 (CEST) X-Virus-Scanned: amavisd-new at mcs.it Received: from baobab.bilink.net ([127.0.0.1]) by localhost (baobab.mcs.it [127.0.0.1]) (amavisd-new, port 11027) with ESMTP id 2iVt+bm4NKoo; Fri, 28 Apr 2017 17:11:53 +0200 (CEST) Received: from hermes.mcs.it (hermes.mcs.it [192.168.132.21]) by baobab.bilink.it (Postfix) with ESMTP id 3wDy2x0Q3kzRRrq; Fri, 28 Apr 2017 17:11:53 +0200 (CEST) Received: from mordeus (unknown [192.168.45.6]) by hermes.mcs.it (Postfix) with ESMTP id C0AFA1B7515; Fri, 28 Apr 2017 17:11:51 +0200 (CEST) Date: Fri, 28 Apr 2017 17:11:51 +0200 From: Luciano Mannucci To: Justin Hibbits Cc: "freebsd-ppc@freebsd.org" Subject: Re: llvm 4.0 on PPC64 In-Reply-To: References: <3wDrG96NhDzRRrV@baobab.bilink.it> X-Mailer: Claws Mail 3.14.1 (GTK+ 2.24.29; amd64-portbld-freebsd10.3) X-Face: 4qPv4GNcD; h<7Q/sK>+GqF4=CR@KmnPkSmwd+#%\F`4yjKO3"C]p'z=(oWRnsYBQGM\5g:4skqQY0NnV'dM:Mm:^/_+I@a"; [-s=ogufdF"9ggQ'=y MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Message-Id: <3wDy2x0Q3kzRRrq@baobab.bilink.it> X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Apr 2017 15:11:54 -0000 On Fri, 28 Apr 2017 09:27:23 -0500 Justin Hibbits wrote: > This blocks Mesa ports, so I added to my poudriere make.conf a > "MESA_LLVM_VER=39" to get things to build. I was building "vim". May I try something similar? Is there a setting (say, in /etc/make.conf) that would work for any port? Thanks again, Luciano. -- /"\ /Via A. Salaino, 7 - 20144 Milano (Italy) \ / ASCII RIBBON CAMPAIGN / PHONE : +39 2 485781 FAX: +39 2 48578250 X AGAINST HTML MAIL / E-MAIL: posthamster@sublink.sublink.ORG / \ AND POSTINGS / WWW: http://www.lesassaie.IT/ From owner-freebsd-ppc@freebsd.org Fri Apr 28 15:44:10 2017 Return-Path: Delivered-To: freebsd-ppc@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 C1A61D54007 for ; Fri, 28 Apr 2017 15:44:10 +0000 (UTC) (envelope-from chmeeedalf@gmail.com) Received: from mail-qt0-x22e.google.com (mail-qt0-x22e.google.com [IPv6:2607:f8b0:400d:c0d::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 7DC34959 for ; Fri, 28 Apr 2017 15:44:10 +0000 (UTC) (envelope-from chmeeedalf@gmail.com) Received: by mail-qt0-x22e.google.com with SMTP id c45so53297326qtb.1 for ; Fri, 28 Apr 2017 08:44:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=0wxJvnCePFFE7CcC2Ib6WJJs1KAxqAqnQ0PYbah08p8=; b=NknId7Afhgn35/QGI3PXKMCJKCrjFk8349FT8jQJiLY5XUT9yEHbd7yLq/Uh5G+WOz mUPGOMY/5HqHAsxuPv2Jq9Iz+ovYL2e2nV5B3lmNWnROQq39wkF5XZ/Hh7bo0tAX4XOm bql+CdR9WsCpdGJCjLn4SHRkOGP5zP+mK5AN+/LfN92+/0E42KW8zTiMBYcFs0SI8vpg /H3UrXt8x9WGwmBvZR6axuw3gdtAtBzFE9Id0xd9uKxV4M1eXwNRoehc2gcgxtpoJF2/ bV+vnx/X38Lww5N5W5p6LFRMqrNpGciRG44ETBJ9e1KpSPEJ7V1RlmDCX9iNs/cE/l4p o0Ow== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=0wxJvnCePFFE7CcC2Ib6WJJs1KAxqAqnQ0PYbah08p8=; b=Gqls3IEBmcy4WEUoJIuUwTsUmyTCExNYz8a1rO/n+1PmPtUP/CRtxEYD+xyyNFZcKB KeqHONDT5mULZ87Zv/PFLNM5WC8Y2qO+cH2BkZYcLIukPltxlB/7hnEcC0bCffjxCiY8 AG6mZM/AlFgGIOZEQKYxbIblkYpo4kanK3nJ3t5DZ64xCr2D++vWf+0T/5Th5aDnhbYh b1+ss9OF/QzWvw8sXE9YcYstprv+rpBmHrf9GuosOpxF8nEtdbGjt+mNDR0n7RGj6KNA 5iSE4VzAkTeloZJzwF0DaXMJHNcvKRifWRdIwyLDTpL/A5XXuAY77cw+RgRHTFZLb3tN q6Tg== X-Gm-Message-State: AN3rC/4W2RO7CgKbBpiFVivrvNPtK8KXXuBXa7e4h5A8UxlOgytu9vU9 L8wBUe/9btL2XZffghL5hll2oCt1GGsj X-Received: by 10.200.36.2 with SMTP id c2mr10311698qtc.271.1493394249567; Fri, 28 Apr 2017 08:44:09 -0700 (PDT) MIME-Version: 1.0 Sender: chmeeedalf@gmail.com Received: by 10.12.150.44 with HTTP; Fri, 28 Apr 2017 08:44:09 -0700 (PDT) In-Reply-To: <3wDy2x0Q3kzRRrq@baobab.bilink.it> References: <3wDrG96NhDzRRrV@baobab.bilink.it> <3wDy2x0Q3kzRRrq@baobab.bilink.it> From: Justin Hibbits Date: Fri, 28 Apr 2017 10:44:09 -0500 X-Google-Sender-Auth: tqg0UzzRnzaMKg3elm1wcDcPvew Message-ID: Subject: Re: llvm 4.0 on PPC64 To: Luciano Mannucci Cc: "freebsd-ppc@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Apr 2017 15:44:10 -0000 On Fri, Apr 28, 2017 at 10:11 AM, Luciano Mannucci wrote: > On Fri, 28 Apr 2017 09:27:23 -0500 > Justin Hibbits wrote: > >> This blocks Mesa ports, so I added to my poudriere make.conf a >> "MESA_LLVM_VER=39" to get things to build. > I was building "vim". May I try something similar? Is there a setting > (say, in /etc/make.conf) that would work for any port? > > Thanks again, > > Luciano. I'm going to guess you're building editors/vim with default options, which puts a dependency on gtk20. This indirectly requires llvm by way of cairo -> libEGL -> llvm39, so adding MESA_LLVM_VER=39 should work for you, too. Looking at http://www.freshports.org/devel/llvm40 it appears the only ports on powerpc64 that would need llvm are those that use mesa, so setting MESA_LLVM_VER should change it for all needed ports. - Justin From owner-freebsd-ppc@freebsd.org Fri Apr 28 16:31:31 2017 Return-Path: Delivered-To: freebsd-ppc@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 9E4AAD54121 for ; Fri, 28 Apr 2017 16:31:31 +0000 (UTC) (envelope-from luciano@vespaperitivo.it) Received: from baobab.bilink.net (baobab.bilink.net [212.45.144.44]) by mx1.freebsd.org (Postfix) with ESMTP id 618EF673 for ; Fri, 28 Apr 2017 16:31:30 +0000 (UTC) (envelope-from luciano@vespaperitivo.it) Received: from localhost (localhost [127.0.0.1]) by baobab.bilink.it (Postfix) with ESMTP id 3wDzpq1cDLzRRrr; Fri, 28 Apr 2017 18:31:31 +0200 (CEST) X-Virus-Scanned: amavisd-new at mcs.it Received: from baobab.bilink.net ([127.0.0.1]) by localhost (baobab.mcs.it [127.0.0.1]) (amavisd-new, port 11027) with ESMTP id O-zezP8yfOAp; Fri, 28 Apr 2017 18:31:31 +0200 (CEST) Received: from hermes.mcs.it (hermes.mcs.it [192.168.132.21]) by baobab.bilink.it (Postfix) with ESMTP id 3wDzpq0tGHzRRrq; Fri, 28 Apr 2017 18:31:31 +0200 (CEST) Received: from mordeus (unknown [192.168.45.6]) by hermes.mcs.it (Postfix) with ESMTP id C100C1B7515; Fri, 28 Apr 2017 18:31:29 +0200 (CEST) Date: Fri, 28 Apr 2017 18:31:29 +0200 From: Luciano Mannucci To: Justin Hibbits Cc: "freebsd-ppc@freebsd.org" Subject: Re: llvm 4.0 on PPC64 In-Reply-To: References: <3wDrG96NhDzRRrV@baobab.bilink.it> <3wDy2x0Q3kzRRrq@baobab.bilink.it> X-Mailer: Claws Mail 3.14.1 (GTK+ 2.24.29; amd64-portbld-freebsd10.3) X-Face: 4qPv4GNcD; h<7Q/sK>+GqF4=CR@KmnPkSmwd+#%\F`4yjKO3"C]p'z=(oWRnsYBQGM\5g:4skqQY0NnV'dM:Mm:^/_+I@a"; [-s=ogufdF"9ggQ'=y MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Message-Id: <3wDzpq0tGHzRRrq@baobab.bilink.it> X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Apr 2017 16:31:31 -0000 On Fri, 28 Apr 2017 10:44:09 -0500 Justin Hibbits wrote: > I'm going to guess you're building editors/vim with default options, > which puts a dependency on gtk20. This indirectly requires llvm by > way of cairo -> libEGL -> llvm39, so adding MESA_LLVM_VER=39 should > work for you, too. Thanks! Now it complains about pthread-stubs, I'll start another thread about that... Thanks again, Luciano. -- /"\ /Via A. Salaino, 7 - 20144 Milano (Italy) \ / ASCII RIBBON CAMPAIGN / PHONE : +39 2 485781 FAX: +39 2 48578250 X AGAINST HTML MAIL / E-MAIL: posthamster@sublink.sublink.ORG / \ AND POSTINGS / WWW: http://www.lesassaie.IT/ From owner-freebsd-ppc@freebsd.org Fri Apr 28 16:35:54 2017 Return-Path: Delivered-To: freebsd-ppc@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 98C59D542D4 for ; Fri, 28 Apr 2017 16:35:54 +0000 (UTC) (envelope-from luciano@vespaperitivo.it) Received: from baobab.bilink.net (baobab.bilink.net [212.45.144.44]) by mx1.freebsd.org (Postfix) with ESMTP id 5F72B92B for ; Fri, 28 Apr 2017 16:35:53 +0000 (UTC) (envelope-from luciano@vespaperitivo.it) Received: from localhost (localhost [127.0.0.1]) by baobab.bilink.it (Postfix) with ESMTP id 3wDzvt0QxqzRRrr for ; Fri, 28 Apr 2017 18:35:54 +0200 (CEST) X-Virus-Scanned: amavisd-new at mcs.it Received: from baobab.bilink.net ([127.0.0.1]) by localhost (baobab.mcs.it [127.0.0.1]) (amavisd-new, port 11027) with ESMTP id uFZrZOrcxy1K for ; Fri, 28 Apr 2017 18:35:53 +0200 (CEST) Received: from hermes.mcs.it (hermes.mcs.it [192.168.132.21]) by baobab.bilink.it (Postfix) with ESMTP id 3wDzvs6r91zRRrq for ; Fri, 28 Apr 2017 18:35:53 +0200 (CEST) Received: from mordeus (unknown [192.168.45.6]) by hermes.mcs.it (Postfix) with ESMTP id B7E0B1B7515 for ; Fri, 28 Apr 2017 18:35:52 +0200 (CEST) Date: Fri, 28 Apr 2017 18:35:52 +0200 From: Luciano Mannucci To: "freebsd-ppc@freebsd.org" Subject: PPC64 libdrm dependencies X-Mailer: Claws Mail 3.14.1 (GTK+ 2.24.29; amd64-portbld-freebsd10.3) X-Face: 4qPv4GNcD; h<7Q/sK>+GqF4=CR@KmnPkSmwd+#%\F`4yjKO3"C]p'z=(oWRnsYBQGM\5g:4skqQY0NnV'dM:Mm:^/_+I@a"; [-s=ogufdF"9ggQ'=y MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Message-Id: <3wDzvs6r91zRRrq@baobab.bilink.it> X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Apr 2017 16:35:54 -0000 Trying to compile libdrm (required by vim :), I'm getting complaints about pthread-stubs not beeing up to date: checking for PTHREADSTUBS... no configure: error: Package requirements (pthread-stubs >= 0.4) were not met: Package dependency requirement 'pthread-stubs >= 0.4' could not be satisfied. Package 'pthread-stubs' has version '0.3', required version is '>= 0.4' Is that a PPC64-only problem? Thanks to everybody, Luciano. -- /"\ /Via A. Salaino, 7 - 20144 Milano (Italy) \ / ASCII RIBBON CAMPAIGN / PHONE : +39 2 485781 FAX: +39 2 48578250 X AGAINST HTML MAIL / E-MAIL: posthamster@sublink.sublink.ORG / \ AND POSTINGS / WWW: http://www.lesassaie.IT/ From owner-freebsd-ppc@freebsd.org Sat Apr 29 03:23:55 2017 Return-Path: Delivered-To: freebsd-ppc@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 0F8D1D5581C for ; Sat, 29 Apr 2017 03:23:55 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-210-51.reflexion.net [208.70.210.51]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A1E7C232 for ; Sat, 29 Apr 2017 03:23:54 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 13619 invoked from network); 29 Apr 2017 03:23:53 -0000 Received: from unknown (HELO rtc-sm-01.app.dca.reflexion.local) (10.81.150.1) by 0 (rfx-qmail) with SMTP; 29 Apr 2017 03:23:53 -0000 Received: by rtc-sm-01.app.dca.reflexion.local (Reflexion email security v8.40.0) with SMTP; Fri, 28 Apr 2017 23:23:53 -0400 (EDT) Received: (qmail 16456 invoked from network); 29 Apr 2017 03:23:52 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (AES256-SHA encrypted) SMTP; 29 Apr 2017 03:23:52 -0000 Received: from [192.168.1.106] (c-76-115-7-162.hsd1.or.comcast.net [76.115.7.162]) by iron2.pdx.net (Postfix) with ESMTPSA id 2F1B0EC7ED9; Fri, 28 Apr 2017 20:23:52 -0700 (PDT) From: Mark Millard Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: llvm 4.0 on PPC64 Message-Id: Date: Fri, 28 Apr 2017 20:23:51 -0700 Cc: FreeBSD PowerPC ML To: luciano@vespaperitivo.it X-Mailer: Apple Mail (2.3273) X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 29 Apr 2017 03:23:55 -0000 Luciano Mannucci luciano at vespaperitivo.it wrote on Fri Apr 28 11:01:12 UTC 2017 (about building llvm 4.0 on powerpc64): > It seems it doesn't compile on 11.0-RELEASE-p1. Is it a known bug? > I'm getting this from make install clean: (He then lists some compile errors.) What compiler was trying to compile devel/llvm40 on powerpc64? For a powerpc64 FreeBSD system. . . Normally there is not a system-clang with libc++ but instead a gcc 4.2.1 and an old libstdc++ . In such a context some other lang/gcc* or devel/powerpc64-gcc or some such would be required to bootstrap devel/llvm40 . This sort of issue has been true since something like clang 3.5 for systems based on gcc 4.2.1 and its libstdc++ . === Mark Millard markmi at dsl-only.net