From owner-freebsd-ppc@freebsd.org Sun Nov 29 00:14:39 2015 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 A9E79A3B74B for ; Sun, 29 Nov 2015 00:14:39 +0000 (UTC) (envelope-from andy.silva@snscommunication.com) Received: from mailer238.gate85.rs.smtp.com (mailer238.gate85.rs.smtp.com [74.91.85.238]) by mx1.freebsd.org (Postfix) with ESMTP id 376311DF2 for ; Sun, 29 Nov 2015 00:14:38 +0000 (UTC) (envelope-from andy.silva@snscommunication.com) X-MSFBL: ZnJlZWJzZC1wcGNAZnJlZWJzZC5vcmdANzRfOTFfODVfMjM4QFNuc3RlbGVjb21f ZGVkaWNhdGVkX3Bvb2xA DKIM-Signature: v=1; a=rsa-sha256; d=smtp.com; s=smtpcomcustomers; c=relaxed/simple; q=dns/txt; i=@smtp.com; t=1448756069; h=From:Subject:To:Date:MIME-Version:Content-Type; bh=1tv78EQTO+XSvCZMoGn0I+YXXGGVtunlhLI+wu3QcMQ=; b=R5iRux377wSy6x61cZz2VPw3q5vsU7SkMnKSs56nOpa3cO27tgK90+s3qlS47hc4 O9o2TDY4RJn1uGkqMXuwZ7ACZF7AfQM8pwTZItQYKHYVD2d57xYNcq95oei/Izh3 6JDdaI/p/72047pd812VDGpxMtGl7rfD71Tm2ki8QQQ=; Received: from [154.20.125.37] ([154.20.125.37:61010] helo=d154-20-125-37.bchsia.telus.net) by rs-ord-mta03-1.smtp.com (envelope-from ) (ecelerity 3.3.2.44647 r(44647)) with ESMTPA id 07/72-32479-5634A565; Sun, 29 Nov 2015 00:14:29 +0000 MIME-Version: 1.0 From: "Andy Silva" Reply-To: andy.silva@snscommunication.com To: freebsd-ppc@freebsd.org Subject: The Wearable Technology Ecosystem: 2015 - 2030 - Opportunities, Challenges, Strategies, Industry Verticals and Forecasts (Report) X-Mailer: Smart_Send_2_0_138 Date: Sat, 28 Nov 2015 16:14:26 -0800 Message-ID: <80204267546562037112998@Ankur> X-SMTPCOM-Tracking-Number: ca6507f2-c97a-4b52-ac5e-892d9d504346 Feedback-ID: 6008902:SMTPCOM X-SMTPCOM-Sender-ID: 6008902 X-SMTPCOM-Spam-Policy: SMTP.com is a paid relay service. We do not tolerate UCE of any kind. Please report it ASAP to abuse@smtp.com Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Nov 2015 00:14:39 -0000 The Wearable Technology Ecosystem: 2015 - 2030 - Opportunities, Challenges,= Strategies, Industry Verticals and Forecasts Hello=20 I wanted to bring to your attention the latest SNS Research report in which= you might be interested, " The Wearable Technology Ecosystem: 2015 - 2030 = - Opportunities, Challenges, Strategies, Industry Verticals and Forecasts."=20 If you would like to see the report sample or have any questions, please le= t me know. =20 Report Information: Release Date: May 2015 Number of Pages: 567 Number of Tables and Figures: 217 =20 =20 Report Overview: =20 While wearable technology has been utilized in vertical sectors such as the= military and healthcare for many years, ongoing advances have triggered a = major resurgence of the concept, particularly among the consumer community.= Key enabling technologies including low cost sensors, wireless connectivit= y, active materials and energy have converged to make wearable technology m= ainstream.=20 With the continued miniaturization of enabling technologies, wearable devic= es have hit the mass market in a diverse variety of form factors, ranging f= rom glasses to even jewelry. Driven by the ability to interconnect with key modern trends of healthcare,= fitness, messaging and socialization, the wearable technology ecosystem is= attracting significant levels of interest. Companies as varied as smartph= one OEMs, wireless carriers, health insurers and retailers are circling the= ecosystem alongside tiny startups, all vying for a stake. SNS Research estimates that by 2016, wearable device shipments will surpass= 140 Million and will account for nearly $30 Billion in revenue. The market= is further expected to grow at a CAGR of 30% over the next five years. The "Wearable Technology Ecosystem: 2015 - 2030 - Opportunities, Challenges= , Strategies, Industry Verticals & Forecasts" report presents an in-depth a= ssessment of the wearable technology ecosystem including key market drivers= , challenges, investment potential, consumer & vertical market opportunitie= s, use cases, future roadmap, value chain, case studies, vendor market shar= e and strategies. The report also presents forecasts for wearabledevice shi= pments and revenue from 2015 through to 2030. The forecasts are further seg= mented for 7 device form factor submarkets, 7 vertical markets, 6 regions a= nd 73 countries. The report comes with an associated Excel datasheet suite covering quantita= tive data from all numeric forecasts presented in the report. Key Findings: =20 The report has the following key findings: By 2016, wearable device OEMs will pocket nearly $30 Billion from device sh= ipment revenues=20 SNS Research estimates that fitness and sports centric wearable device ship= ments are expected to grow at a CAGR of 28% over the next 5 years, eventual= ly accounting for 80 Million device shipments by the end of 2020=20 Wireless carriers are increasingly integrating wearable devices within thei= r M2M and IoT strategies=20 Wearable devices will help wireless carriers drive over $71 Billion in addi= tional service revenue by the end of 2020, following a CAGR of nearly 80% b= etween 2015 and 2020=20 The wearable applications ecosystem will account for nearly $2 Billion in r= evenue by the end of 2016=20 Driven by ongoing innovation and crowdfunding campaigns, SNS Research estim= ates that investors will pour over $1 Billion into wearabletechnology start= ups in 2015=20 The market is ripe for acquisitions of pure-play wearable technology startu= ps, as competition heats up between consumer and vertical centric OEMs=20 Nearly 50% of all wearable devices shipped in 2020 will support embedded ce= llular connectivity. This represents a $1.1 Billion opportunity for wireles= s chipset suppliers Topics Covered: =20 The report covers the following topics: Wearable technology ecosystem=20 Market drivers and barriers=20 Enabling technologies for wearable devices=20 Prospects of standardization and regulation for wearable technology=20 Wearable technology industry roadmap and value chain=20 Assessment of vertical market opportunities and use cases for consumer, hea= lthcare, professional sports, retail & hospitality, military, public safety= and 8 other verticals=20 Case studies of wearable technology deployments=20 Company profiles and strategies of over 360 wearable technology ecosystem p= layers=20 Wearable device vendor market share=20 Wearable device operating systems=20 Prospects of smartphone OEMs and wireless chipset suppliers in the wearable= technology ecosystem=20 LTE Direct and its impact on wearable technology=20 Strategic recommendations for enabling technology providers, wearable devic= e OEMs, vertical market players, application developers and wireless carrie= rs=20 Market analysis and forecasts from 2015 till 2030 Forecast Segmentation: =20 Market forecasts are provided for each of the following submarkets and the= ir categories: Wearable device shipments and revenue=20 Wearable application ecosystem revenue=20 Wearable driven wireless carrier service revenue=20 Vertical Submarkets=20 Consumer=20 Healthcare=20 Professional Sports Retail & Hospitality=20 Military=20 Public Safety=20 Others Form Factor Submarkets=20 Smart Bands=20 Smart Watches=20 Smart Glasses=20 Smart Clothing=20 Smart Jewelry=20 Heads-up Displays=20 Others Regional Markets=20 Asia Pacific=20 Eastern Europe=20 Latin & Central America=20 Middle East & Africa=20 North America=20 Western Europe Country Markets=20 73 Country level markets: Algeria, Argentina, Australia, Austria, Banglades= h, Belarus, Belgium, Bolivia, Bosnia & Herzegovina, Brazil, Bulgaria, Canad= a, Chile, China, Colombia, Croatia, Czech Republic, Denmark, Ecuador, Egypt= , Finland, France, Germany, Greece, Hong Kong, Hungary, India, Indonesia, I= reland, Israel, Italy, Japan, Kenya, Luxembourg, Malaysia, Mexico, Morocco,= Netherlands, New Zealand, Nigeria, Norway, Pakistan, Paraguay, Peru, Phili= ppines, Poland, Portugal, Qatar, Romania, Russia, Saudi Arabia, Serbia, Sin= gapore, Slovakia, South Africa, South Korea, Spain, Sudan, Sweden, Switzerl= and, Taiwan, Tanzania, Thailand, Tunisia, Turkey, UAE, UK, Ukraine, Uruguay= , USA, Uzbekistan, Venezuela and Vietnam Key Questions Answered: The report provides answers to the following key questions: How big is the wearable technology ecosystem=3F=20 How is the ecosystem evolving by segment and region=3F=20 What will the market size be in 2020 and at what rate will it grow=3F=20 What trends, challenges and barriers are influencing its growth=3F=20 Who are the key wearable device vendors and what are their strategies=3F=20 How much are vertical enterprises investing in wearable devices=3F=20 What opportunities exist for wireless chipset suppliers in the wearable tec= hnology ecosystem=3F=20 How can wireless carriers capitalize on the growing popularity of smart wat= ches, fitness bands, smart glasses and other wearable devices=3F=20 Which countries, regions and verticals will see the highest percentage of w= earable device shipments=3F=20 Which sports category will see the highest level of wearable technology int= egration=3F=20 How big is the wearable applications ecosystem=3F Report Pricing: Single User License: USD 2,500 Company Wide License: USD 3,500 Ordering Process: Please contact Andy Silva on andy.silva@snscommunication.com Provide the following information: 1. Report Title - 2. Report License - (Single User/Company Wide) 3. Name - 4. Email - 5. Job Title - 6. Company - 7. Invoice Address - Please contact me if you have any questions, or wish to purchase a copy. Ta= ble of contents and List of figures mentioned below for your better inside. I look forward to hearing from you. Kind Regards Andy Silva Marketing Executive Signals and Systems Telecom Reef Tower Jumeirah Lake Towers Sheikh Zayed Road Dubai, UAE =20 ___________________________________________________________________________= __________________________________________________________________________ =20 Table of Content =20 Chapter 1 1.1 Executive Summary 1.2 Topics Covered 1.3 Historical Revenue & Forecast Segmentation 1.4 Key Questions Answered 1.5 Key Findings 1.6 Methodology 1.7 Target Audience 1.8 Companies & Organizations Mentioned =20 Chapter 2: An Overview of Wearable Technology 2.1 What is Wearable Technology=3F 2.2 Device Classification 2.2.1 Head-worn Devices 2.2.2 Wrist-worn Devices 2.2.3 Leg and Ankle-worn Devices 2.2.4 Arm, Chest and Neck-worn Devices 2.2.5 Smart Clothing & Jewelry 2.2.6 In-Body Wearables 2.3 Enabling Technologies 2.3.1 MEMS & Sensors 2.3.2 BT-LE (Bluetooth Low Energy) & WiFi 2.3.3 Voice Recognition 2.3.4 Lowed Powered Wireless SoCs 2.3.5 RFID & NFC 2.3.6 GPS & Navigation Technology 2.3.7 Energy Harvesting 2.3.8 Ergonomics & Materials Science 2.3.9 Augmented Reality 2.4 Market Growth Drivers 2.4.1 Proliferation of Smartphones 2.4.2 Advances in Enabling Technologies & Components 2.4.3 Interest from New Market Segments 2.4.4 Human Centric Assistance 2.4.5 Meaningful Analytics & Tracking 2.4.6 Venture Capital, Crowdfunding & Corporate Investments 2.4.7 Endorsement by Major Mobile OEMs 2.5 Market Barriers 2.5.1 High Costs 2.5.2 Power Consumption & Battery Life Issues 2.5.3 Usability & Unusual Styling 2.5.4 Potential Health Issues 2.5.5 Privacy & Security Concerns 2.5.6 Social Acceptance =20 Chapter 3: Vertical Opportunities & Use Cases 3.1 Consumer Markets 3.1.1 Infotainment & Lifestyle 3.1.2 Casual Sports & Fitness 3.1.3 Gaming 3.1.4 Pet Care 3.1.5 Child Care & Entertainment 3.1.6 Helping People with Disabilities 3.1.7 Car Insurance Claims 3.1.8 Accurate & Targeted Marketing 3.2 Healthcare 3.2.1 Remote Patient Monitoring 3.2.2 Assisted Patient Examination 3.2.3 Reducing Healthcare Costs 3.2.4 Optimizing Health Insurance Costs 3.2.5 Enhancing Medical R&D 3.3 Professional Sports 3.3.1 Sports Data Analytics 3.3.2 Enhancing Real-Time Decision Making 3.3.3 Injury Prevention 3.4 Retail & Hospitality 3.4.1 Improving Retail Productivity 3.4.2 Comparing & Contrasting Retail Items 3.4.3 Travel: Personalizing Customer Service 3.4.4 Replacing Hotel Keys and Credit Cards 3.4.5 Augmenting City & Museum Tours 3.5 Military 3.5.1 Enhancing Infantry Tactics: Shooting Without Being Shot 3.5.2 Monitoring Combat Stress & Injuries 3.5.3 Enhancing Situational Awareness in the Battlefield 3.5.4 Enabling Battlefield Mobility 3.5.5 Facilitating Communications with Military Dogs 3.6 Public Safety 3.6.1 Recording Criminal Evidence 3.6.2 Enhancing Situational Awareness & Assets Coordination 3.6.3 Identifying Suspects & Traffic Violators 3.6.4 Monitoring Biophysical Activity for First Responders 3.6.5 Enhancing Fire Fighting Capabilities 3.6.6 Improving Response to Medical Emergencies 3.7 Other Verticals 3.7.1 Construction Industry 3.7.2 Mining Industry 3.7.3 Manufacturing Operations 3.7.4 Logistics & Supply Chain 3.7.5 Financial Services 3.7.6 Security & Authentication 3.7.7 Repair, Inspection & Field Services 3.7.8 Education 3.8 Case Studies 3.8.1 Virgin Atlantic: Improving Airline Customer Services with Wearable Te= chnology 3.8.1.1 Solution & Vendors 3.8.1.2 Applications 3.8.1.3 Feedback from the Field 3.8.2 U.S. Department of Defense: Delivering Tactical Information with Wear= able Technology 3.8.2.1 Solution & Vendors 3.8.2.2 Applications 3.8.2.3 Feedback from the Field 3.8.3 Dubai Police: Catching Speeding Drivers with Google Glass 3.8.3.1 Solution & Vendors 3.8.3.2 Applications 3.8.3.3 Feedback from the Field 3.8.4 Disney: Theme Park Management with Wearable Technology 3.8.4.1 Solution & Vendors 3.8.4.2 Applications 3.8.4.3 Feedback from the Field 3.8.5 AT&T: Connected Healthcare Monitoring for the Elderly 3.8.5.1 Solution & Vendors 3.8.5.2 Applications 3.8.5.3 Feedback from the Field =20 Chapter 4: Industry Roadmap & Value Chain 4.1 Wearable Technology Industry Roadmap 4.1.1 2013 =96 2014: Initial Hype & the Revival of Smart Watches 4.1.2 2015 =96 2016: Convergence of Wrist Worn Wearables 4.1.3 2017 =96 2020 & Beyond: The Augmented Reality & Smart Glasses Era 4.2 The Wearable Technology Value Chain 4.2.1 Wearable Device OEM Ecosystem 4.2.1.1 Vertical Centric OEMs 4.2.1.2 Smartphone, Tablet & Consumer Electronics OEMs 4.2.1.3 Fashion & Watch OEMs 4.2.2 Consumers & Vertical Enterprises 4.2.3 Wireless Carriers & the Connectivity Ecosystem 4.2.4 Applications Ecosystem =20 Chapter 5: Market Analysis & Forecasts 5.1 Global Outlook of Wearable Technology 5.2 Form Factor Segmentation 5.3 Smart Bands 5.4 Smart Watches 5.5 Smart Glasses 5.6 Smart Clothing 5.7 Smart Jewelry 5.8 Heads-up Display Systems 5.9 Others 5.10 Vertical Market Segmentation 5.11 Consumer Wearable Devices 5.12 Healthcare Wearable Devices 5.13 Professional Sports Wearable Devices 5.14 Retail & Hospitality Wearable Devices 5.15 Military Wearable Devices 5.16 Public Safety Wearable Devices 5.17 Wearable Devices in Other Verticals 5.18 Regional Market Segmentation 5.19 Asia Pacific 5.20 North America 5.20.1 Canada 5.20.2 USA 5.21 Western Europe 5.22 Eastern Europe 5.23 Middle East & Africa 5.24 Latin & Central America =20 Chapter 6: Key Market Players 6.1 270 Vision 6.2 3L Labs 6.3 4DForce 6.4 4iii Innovations 6.5 9Solutions 6.6 Abbot Laboratories 6.7 Active Mind Technology 6.8 AcousticSheep 6.9 Adidas 6.10 AirType 6.11 Amazon 6.12 Ambit Networks 6.13 AMD (Advanced Micro Devices) 6.14 Amiigo 6.15 Amulyte 6.16 Apple 6.17 ARA (Applied Research Associates) 6.18 Archos 6.19 ARM Holdings 6.20 ASUS (ASUSTeK Computer) 6.21 Atellani 6.22 Atheer Labs 6.23 Atlas Wearables 6.24 Augmendix 6.25 Avegant 6.26 AVG 6.27 Baidu 6.28 BAE Systems 6.29 Basis Science 6.30 Beddit 6.31 Behavioral Technology Group 6.32 BIA Sport 6.33 Bionym 6.34 Biosensics 6.35 BIT (Blue Infusion Technologies) 6.36 Bitbanger Labs 6.37 BI (GEO Group) 6.38 Blocks Wearables 6.39 bOMDIC 6.40 Bondara (Nagook) 6.41 Boston Scientific Corporation 6.42 BRAGI 6.43 Brilliantservice 6.44 Broadcom 6.45 Breitling 6.46 Brother Industries 6.47 BSX Atheletics 6.48 BTS Bioengineering 6.49 Buhel 6.50 Cambridge Temperature Concepts 6.51 Carre Technologies 6.52 Casio 6.53 Catapult Sports 6.54 Citizen 6.55 Cityzen Sciences 6.56 Codoon 6.57 CommandWear 6.58 CompeGPS 6.59 ConnecteDevice 6.60 Connect America 6.61 Control VR 6.62 Cool Shirt Systems 6.63 Creoir 6.64 CSR 6.65 Cuff 6.66 Cyberdyne 6.67 DAQRI 6.68 Dell 6.69 DK Tek Innovations 6.70 DorsaVi (ASX) 6.71 Dreamtrap Commercials 6.72 EB Sport Group 6.73 EdanSafe 6.74 Ekso Bionics 6.75 Electric Foxy 6.76 Emotiv Systems 6.77 Enjoy S.R.L 6.78 Epson (Seiko Epson Corporation) 6.79 Everfind 6.80 EuroTech 6.81 Evena Medical 6.82 Exelis 6.83 EyeTap 6.84 FashionTEQ 6.85 Fat Shark 6.86 Fatigue Science 6.87 Filip Technologies 6.88 Finis 6.89 FitBark 6.90 Fitbit 6.91 Fitbug 6.92 FitLinxx 6.93 Flyfit 6.94 Flextronics 6.95 Force Impact Technologies 6.96 Fossil 6.97 Foxtel 6.98 Freescale Semiconductor 6.99 Free Wavz 6.100 Fujitsu 6.101 Garmin 6.102 GEAK (Shanda Group) 6.103 Gemalto 6.104 General Dynamics Mission Systems 6.105 GestureLogic 6.106 Geopalz 6.107 Ginger.io 6.108 GlassUp 6.109 Glofaster 6.110 GN Store Nord 6.111 GoPro 6.112 Google 6.113 GOQii 6.114 Gucci 6.115 Guess 6.116 HealBe 6.117 HereO 6.118 Hollywog 6.119 Honeywell International 6.120 Hovding 6.121 House of Horology 6.122 HP 6.123 HTC 6.124 Huawei 6.125 i4C Innovations 6.126 i.am+ 6.127 ICEdot 6.128 ICON Health and Fitness 6.129 iHealth Lab 6.130 iLOC Technologies 6.131 i=92m SpA 6.132 Imagination Technologies 6.133 Imec 6.134 Immerz 6.135 Ineda Systems 6.136 Innovega 6.137 InfinitEye 6.138 Intel Corporation 6.139 InteraXon 6.140 InvenSense 6.141 Iotera 6.142 iRhythm 6.143 Instabeat 6.144 Iron Will Innovations 6.145 Jawbone 6.146 Jaybird 6.147 Johnson & Johnson 6.148 Kairos Watches 6.149 Kapture 6.150 Ki Performance 6.151 Kiwi Wearable Technologies 6.152 KMS Solutions 6.153 KoruLab 6.154 Kreyos 6.155 Kronoz 6.156 L-3 Communications 6.157 Lark Technologies 6.158 Laster Technologies 6.159 LeapFrog Enterprises 6.160 Lechal 6.161 LG Electronics 6.162 LifeBEAM 6.163 LifeLogger Technologies Corporation 6.164 Limmex 6.165 Liquid Image 6.166 Lockheed Martin 6.167 LogBar 6.168 LOSTnFOUND 6.169 Lumafit 6.170 Lumo BodyTech 6.171 Lumus 6.172 Luxottica 6.173 Mad Apparel 6.174 Magellan (MiTAC Digital Corporation) 6.175 Martian Watches 6.176 Matilde 6.177 MC10 6.178 McLear 6.179 MediaTek 6.180 Medtronic 6.181 Melon 6.182 META 6.183 Meta Watch 6.184 Microsoft 6.185 MindStream 6.186 Mio Global 6.187 Misfit Wearables 6.188 Moff 6.189 MonDevices 6.190 Moov 6.191 Moticon 6.192 Motion Fitness 6.193 Motorola Mobility/Lenovo 6.194 Motorola Solutions 6.195 Movable 6.196 Mozilla Corporation 6.197 Mutalink 6.198 Mutewatch 6.199 Myontec 6.200 Narrative 6.201 Neptune 6.202 Netatmo 6.203 NeuroPro 6.204 NeuroSky 6.205 New Balance 6.206 Nike 6.207 Nintendo 6.208 Nissan 6.209 Nixie Labs 6.210 Nixon 6.211 Nod 6.212 Notch Interfaces 6.213 NTT DoCoMo 6.214 Nuance 6.215 Nuubo 6.216 NVIDIA 6.217 NZN Labs 6.218 O-Synce 6.219 Oculus VR (Facebook) 6.220 ODG (Osterhout Design Group) 6.221 Olive Labs 6.222 Omate 6.223 OMG Life 6.224 Omron 6.225 OMsignal 6.226 Opening Ceremony 6.227 Optalert 6.228 Optinvent 6.229 OrCam Technologies 6.230 OriginGPS 6.231 Orion Labs (OnBeep) 6.232 Orpyx Medical Technologies 6.233 Owlet Baby Care 6.234 Panasonic 6.235 Pebble 6.236 Perceptive Devices 6.237 Performance Sports Group 6.238 Perpetua Power Source Technologies 6.239 PFO Tech 6.240 PHTL (PH Technical Labs) 6.241 Pivothead 6.242 Pixie Scientific 6.243 Phyode 6.244 Plantronics 6.245 Playtabase 6.246 PNI Sensor Corporation 6.247 Polar Electro 6.248 Pragmasystems 6.249 Preventice 6.250 Proteus Digital Health 6.251 PUSH Design Solutions 6.252 Qardio 6.253 Qualcomm 6.254 Ralph Lauren Corporation 6.255 Raytheon 6.256 Razer 6.257 Recon Instruments 6.258 Reebok International 6.259 Rest Devices 6.260 Revolutionary Tracker 6.261 RHLvision Technologies 6.262 Ringblingz 6.263 Ringly 6.264 RSL Steeper Group 6.265 Rufus Labs 6.266 S3 ID 6.267 Salesforce.com 6.268 Salutron 6.269 Samsung Electronics 6.270 Sarvint Technologies 6.271 Secret Labs 6.272 Seiko 6.273 SenseCore 6.274 Sensegiz Technologies 6.275 Sensible Baby 6.276 Sensoplex 6.277 Sensoria 6.278 Senso Solutions 6.279 Sentimoto 6.280 Seraphim Sense 6.281 Shimmer 6.282 ShotTracker 6.283 Si14 6.284 Sigmo 6.285 Skully Systems 6.286 Smart Device (SmartQ) 6.287 Smarty Destination Technology 6.288 Smarty Ring 6.289 SMI (SensoMotoric Instruments) 6.290 SMS Audio 6.291 Snaptracs 6.292 Somaxis 6.293 Sonitus Medical 6.294 Sonostar 6.295 Sony Mobile Communications 6.296 Sotera Wireless 6.297 Soundbrenner 6.298 SparkPeople 6.299 Spire 6.300 Sports Beat 6.301 SpotNSave 6.302 Spree Wearables 6.303 Sproutling 6.304 Sqord 6.305 Stalker Radar (Applied Concepts) 6.306 STATSports 6.307 Striiv 6.308 STMicroelectronics 6.309 SunFriend Corporation 6.310 Suunto 6.311 sWaP 6.312 Swatch Group 6.313 T.Ware 6.314 Tag Heuer 6.315 Tarsier 6.316 TASER International 6.317 TCL Communication 6.318 Technical Illusions 6.319 Thalmic Labs 6.320 Theatro 6.321 TI (Texas Instruments) 6.322 Timex Group 6.323 TLink Golf 6.324 TN Games 6.325 Tobii Technology 6.326 TomTom 6.327 Tomoon Technology 6.328 Touch Bionics 6.329 TrackingPoint 6.330 Two Tin Cans 6.331 U-blox 6.332 Under Armour 6.333 Uno 6.334 Valencell 6.335 Validic (Motivation Science) 6.336 Vancive Medical Technologies (Avery Dennison) 6.337 Vergence Labs 6.338 Victoria=92s Secret 6.339 Vigo 6.340 VSN Mobil 6.341 Vuzix 6.342 Wahoo Fitness 6.343 Wather Enterprises 6.344 We:eX (Wearable Experiments) 6.345 Wearable Intelligence 6.346 Weartrons Labs 6.347 Wellograph 6.348 Whistle 6.349 Withings 6.350 WTS (Wonder Technology Solutions) 6.351 X-Doria (Doria International) 6.352 Xensr 6.353 Xiaomi 6.354 XO Eye Technologies 6.355 XOWi 6.356 Xybermind 6.357 Yingqu Technology 6.358 Zackees 6.359 Zeiss (Carl Zeiss AG) 6.360 Zephyr Technology (Covidien) 6.361 Zepp Labs 6.362 Zinc Software 6.363 Zoll Medical Corporation 6.364 ZTE =20 Chapter 7: Conclusion & Strategic Recommendations 7.1 Wearable Technology Operating Systems: Is there a Dominant Market Leade= r=3F 7.2 LTE Direct & its Impact on Wearable Technology 7.3 How is Wearable Technology Affecting the Wireless Chipsets Ecosystem=3F 7.4 How Big is the Wearable Applications Ecosystem=3F 7.5 Prospects of Standardization & Regulation 7.6 Prospects of Smartphone OEMs in the Wearable Technology Ecosystem 7.7 Wireless Carriers: The Wearable Service Revenue Opportunity 7.8 Vendor Share: Who Leads the Market=3F 7.9 The Rise of Wearable Startups 7.10 Combining Fashion with Technology 7.11 Prospects of Fitness & Sports Centric Wearables 7.12 Recommendations 7.12.1 Enabling Technology Providers 7.12.2 Wearable Device OEMs & Vertical Players 7.12.3 Wearable Application Developers 7.12.4 Wireless Carriers List of Figure: =20 Figure 1: In-body Pill Camera Figure 2: Smartphone Installed Base by Region (Millions): 2015 - 2030 Figure 3: KOR-FX Haptic Feedback Vest Figure 4: DARPA ULTRA-VIS Wearable Display Unit and Augmented Reality View Figure 5: Wearable Technology Industry Roadmap Figure 6: The Wearable Technology Value Chain Figure 7: Global Wearable Device Shipments (Millions of Units): 2015 - 2030 Figure 8: Global Wearable Device Shipment Revenue ($ Million): 2015 - 2030 Figure 9: Global Wearable Device Shipments by Form Factor (Millions of Unit= s): 2015 - 2030 Figure 10: Global Wearable Device Shipment Revenue by Form Factor ($ Millio= n): 2015 - 2030 Figure 11: Global Smart Band Shipments (Millions of Units): 2015 - 2030 Figure 12: Global Smart Band Shipment Revenue ($ Million): 2015 - 2030 Figure 13: Global Smart Watch Shipments (Millions of Units): 2015 - 2030 Figure 14: Global Smart Watch Shipment Revenue ($ Million): 2015 - 2030 Figure 15: Global Smart Glasses Shipments (Millions of Units): 2015 - 2030 Figure 16: Global Smart Glasses Shipment Revenue ($ Million): 2015 - 2030 Figure 17: Global Smart Clothing Shipments (Millions of Units): 2015 - 2030 Figure 18: Global Smart Clothing Shipment Revenue ($ Million): 2015 - 2030 Figure 19: Global Smart Jewelry Shipments (Millions of Units): 2015 - 2030 Figure 20: Global Smart Jewelry Shipment Revenue ($ Million): 2015 - 2030 Figure 21: Global Heads-up Display System Shipments (Millions of Units): 20= 15 - 2030 Figure 22: Global Heads-up Display System Shipment Revenue ($ Million): 201= 5 - 2030 Figure 23: Global Other Wearable Device Shipments (Millions of Units): 2015= - 2030 Figure 24: Global Other Wearable Device Shipment Revenue ($ Million): 2015 = - 2030 Figure 25: Global Wearable Device Shipments by Vertical (Millions of Units)= : 2015 - 2030 Figure 26: Global Wearable Device Shipment Revenue by Vertical ($ Million):= 2015 - 2030 Figure 27: Global Customer Wearable Device Shipments (Millions of Units): 2= 015 - 2030 Figure 28: Global Consumer Wearable Device Shipment Revenue ($ Million): 20= 15 - 2030 Figure 29: Global Healthcare Wearable Device Shipments (Millions of Units):= 2015 - 2030 Figure 30: Global Healthcare Wearable Device Shipment Revenue ($ Million): = 2015 - 2030 Figure 31: Global Professional Sports Wearable Device Shipments (Millions o= f Units): 2015 - 2030 Figure 32: Global Professional Sports Wearable Device Shipment Revenue ($ M= illion): 2015 - 2030 Figure 33: Global Retail & Hospitality Wearable Device Shipments (Millions = of Units): 2015 - 2030 Figure 34: Global Retail & Hospitality Wearable Device Shipment Revenue ($ = Million): 2015 - 2030 Figure 35: Global Military Wearable Device Shipments (Millions of Units): 2= 015 - 2030 Figure 36: Global Military Wearable Device Shipment Revenue ($ Million): 20= 15 - 2030 Figure 37: Global Public Safety Wearable Device Shipments (Millions of Unit= s): 2015 - 2030 Figure 38: Global Public Safety Wearable Device Shipment Revenue ($ Million= ): 2015 - 2030 Figure 39: Global Wearable Device Shipments in Other Verticals (Millions of= Units): 2015 - 2030 Figure 40: Global Wearable Device Shipment Revenue in Other Verticals ($ Mi= llion): 2015 - 2030 Figure 41: Wearable Device Shipments by Region (Millions of Units): 2015 - = 2030 Figure 42: Wearable Device Shipment Revenue by Region ($ Million): 2015 - 2= 030 Figure 43: Asia Pacific Wearable Device Shipments (Millions of Units): 2015= - 2030 Figure 44: Asia Pacific Wearable Device Shipment Revenue ($ Million): 2015 = - 2030 Figure 45: Australia Wearable Device Shipments (Millions of Units): 2015 - = 2030 Figure 46: Australia Wearable Device Shipment Revenue ($ Million): 2015 - 2= 030 Figure 47: Bangladesh Wearable Device Shipments (Millions of Units): 2015 -= 2030 Figure 48: Bangladesh Wearable Device Shipment Revenue ($ Million): 2015 - = 2030 Figure 49: China Wearable Device Shipments (Millions of Units): 2015 - 2030 Figure 50: China Wearable Device Shipment Revenue ($ Million): 2015 - 2030 Figure 51: Hong Kong Wearable Device Shipments (Millions of Units): 2015 - = 2030 Figure 52: Hong Kong Wearable Device Shipment Revenue ($ Million): 2015 - 2= 030 Figure 53: India Wearable Device Shipments (Millions of Units): 2015 - 2030 Figure 54: India Wearable Device Shipment Revenue ($ Million): 2015 - 2030 Figure 55: Indonesia Wearable Device Shipments (Millions of Units): 2015 - = 2030 Figure 56: Indonesia Wearable Device Shipment Revenue ($ Million): 2015 - 2= 030 Figure 57: Japan Wearable Device Shipments (Millions of Units): 2015 - 2030 Figure 58: Japan Wearable Device Shipment Revenue ($ Million): 2015 - 2030 Figure 59: Malaysia Wearable Device Shipments (Millions of Units): 2015 - 2= 030 Figure 60: Malaysia Wearable Device Shipment Revenue ($ Million): 2015 - 20= 30 Figure 61: New Zealand Wearable Device Shipments (Millions of Units): 2015 = - 2030 Figure 62: New Zealand Wearable Device Shipment Revenue ($ Million): 2015 -= 2030 Figure 63: Pakistan Wearable Device Shipments (Millions of Units): 2015 - 2= 030 Figure 64: Pakistan Wearable Device Shipment Revenue ($ Million): 2015 - 20= 30 Figure 65: Philippines Wearable Device Shipments (Millions of Units): 2015 = - 2030 Figure 66: Philippines Wearable Device Shipment Revenue ($ Million): 2015 -= 2030 Figure 67: Singapore Wearable Device Shipments (Millions of Units): 2015 - = 2030 Figure 68: Singapore Wearable Device Shipment Revenue ($ Million): 2015 - 2= 030 Figure 69: South Korea Wearable Device Shipments (Millions of Units): 2015 = - 2030 Figure 70: South Korea Wearable Device Shipment Revenue ($ Million): 2015 -= 2030 Figure 71: Taiwan Wearable Device Shipments (Millions of Units): 2015 - 2030 Figure 72: Taiwan Wearable Device Shipment Revenue ($ Million): 2015 - 2030 Figure 73: Thailand Wearable Device Shipments (Millions of Units): 2015 - 2= 030 Figure 74: Thailand Wearable Device Shipment Revenue ($ Million): 2015 - 20= 30 Figure 75: Vietnam Wearable Device Shipments (Millions of Units): 2015 - 20= 30 Figure 76: Vietnam Wearable Device Shipment Revenue ($ Million): 2015 - 2030 Figure 77: Rest of Asia Pacific Wearable Device Shipments (Millions of Unit= s): 2015 - 2030 Figure 78: Rest of Asia Pacific Wearable Device Shipment Revenue ($ Million= ): 2015 - 2030 Figure 79: North America Wearable Device Shipments (Millions of Units): 201= 5 - 2030 Figure 80: North America Wearable Device Shipment Revenue ($ Million): 2015= - 2030 Figure 81: Canada Wearable Device Shipments (Millions of Units): 2015 - 2030 Figure 82: Canada Wearable Device Shipment Revenue ($ Million): 2015 - 2030 Figure 83: USA Wearable Device Shipments (Millions of Units): 2015 - 2030 Figure 84: USA Wearable Device Shipment Revenue ($ Million): 2015 - 2030 Figure 85: Western Europe Wearable Device Shipments (Millions of Units): 20= 15 - 2030 Figure 86: Western Europe Wearable Device Shipment Revenue ($ Million): 201= 5 - 2030 Figure 87: Austria Wearable Device Shipments (Millions of Units): 2015 - 20= 30 Figure 88: Austria Wearable Device Shipment Revenue ($ Million): 2015 - 2030 Figure 89: Belgium Wearable Device Shipments (Millions of Units): 2015 - 20= 30 Figure 90: Belgium Wearable Device Shipment Revenue ($ Million): 2015 - 2030 Figure 91: Denmark Wearable Device Shipments (Millions of Units): 2015 - 20= 30 Figure 92: Denmark Wearable Device Shipment Revenue ($ Million): 2015 - 2030 Figure 93: Finland Wearable Device Shipments (Millions of Units): 2015 - 20= 30 Figure 94: Finland Wearable Device Shipment Revenue ($ Million): 2015 - 2030 Figure 95: France Wearable Device Shipments (Millions of Units): 2015 - 2030 Figure 96: France Wearable Device Shipment Revenue ($ Million): 2015 - 2030 Figure 97: Germany Wearable Device Shipments (Millions of Units): 2015 - 20= 30 Figure 98: Germany Wearable Device Shipment Revenue ($ Million): 2015 - 2030 Figure 99: Greece Wearable Device Shipments (Millions of Units): 2015 - 2030 Figure 100: Greece Wearable Device Shipment Revenue ($ Million): 2015 - 2030 Figure 101: Ireland Wearable Device Shipments (Millions of Units): 2015 - 2= 030 Figure 102: Ireland Wearable Device Shipment Revenue ($ Million): 2015 - 20= 30 Figure 103: Italy Wearable Device Shipments (Millions of Units): 2015 - 2030 Figure 104: Italy Wearable Device Shipment Revenue ($ Million): 2015 - 2030 Figure 105: Luxembourg Wearable Device Shipments (Millions of Units): 2015 = - 2030 Figure 106: Luxembourg Wearable Device Shipment Revenue ($ Million): 2015 -= 2030 Figure 107: Netherlands Wearable Device Shipments (Millions of Units): 2015= - 2030 Figure 108: Netherlands Wearable Device Shipment Revenue ($ Million): 2015 = - 2030 Figure 109: Norway Wearable Device Shipments (Millions of Units): 2015 - 20= 30 Figure 110: Norway Wearable Device Shipment Revenue ($ Million): 2015 - 2030 Figure 111: Portugal Wearable Device Shipments (Millions of Units): 2015 - = 2030 Figure 112: Portugal Wearable Device Shipment Revenue ($ Million): 2015 - 2= 030 Figure 113: Spain Wearable Device Shipments (Millions of Units): 2015 - 2030 Figure 114: Spain Wearable Device Shipment Revenue ($ Million): 2015 - 2030 Figure 115: Sweden Wearable Device Shipments (Millions of Units): 2015 - 20= 30 Figure 116: Sweden Wearable Device Shipment Revenue ($ Million): 2015 - 2030 Figure 117: Switzerland Wearable Device Shipments (Millions of Units): 2015= - 2030 Figure 118: Switzerland Wearable Device Shipment Revenue ($ Million): 2015 = - 2030 Figure 119: Turkey Wearable Device Shipments (Millions of Units): 2015 - 20= 30 Figure 120: Turkey Wearable Device Shipment Revenue ($ Million): 2015 - 2030 Figure 121: UK Wearable Device Shipments (Millions of Units): 2015 - 2030 Figure 122: UK Wearable Device Shipment Revenue ($ Million): 2015 - 2030 Figure 123: Rest of Western Europe Wearable Device Shipments (Millions of U= nits): 2015 - 2030 Figure 124: Rest of Western Europe Wearable Device Shipment Revenue ($ Mill= ion): 2015 - 2030 Figure 125: Eastern Europe Wearable Device Shipments (Millions of Units): 2= 015 - 2030 Figure 126: Eastern Europe Wearable Device Shipment Revenue ($ Million): 20= 15 - 2030 Figure 127: Belarus Wearable Device Shipments (Millions of Units): 2015 - 2= 030 Figure 128: Belarus Wearable Device Shipment Revenue ($ Million): 2015 - 20= 30 Figure 129: Bosnia & Herzegovina Wearable Device Shipments (Millions of Uni= ts): 2015 - 2030 Figure 130: Bosnia & Herzegovina Wearable Device Shipment Revenue ($ Millio= n): 2015 - 2030 Figure 131: Bulgaria Wearable Device Shipments (Millions of Units): 2015 - = 2030 Figure 132: Bulgaria Wearable Device Shipment Revenue ($ Million): 2015 - 2= 030 Figure 133: Croatia Wearable Device Shipments (Millions of Units): 2015 - 2= 030 Figure 134: Croatia Wearable Device Shipment Revenue ($ Million): 2015 - 20= 30 Figure 135: Czech Republic Wearable Device Shipments (Millions of Units): 2= 015 - 2030 Figure 136: Czech Republic Wearable Device Shipment Revenue ($ Million): 20= 15 - 2030 Figure 137: Hungary Wearable Device Shipments (Millions of Units): 2015 - 2= 030 Figure 138: Hungary Wearable Device Shipment Revenue ($ Million): 2015 - 20= 30 Figure 139: Poland Wearable Device Shipments (Millions of Units): 2015 - 20= 30 Figure 140: Poland Wearable Device Shipment Revenue ($ Million): 2015 - 2030 Figure 141: Romania Wearable Device Shipments (Millions of Units): 2015 - 2= 030 Figure 142: Romania Wearable Device Shipment Revenue ($ Million): 2015 - 20= 30 Figure 143: Russia Wearable Device Shipments (Millions of Units): 2015 - 20= 30 Figure 144: Russia Wearable Device Shipment Revenue ($ Million): 2015 - 2030 Figure 145: Serbia Wearable Device Shipments (Millions of Units): 2015 - 20= 30 Figure 146: Serbia Wearable Device Shipment Revenue ($ Million): 2015 - 2030 Figure 147: Slovakia Wearable Device Shipments (Millions of Units): 2015 - = 2030 Figure 148: Slovakia Wearable Device Shipment Revenue ($ Million): 2015 - 2= 030 Figure 149: Ukraine Wearable Device Shipments (Millions of Units): 2015 - 2= 030 Figure 150: Ukraine Wearable Device Shipment Revenue ($ Million): 2015 - 20= 30 Figure 151: Uzbekistan Wearable Device Shipments (Millions of Units): 2015 = - 2030 Figure 152: Uzbekistan Wearable Device Shipment Revenue ($ Million): 2015 -= 2030 Figure 153: Rest of Eastern Europe Wearable Device Shipments (Millions of U= nits): 2015 - 2030 Figure 154: Rest of Eastern Europe Wearable Device Shipment Revenue ($ Mill= ion): 2015 - 2030 Figure 155: Middle East & Africa Wearable Device Shipments (Millions of Uni= ts): 2015 - 2030 Figure 156: Middle East & Africa Wearable Device Shipment Revenue ($ Millio= n): 2015 - 2030 Figure 157: Algeria Wearable Device Shipments (Millions of Units): 2015 - 2= 030 Figure 158: Algeria Wearable Device Shipment Revenue ($ Million): 2015 - 20= 30 Figure 159: Egypt Wearable Device Shipments (Millions of Units): 2015 - 2030 Figure 160: Egypt Wearable Device Shipment Revenue ($ Million): 2015 - 2030 Figure 161: Israel Wearable Device Shipments (Millions of Units): 2015 - 20= 30 Figure 162: Israel Wearable Device Shipment Revenue ($ Million): 2015 - 2030 Figure 163: Kenya Wearable Device Shipments (Millions of Units): 2015 - 2030 Figure 164: Kenya Wearable Device Shipment Revenue ($ Million): 2015 - 2030 Figure 165: Morocco Wearable Device Shipments (Millions of Units): 2015 - 2= 030 Figure 166: Morocco Wearable Device Shipment Revenue ($ Million): 2015 - 20= 30 Figure 167: Nigeria Wearable Device Shipments (Millions of Units): 2015 - 2= 030 Figure 168: Nigeria Wearable Device Shipment Revenue ($ Million): 2015 - 20= 30 Figure 169: Qatar Wearable Device Shipments (Millions of Units): 2015 - 2030 Figure 170: Qatar Wearable Device Shipment Revenue ($ Million): 2015 - 2030 Figure 171: Saudi Arabia Wearable Device Shipments (Millions of Units): 201= 5 - 2030 Figure 172: Saudi Arabia Wearable Device Shipment Revenue ($ Million): 2015= - 2030 Figure 173: South Africa Wearable Device Shipments (Millions of Units): 201= 5 - 2030 Figure 174: South Africa Wearable Device Shipment Revenue ($ Million): 2015= - 2030 Figure 175: Sudan Wearable Device Shipments (Millions of Units): 2015 - 2030 Figure 176: Sudan Wearable Device Shipment Revenue ($ Million): 2015 - 2030 Figure 177: Tanzania Wearable Device Shipments (Millions of Units): 2015 - = 2030 Figure 178: Tanzania Wearable Device Shipment Revenue ($ Million): 2015 - 2= 030 Figure 179: Tunisia Wearable Device Shipments (Millions of Units): 2015 - 2= 030 Figure 180: Tunisia Wearable Device Shipment Revenue ($ Million): 2015 - 20= 30 Figure 181: UAE Wearable Device Shipments (Millions of Units): 2015 - 2030 Figure 182: UAE Wearable Device Shipment Revenue ($ Million): 2015 - 2030 Figure 183: Rest of the Middle East & Africa Wearable Device Shipments (Mil= lions of Units): 2015 - 2030 Figure 184: Rest of the Middle East & Africa Wearable Device Shipment Reven= ue ($ Million): 2015 - 2030 Figure 185: Latin & Central America Wearable Device Shipments (Millions of = Units): 2015 - 2030 Figure 186: Latin & Central America Wearable Device Shipment Revenue ($ Mil= lion): 2015 - 2030 Figure 187: Argentina Wearable Device Shipments (Millions of Units): 2015 -= 2030 Figure 188: Argentina Wearable Device Shipment Revenue ($ Million): 2015 - = 2030 Figure 189: Bolivia Wearable Device Shipments (Millions of Units): 2015 - 2= 030 Figure 190: Bolivia Wearable Device Shipment Revenue ($ Million): 2015 - 20= 30 Figure 191: Brazil Wearable Device Shipments (Millions of Units): 2015 - 20= 30 Figure 192: Brazil Wearable Device Shipment Revenue ($ Million): 2015 - 2030 Figure 193: Chile Wearable Device Shipments (Millions of Units): 2015 - 2030 Figure 194: Chile Wearable Device Shipment Revenue ($ Million): 2015 - 2030 Figure 195: Colombia Wearable Device Shipments (Millions of Units): 2015 - = 2030 Figure 196: Colombia Wearable Device Shipment Revenue ($ Million): 2015 - 2= 030 Figure 197: Ecuador Wearable Device Shipments (Millions of Units): 2015 - 2= 030 Figure 198: Ecuador Wearable Device Shipment Revenue ($ Million): 2015 - 20= 30 Figure 199: Mexico Wearable Device Shipments (Millions of Units): 2015 - 20= 30 Figure 200: Mexico Wearable Device Shipment Revenue ($ Million): 2015 - 2030 Figure 201: Paraguay Wearable Device Shipments (Millions of Units): 2015 - = 2030 Figure 202: Paraguay Wearable Device Shipment Revenue ($ Million): 2015 - 2= 030 Figure 203: Peru Wearable Device Shipments (Millions of Units): 2015 - 2030 Figure 204: Peru Wearable Device Shipment Revenue ($ Million): 2015 - 2030 Figure 205: Uruguay Wearable Device Shipments (Millions of Units): 2015 - 2= 030 Figure 206: Uruguay Wearable Device Shipment Revenue ($ Million): 2015 - 20= 30 Figure 207: Venezuela Wearable Device Shipments (Millions of Units): 2015 -= 2030 Figure 208: Venezuela Wearable Device Shipment Revenue ($ Million): 2015 - = 2030 Figure 209: Rest of Latin & Central America Wearable Device Shipments (Mill= ions of Units): 2015 - 2030 Figure 210: Rest of Latin & Central America Wearable Device Shipment Revenu= e ($ Million): 2015 - 2030 Figure 211: Global Wireless Chipset Shipments for Wearable Devices (Million= s of Units): 2015 - 2030 Figure 212: Global Wearable Application Ecosystem Revenue by Vertical ($ Mi= llion): 2015 - 2030 Figure 213: Global Wearable Driven Wireless Carrier Service Revenue by Form= Factor ($ Million): 2015 - 2030 Figure 214: Wearable Technology Market Share (%) Figure 215: Fashion Centric Wearables Figure 216: Global Fitness & Sports Centric Wearable Device Shipments by Ca= tegory (Millions of Units): 2015 - 2030 Figure 217: Global Fitness & Sports Centric Wearable Device Shipment Revenu= e by Category ($ Million): 2015 =96 2030 =20 =20 Thank you once again and looking forward to hearing from you. =20 Kind Regards =20 Andy Silva Marketing Executive Signals and Systems Telecom andy.silva@snscommunication.com Reef Tower Jumeirah Lake Towers Sheikh Zayed Road Dubai, UAE =20 =20 To unsubscribe send an email with unsubscribe in the subject line to: remov= e@snsreports.com From owner-freebsd-ppc@freebsd.org Sun Nov 29 03:58:09 2015 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 13452A3A8D8 for ; Sun, 29 Nov 2015 03:58:09 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-211-151.reflexion.net [208.70.211.151]) (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 C9F891E0A for ; Sun, 29 Nov 2015 03:58:08 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 22528 invoked from network); 29 Nov 2015 03:58:01 -0000 Received: from unknown (HELO mail-cs-01.app.dca.reflexion.local) (10.81.19.1) by 0 (rfx-qmail) with SMTP; 29 Nov 2015 03:58:01 -0000 Received: by mail-cs-01.app.dca.reflexion.local (Reflexion email security v7.80.0) with SMTP; Sat, 28 Nov 2015 22:58:02 -0500 (EST) Received: (qmail 581 invoked from network); 29 Nov 2015 03:58:02 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with SMTP; 29 Nov 2015 03:58:02 -0000 X-No-Relay: not in my network X-No-Relay: not in my network Received: from [192.168.1.8] (c-76-115-7-162.hsd1.or.comcast.net [76.115.7.162]) by iron2.pdx.net (Postfix) with ESMTPSA id E8605B1E001; Sat, 28 Nov 2015 19:57:54 -0800 (PST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\)) Subject: lang/gcc5 vs. devel/powerpc64-gcc: conflict for /usr/local/bin/powerpc64-portbld-freebsd11.0-gcc-5.2.0 From: Mark Millard In-Reply-To: <6AA244B9-DE60-4D8B-A08E-AADD73F9D856@dsl-only.net> Date: Sat, 28 Nov 2015 19:57:59 -0800 Content-Transfer-Encoding: quoted-printable Message-Id: References: <01BA3FF2-F362-48FA-B9E2-112E05CC00ED@dsl-only.net> <6AA244B9-DE60-4D8B-A08E-AADD73F9D856@dsl-only.net> To: FreeBSD PowerPC ML , FreeBSD Toolchain X-Mailer: Apple Mail (2.2104) X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Nov 2015 03:58:09 -0000 On a powerpc64 PowerMac I attempted to install lang/gcc5 and then use it = to update devel/powerpc64-xtoolchain-gcc from the old 4.9.1 vintage that = I had around. After the usual workaround for around 6 files that stage = funny when a powerpc64 hosts powerpc64-gcc being built, I got the = following notice on continuing the powerpc64-xtoolchain-gcc build = (portmaster's -C used): > Installing powerpc64-gcc-5.2.0... > pkg-static: powerpc64-gcc-5.2.0 conflicts with gcc5-5.2.0_2 (installs = files into the same place). Problematic file: = /usr/local/bin/powerpc64-portbld-freebsd11.0-gcc-5.2.0 Context details for those that care: > # freebsd-version -ku; uname -aKU > 11.0-CURRENT > 11.0-CURRENT > FreeBSD FBSDG5C0 11.0-CURRENT FreeBSD 11.0-CURRENT #12 r281630M: Sat = Apr 18 01:15:13 PDT 2015 = root@FBSDG5C0:/usr/obj/usr/src/sys/GENERIC64vtsc-NODEBUG powerpc = 1100070 1100070 The activity was to be a preliminary stage to updating to a more modern = 11.0-CURRENT based on the updated powerpc64-xtoolchain-gcc . > # svnlite info /usr/ports > Path: /usr/ports > Working Copy Root Path: /usr/ports > URL: https://svn0.us-west.freebsd.org/ports/head > Relative URL: ^/head > Repository Root: https://svn0.us-west.freebsd.org/ports > Repository UUID: 35697150-7ecd-e111-bb59-0022644237b5 > Revision: 402562 > Node Kind: directory > Schedule: normal > Last Changed Author: rene > Last Changed Rev: 402562 > Last Changed Date: 2015-11-28 15:08:03 -0800 (Sat, 28 Nov 2015) > # more /etc/make.conf > WRKDIRPREFIX=3D/usr/obj/portswork > MALLOC_PRODUCTION=3D > CC=3D/usr/local/bin/gcc5 > CXX=3D/usr/local/bin/g++5 > CPP=3D/usr/local/bin/cpp5 > AS=3D/usr/local/powerpc64-portbld-freebsd11.0/bin/as > AR=3D/usr/local/powerpc64-portbld-freebsd11.0/bin/ar > LD=3D/usr/local/powerpc64-portbld-freebsd11.0/bin/ld > NM=3D/usr/local/powerpc64-portbld-freebsd11.0/bin/nm > OBJCOPY=3D/usr/local/powerpc64-portbld-freebsd11.0/bin/objcopy > OBJDUMP=3D/usr/local/powerpc64-portbld-freebsd11.0/bin/objdump > RANLIB=3D/usr/local/powerpc64-portbld-freebsd11.0/bin/ranlib > SIZE=3D/usr/local/powerpc64-portbld-freebsd11.0/bin/size > STRINGS=3D/usr/local/powerpc64-portbld-freebsd11.0/bin/strings Side note on the powerpc64-gcc staging problems: My workaround for the powerpc64-gcc staging problems when built on a = powerpc64 PowerMac for a 11.0-CURRENT context was: > cp -ax = /usr/obj/portswork/usr/ports/devel/powerpc64-gcc/work/build-gcc/gcc/gcov = /usr/obj/portswork/usr/ports/devel/powerpc64-gcc/work/stage/usr/local/bin/= powerpc64-portbld-freebsd11.0-gcov >=20 > cp -ax = /usr/obj/portswork/usr/ports/devel/powerpc64-gcc/work/build-gcc/gcc/gcov-t= ool = /usr/obj/portswork/usr/ports/devel/powerpc64-gcc/work/stage/usr/local/bin/= powerpc64-portbld-freebsd11.0-gcov-tool >=20 > cp -ax = /usr/obj/portswork/usr/ports/devel/powerpc64-gcc/work/stage/usr/local/man/= man1/cpp.1.gz = /usr/obj/portswork/usr/ports/devel/powerpc64-gcc/work/stage/usr/local/man/= man1/powerpc64-portbld-freebsd11.0-cpp.1.gz >=20 > cp -ax = /usr/obj/portswork/usr/ports/devel/powerpc64-gcc/work/stage/usr/local/man/= man1/g++.1.gz = /usr/obj/portswork/usr/ports/devel/powerpc64-gcc/work/stage/usr/local/man/= man1/powerpc64-portbld-freebsd11.0-g++.1.gz >=20 > cp -ax = /usr/obj/portswork/usr/ports/devel/powerpc64-gcc/work/stage/usr/local/man/= man1/gcc.1.gz = /usr/obj/portswork/usr/ports/devel/powerpc64-gcc/work/stage/usr/local/man/= man1/powerpc64-portbld-freebsd11.0-gcc.1.gz >=20 > cp -ax = /usr/obj/portswork/usr/ports/devel/powerpc64-gcc/work/stage/usr/local/man/= man1/gcov.1.gz = /usr/obj/portswork/usr/ports/devel/powerpc64-gcc/work/stage/usr/local/man/= man1/powerpc64-portbld-freebsd11.0-gcov.1.gz >=20 > portmaster --no-confirm -CtDK lang/powerpc64-xtoolchain-gcc That last simply added the "C" before the "tDK" of the original = portmaster command that I started the powerpc64-xtoolchain-gcc build = with. =3D=3D=3D Mark Millard markmi at dsl-only.net From owner-freebsd-ppc@freebsd.org Sun Nov 29 10:03:10 2015 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 7CBA1A3B8BD for ; Sun, 29 Nov 2015 10:03:10 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-211-151.reflexion.net [208.70.211.151]) (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 3B4841F6D for ; Sun, 29 Nov 2015 10:03:09 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 26451 invoked from network); 29 Nov 2015 10:03:06 -0000 Received: from unknown (HELO rtc-sm-01.app.dca.reflexion.local) (10.81.150.1) by 0 (rfx-qmail) with SMTP; 29 Nov 2015 10:03:06 -0000 Received: by rtc-sm-01.app.dca.reflexion.local (Reflexion email security v7.80.0) with SMTP; Sun, 29 Nov 2015 05:03:07 -0500 (EST) Received: (qmail 30787 invoked from network); 29 Nov 2015 10:03:07 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with SMTP; 29 Nov 2015 10:03:07 -0000 X-No-Relay: not in my network X-No-Relay: not in my network Received: from [192.168.1.8] (c-76-115-7-162.hsd1.or.comcast.net [76.115.7.162]) by iron2.pdx.net (Postfix) with ESMTPSA id A1165B1E002; Sun, 29 Nov 2015 02:03:05 -0800 (PST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\)) Subject: head/kerberos5/lib/libkrb5/ and libhdb/ not looking in /usr/obj/usr/src/tmp/usr/lib/ for linking From: Mark Millard In-Reply-To: <6AA244B9-DE60-4D8B-A08E-AADD73F9D856@dsl-only.net> Date: Sun, 29 Nov 2015 02:03:05 -0800 Content-Transfer-Encoding: quoted-printable Message-Id: <106D9CB0-D9AE-4463-A03E-3AB16583CDA7@dsl-only.net> References: <01BA3FF2-F362-48FA-B9E2-112E05CC00ED@dsl-only.net> <6AA244B9-DE60-4D8B-A08E-AADD73F9D856@dsl-only.net> To: FreeBSD PowerPC ML , FreeBSD Toolchain X-Mailer: Apple Mail (2.2104) X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Nov 2015 10:03:10 -0000 The following additions of "-L/usr/obj/usr/src/tmp/usr/lib" just = illustrate the kind of path that is missing for libkrb5 and libhdb: = these additions were sufficient for my context to link. I do not think = such hard wired path are appropriate outside such an experiment. Index: /usr/src/kerberos5/lib/libhdb/Makefile =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- /usr/src/kerberos5/lib/libhdb/Makefile (revision 291443) +++ /usr/src/kerberos5/lib/libhdb/Makefile (working copy) @@ -1,7 +1,7 @@ # $FreeBSD$ =20 LIB=3D hdb -LDFLAGS=3D -Wl,--no-undefined ${LDAPLDFLAGS} +LDFLAGS=3D -Wl,--no-undefined ${LDAPLDFLAGS} = -L/usr/obj/usr/src/tmp/usr/lib VERSION_MAP=3D ${KRB5DIR}/lib/hdb/version-script.map LIBADD=3D asn1 com_err krb5 roken sqlite3 LDADD=3D ${LDAPLDADD} Index: /usr/src/kerberos5/lib/libkrb5/Makefile =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- /usr/src/kerberos5/lib/libkrb5/Makefile (revision 291443) +++ /usr/src/kerberos5/lib/libkrb5/Makefile (working copy) @@ -1,7 +1,7 @@ # $FreeBSD$ =20 LIB=3D krb5 -LDFLAGS=3D -Wl,--no-undefined +LDFLAGS=3D -Wl,--no-undefined -L/usr/obj/usr/src/tmp/usr/lib VERSION_MAP=3D ${KRB5DIR}/lib/krb5/version-script.map LIBADD=3D asn1 com_err crypt crypto hx509 roken wind heimbase = heimipcc =20 Without those -L/usr/obj/usr/src/tmp/usr/lib additions the results were = that the following were not found: -lprivateheimipcc and -lprivatesqlite3 See below: --- libkrb5.so.11.full --- building shared library libkrb5.so.11 /usr/local/bin/powerpc64-portbld-freebsd11.0-gcc -Wl,--no-undefined = -Wl,--version-script=3D/usr/src/kerberos5/lib/libkrb5/../../../crypto/heim= dal/lib/krb5/version- script.map -fstack-protector-strong -shared -Wl,-x -Wl,--fatal-warnings = -Wl,--warn-shared-textrel -o libkrb5.so.11.full = -Wl,-soname,libkrb5.so.11 . . . -lasn1 -lcom_err -lcrypt -lcrypto = -lhx509 -lroken -lwind -lheimbase -lprivateheimipcc /usr/local/bin/powerpc64-freebsd-ld: cannot find -lprivateheimipcc collect2: error: ld returned 1 exit status *** [libkrb5.so.11.full] Error code 1 and --- kerberos5/lib/libhdb__L --- /usr/local/bin/powerpc64-portbld-freebsd11.0-gcc -Wl,--no-undefined = -Wl,--version-script=3D/usr/src/kerberos5/lib/libhdb/../../../crypto/heimd= al/lib/hdb/version-s cript.map -fstack-protector-strong -shared -Wl,-x -Wl,--fatal-warnings = -Wl,--warn-shared-textrel -o libhdb.so.11.full -Wl,-soname,libhdb.so.11 = . . . -lasn1 -lcom_err -lkrb5 -lroken -lprivatesqlite3 -lpthread . . . --- kerberos5/lib/libhdb__L --- --- libhdb.so.11.full --- /usr/local/bin/powerpc64-freebsd-ld: cannot find -lprivatesqlite3 collect2: error: ld returned 1 exit status *** [libhdb.so.11.full] Error code 1 With the 2 -L/usr/obj/usr/src/tmp/usr/lib additions the build gets well = past head/kerberos5 . Context details if you care: > # freebsd-version -ku; uname -aKU > 11.0-CURRENT > 11.0-CURRENT > FreeBSD FBSDG5C0 11.0-CURRENT FreeBSD 11.0-CURRENT #12 r281630M: Sat = Apr 18 01:15:13 PDT 2015 = root@FBSDG5C0:/usr/obj/usr/src/sys/GENERIC64vtsc-NODEBUG powerpc = 1100070 1100070 I am attempting an update after having been away from the PowerMacs for = months. > # svnlite info /usr/src > Path: /usr/src > Working Copy Root Path: /usr/src > URL: https://svn0.us-west.freebsd.org/base/head > Relative URL: ^/head > Repository Root: https://svn0.us-west.freebsd.org/base > Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f > Revision: 291443 > Node Kind: directory > Schedule: normal > Last Changed Author: nwhitehorn > Last Changed Rev: 291442 > Last Changed Date: 2015-11-28 23:16:08 -0800 (Sat, 28 Nov 2015) > make -j 8 WITH_FAST_DEPEND=3D CROSS_TOOLCHAIN=3Dpowerpc64-gcc \ > WITH_LIBCPLUSPLUS=3D \ > WITHOUT_CLANG_BOOTSTRAP=3D WITH_CLANG=3D WITH_CLANG_IS_CC=3D \ > WITH_LLDB=3D \ > WITHOUT_GCC_BOOTSTRAP=3D WITHOUT_GCC=3D WITHOUT_GNUCXX=3D \ > WITHOUT_BOOT=3D \ > WITHOUT_LIB32=3D \ > buildworld buildkernel \ > KERNCONF=3DGENERIC64vtsc-NODEBUG \ > TARGET=3Dpowerpc TARGET_ARCH=3Dpowerpc64 powerpc64-gcc had been updated to be modern first: it is from . . . > # svnlite info /usr/ports > Path: /usr/ports > Working Copy Root Path: /usr/ports > URL: https://svn0.us-west.freebsd.org/ports/head > Relative URL: ^/head > Repository Root: https://svn0.us-west.freebsd.org/ports > Repository UUID: 35697150-7ecd-e111-bb59-0022644237b5 > Revision: 402562 > Node Kind: directory > Schedule: normal > Last Changed Author: rene > Last Changed Rev: 402562 > Last Changed Date: 2015-11-28 15:08:03 -0800 (Sat, 28 Nov 2015) =3D=3D=3D Mark Millard markmi at dsl-only.net From owner-freebsd-ppc@freebsd.org Sun Nov 29 20:43:00 2015 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 D780EA3B981 for ; Sun, 29 Nov 2015 20:43:00 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-211-151.reflexion.net [208.70.211.151]) (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 8A1131CE5 for ; Sun, 29 Nov 2015 20:42:59 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 7061 invoked from network); 29 Nov 2015 20:42:57 -0000 Received: from unknown (HELO mail-cs-02.app.dca.reflexion.local) (10.81.19.2) by 0 (rfx-qmail) with SMTP; 29 Nov 2015 20:42:57 -0000 Received: by mail-cs-02.app.dca.reflexion.local (Reflexion email security v7.80.0) with SMTP; Sun, 29 Nov 2015 15:42:58 -0500 (EST) Received: (qmail 2427 invoked from network); 29 Nov 2015 20:42:58 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with SMTP; 29 Nov 2015 20:42:58 -0000 X-No-Relay: not in my network X-No-Relay: not in my network Received: from [192.168.1.8] (c-76-115-7-162.hsd1.or.comcast.net [76.115.7.162]) by iron2.pdx.net (Postfix) with ESMTPSA id 7127D1C4400; Sun, 29 Nov 2015 12:42:53 -0800 (PST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\)) Subject: - j 6 buildworld: -lcapsicum use before libcapsicum.so.0 /usr/obj/usr/src/tmp/lib/ install From: Mark Millard In-Reply-To: <106D9CB0-D9AE-4463-A03E-3AB16583CDA7@dsl-only.net> Date: Sun, 29 Nov 2015 12:42:56 -0800 Content-Transfer-Encoding: quoted-printable Message-Id: References: <01BA3FF2-F362-48FA-B9E2-112E05CC00ED@dsl-only.net> <6AA244B9-DE60-4D8B-A08E-AADD73F9D856@dsl-only.net> <106D9CB0-D9AE-4463-A03E-3AB16583CDA7@dsl-only.net> To: FreeBSD PowerPC ML , FreeBSD Toolchain X-Mailer: Apple Mail (2.2104) X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Nov 2015 20:43:01 -0000 This is a -j 6 buildworld context. In the following sequence the -lcapsicum use when linking = libcasper.so.0.full does not use /usr/obj/usr/src/tmp/lib/libcapsicum.so = because that file and the link to it at = /usr/obj/usr/src/tmp/usr/lib/libcapsicum.so are only created (installed) = later. (See the sequence later below.) This can lead to use of /lib/libcapsicum.so instead if it is found, = which for my context it is. In my case of updating from 11.0-CURRENT = from back on 2015-Apr-18 /lib/libcapsicum.so use ends up complaining = about undefined references, such as to nvlist_getf_binary that existed = back then but do not now. That is what exposed the time-order problem. > --- all_subdir_libcasper --- > /usr/local/bin/powerpc64-portbld-freebsd11.0-gcc = -L/usr/obj/usr/src/tmp/usr/lib/. -L/usr/obj/usr/src/lib/libc++/. = -L/usr/lib/. -fstack-protector-strong -shared -Wl,-x = -Wl,--fatal-warnings -Wl,--warn-shared-textrel -o libcasper.so.0.full = -Wl,-soname,libcasper.so.0 `NM=3D'/usr/local/powerpc64-freebsd/bin/nm' = NMFLAGS=3D'' lorder libcasper.So | tsort -q` -lcapsicum -lnv -lpjdlog . . . > =3D=3D=3D> lib/libcapsicum (install) > --- _libinstall --- > --- _INCSINS --- > --- _libinstall --- > sh /usr/src/tools/install.sh -C -o root -g wheel -m 444 = libcapsicum.a /usr/obj/usr/src/tmp/usr/lib/ > --- _INCSINS --- > sh /usr/src/tools/install.sh -C -o root -g wheel -m 444 = /usr/src/lib/libcapsicum/libcapsicum.h = /usr/src/lib/libcapsicum/libcapsicum_dns.h = /usr/src/lib/libcapsicum/libcapsicum_grp.h = /usr/src/lib/libcapsicum/libcapsicum_pwd.h = /usr/src/lib/libcapsicum/libcapsicum_random.h = /usr/src/lib/libcapsicum/libcapsicum_service.h = /usr/src/lib/libcapsicum/libcapsicum_sysctl.h = /usr/obj/usr/src/tmp/usr/include/ > --- _libinstall --- > sh /usr/src/tools/install.sh -s -o root -g wheel -m 444 = libcapsicum.so.0 /usr/obj/usr/src/tmp/lib/ > sh /usr/src/tools/install.sh -T debug -o root -g wheel -m 444 = libcapsicum.so.0.debug /usr/obj/usr/src/tmp/usr/lib/debug/lib/ > sh /usr/src/tools/install.sh -l rs = /usr/obj/usr/src/tmp/lib/libcapsicum.so.0 = /usr/obj/usr/src/tmp/usr/lib/libcapsicum.so The -L's ending with /.'s are from my /etc/src.conf . They are = associated with trying to self-build on a powerpc64 PowerMac using only = powerpc64-xtoolchain-gcc's powerpc64-gcc WITH_LIBCPLUSPLUS: = powerpc64-gcc is acting as both the host toolchain and the = CROSS_TOOLCHAIN. No 4.2.1 gcc is present. I know this is not a usual way = of doing things. There may be better ways. But if I manage to expose = some missing dependency tracking some good came of it. The make command was: > make -j 6 WITH_FAST_DEPEND=3D CROSS_TOOLCHAIN=3Dpowerpc64-gcc = WITH_LIBCPLUSPLUS=3D WITHOUT_CLANG_BOOTSTRAP=3D WITH_CLANG=3D = WITH_CLANG_IS_CC=3D WITH_LLDB=3D WITHOUT_GCC_BOOTSTRAP=3D WITHOUT_GCC=3D = WITHOUT_GNUCXX=3D WITHOUT_BOOT=3D WITHOUT_LIB32=3D buildworld = buildkernel KERNCONF=3DGENERIC64vtsc-NODEBUG TARGET=3Dpowerpc = TARGET_ARCH=3Dpowerpc64 Context details if you care: > # freebsd-version -ku; uname -aKU > 11.0-CURRENT > 11.0-CURRENT > FreeBSD FBSDG5C0 11.0-CURRENT FreeBSD 11.0-CURRENT #12 r281630M: Sat = Apr 18 01:15:13 PDT 2015 = root@FBSDG5C0:/usr/obj/usr/src/sys/GENERIC64vtsc-NODEBUG powerpc = 1100070 1100070 I am attempting an update after having been away from the PowerMacs for = months. > # svnlite info /usr/src > Path: /usr/src > Working Copy Root Path: /usr/src > URL: https://svn0.us-west.freebsd.org/base/head > Relative URL: ^/head > Repository Root: https://svn0.us-west.freebsd.org/base > Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f > Revision: 291443 > Node Kind: directory > Schedule: normal > Last Changed Author: nwhitehorn > Last Changed Rev: 291442 > Last Changed Date: 2015-11-28 23:16:08 -0800 (Sat, 28 Nov 2015) > # more /etc/src.conf > NO_WERROR=3D > WITH_DEBUG=3D > WITH_DEBUG_FILES=3D > MALLOC_PRODUCTION=3D > CC=3D/usr/local/bin/powerpc64-portbld-freebsd11.0-gcc > CXX=3D/usr/local/bin/powerpc64-portbld-freebsd11.0-g++ > CPP=3D/usr/local/bin/powerpc64-portbld-freebsd11.0-cpp > CROSS_BINUTILS_PREFIX=3D/usr/local/powerpc64-freebsd/bin/ > X_COMPILER_TYPE=3Dgcc > DEPFLAGS+=3D-isystem /usr/obj/usr/src/tmp/usr/include/. = -I/usr/obj/usr/src/tmp/usr/include/c++/v1/. -I/usr/include/c++/v1/. > L/usr/obj/usr/src/tmp/usr/lib/lib32/. > CFLAGS+=3D-isystem /usr/obj/usr/src/tmp/usr/include/. = -L/usr/obj/usr/src/tmp/usr/lib/. -L/usr/obj/usr/src/tmp/lib/. > LDFLAGS+=3D-L/usr/obj/usr/src/tmp/usr/lib/. = -L/usr/obj/usr/src/tmp/lib/. > CXXFLAGS+=3D-isystem /usr/obj/usr/src/tmp/usr/include/. = -I/usr/obj/usr/src/tmp/usr/include/c++/v1/. -std=3Dgnu++11 = -L/usr/obj/usr/src/lib/libc++/. > LDFLAGS+=3D-L/usr/obj/usr/src/lib/libc++/. > CXXFLAGS+=3D-I/usr/include/c++/v1/. -std=3Dgnu++11 -L/usr/lib/. > LDFLAGS+=3D-L/usr/lib/. > # svnlite info /usr/ports/ > Path: /usr/ports > Working Copy Root Path: /usr/ports > URL: https://svn0.us-west.freebsd.org/ports/head > Relative URL: ^/head > Repository Root: https://svn0.us-west.freebsd.org/ports > Repository UUID: 35697150-7ecd-e111-bb59-0022644237b5 > Revision: 402562 > Node Kind: directory > Schedule: normal > Last Changed Author: rene > Last Changed Rev: 402562 > Last Changed Date: 2015-11-28 15:08:03 -0800 (Sat, 28 Nov 2015) =3D=3D=3D Mark Millard markmi at dsl-only.net From owner-freebsd-ppc@freebsd.org Mon Nov 30 04:08:03 2015 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 2BAA0A3BF31 for ; Mon, 30 Nov 2015 04:08:03 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-211-152.reflexion.net [208.70.211.152]) (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 E0D051EE0 for ; Mon, 30 Nov 2015 04:08:02 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 12424 invoked from network); 30 Nov 2015 04:08:00 -0000 Received: from unknown (HELO mail-cs-01.app.dca.reflexion.local) (10.81.19.1) by 0 (rfx-qmail) with SMTP; 30 Nov 2015 04:08:00 -0000 Received: by mail-cs-01.app.dca.reflexion.local (Reflexion email security v7.80.0) with SMTP; Sun, 29 Nov 2015 23:08:02 -0500 (EST) Received: (qmail 13182 invoked from network); 30 Nov 2015 04:08:02 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with SMTP; 30 Nov 2015 04:08:02 -0000 X-No-Relay: not in my network X-No-Relay: not in my network Received: from [192.168.1.8] (c-76-115-7-162.hsd1.or.comcast.net [76.115.7.162]) by iron2.pdx.net (Postfix) with ESMTPSA id 6E2E7B1E001; Sun, 29 Nov 2015 20:07:54 -0800 (PST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\)) Subject: More 11.0-CURRENT: without adding -lmd linking various programs are getting undefined references From: Mark Millard In-Reply-To: Date: Sun, 29 Nov 2015 20:07:59 -0800 Content-Transfer-Encoding: quoted-printable Message-Id: <8AF435C1-9F0B-4466-9210-A54D7210B30C@dsl-only.net> References: <01BA3FF2-F362-48FA-B9E2-112E05CC00ED@dsl-only.net> <6AA244B9-DE60-4D8B-A08E-AADD73F9D856@dsl-only.net> <106D9CB0-D9AE-4463-A03E-3AB16583CDA7@dsl-only.net> To: FreeBSD PowerPC ML , FreeBSD Toolchain X-Mailer: Apple Mail (2.2104) X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Nov 2015 04:08:03 -0000 Without the following explicit references to (lib)md or -lmd for = programs (possibly indirectly) using libmd I get link failures during = the build, such as: /usr/obj/usr/src/tmp/usr/lib/./libulog.so: undefined reference to = `_libmd_SHA1_Init' /usr/obj/usr/src/tmp/usr/lib/./libulog.so: undefined reference to = `_libmd_SHA1_Update' /usr/obj/usr/src/tmp/usr/lib/./libulog.so: undefined reference to = `_libmd_SHA1_Final' . . . /usr/obj/usr/src/tmp/usr/lib/./libzfs.so: undefined reference to = `_libmd_SHA256_Update' /usr/obj/usr/src/tmp/usr/lib/./libzfs.so: undefined reference to = `_libmd_SHA256_Final' /usr/obj/usr/src/tmp/usr/lib/./libzfs.so: undefined reference to = `_libmd_SHA256_Init' . . . I am attempting to build for updating an 2015-Apr-18 vintage = 11.0-CURRENT, so it starts from a context back from before the renames = to use the __libdm_ prefixes on the names. So for me no implicit = bindings are being provided. Some of my temporary(?) workarounds for this are: Index: /usr/src/libexec/ulog-helper/Makefile =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- /usr/src/libexec/ulog-helper/Makefile (revision 291443) +++ /usr/src/libexec/ulog-helper/Makefile (working copy) @@ -5,6 +5,6 @@ BINMODE=3D4555 MAN=3D =20 -LIBADD=3D ulog +LIBADD=3D ulog md Index: /usr/src/cddl/sbin/zfs/Makefile =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- /usr/src/cddl/sbin/zfs/Makefile (revision 291443) +++ /usr/src/cddl/sbin/zfs/Makefile (working copy) @@ -24,6 +24,6 @@ =20 DPADD=3D ${LIBGEOM} ${LIBJAIL} ${LIBNVPAIR} ${LIBUMEM} \ ${LIBUTIL} ${LIBUUTIL} ${LIBZFS_CORE} ${LIBZFS} -LDADD=3D -lgeom -ljail -lnvpair -lumem -lutil -luutil -lzfs_core -lzfs +LDADD=3D -lmd -lgeom -ljail -lnvpair -lumem -lutil -luutil -lzfs_core = -lzfs =20 .include Index: /usr/src/cddl/sbin/zpool/Makefile =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- /usr/src/cddl/sbin/zpool/Makefile (revision 291443) +++ /usr/src/cddl/sbin/zpool/Makefile (working copy) @@ -29,6 +29,6 @@ =20 DPADD=3D ${LIBAVL} ${LIBGEOM} ${LIBNVPAIR} \ ${LIBUMEM} ${LIBUTIL} ${LIBUUTIL} ${LIBZFS_CORE} ${LIBZFS} -LDADD=3D -lavl -lgeom -lnvpair -lumem -lutil -luutil -lzfs_core -lzfs +LDADD=3D -lmd -lavl -lgeom -lnvpair -lumem -lutil -luutil -lzfs_core = -lzfs =20 .include Without those the results were: --- ulog-helper.full --- /usr/local/bin/powerpc64-portbld-freebsd11.0-gcc -O2 -pipe -isystem = /usr/obj/usr/src/tmp/usr/include/. -L/usr/obj/usr/src/tmp/usr/lib/. = -L/usr/obj/usr/src/tmp/li b/. -g -std=3Dgnu99 -fstack-protector-strong -Wsystem-headers -Wall = -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes = -Wmissing-prototypes -Wpointer-ari th -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow = -Wunused-parameter -Wcast-align -Wchar-subscripts -Winline = -Wnested-externs -Wredundant-decls -Wol d-style-definition -Wno-pointer-sign -Wformat=3D2 -Wno-format-extra-args = -L/usr/obj/usr/src/tmp/usr/lib/. -L/usr/obj/usr/src/tmp/lib/. = -L/usr/obj/usr/src/lib/libc ++/. -L/usr/lib/. -o ulog-helper.full ulog-helper.o -lulog . . . --- all_subdir_libexec --- /usr/obj/usr/src/tmp/usr/lib/./libulog.so: undefined reference to = `_libmd_SHA1_Init' /usr/obj/usr/src/tmp/usr/lib/./libulog.so: undefined reference to = `_libmd_SHA1_Update' /usr/obj/usr/src/tmp/usr/lib/./libulog.so: undefined reference to = `_libmd_SHA1_Final' collect2: error: ld returned 1 exit status . . . --- all_subdir_cddl --- /usr/local/bin/powerpc64-portbld-freebsd11.0-gcc -O2 -pipe -isystem = /usr/obj/usr/src/tmp/usr/include/. -L/usr/obj/usr/src/tmp/usr/lib/. = -L/usr/obj/usr/src/tmp/li b/. = -I/usr/src/cddl/sbin/zfs/../../../cddl/contrib/opensolaris/lib/libzpool/co= mmon -I/usr/src/cddl/sbin/zfs/../../../cddl/compat/opensolaris/include = -I/usr/src/c ddl/sbin/zfs/../../../cddl/compat/opensolaris/lib/libumem = -I/usr/src/cddl/sbin/zfs/../../../sys/cddl/compat/opensolaris = -I/usr/src/cddl/sbin/zfs/../../../cddl/co ntrib/opensolaris/head = -I/usr/src/cddl/sbin/zfs/../../../cddl/contrib/opensolaris/lib/libuutil/co= mmon -I/usr/src/cddl/sbin/zfs/../../../cddl/contrib/opensolaris/ lib/libzfs/common = -I/usr/src/cddl/sbin/zfs/../../../cddl/contrib/opensolaris/lib/libzfs_core= /common -I/usr/src/cddl/sbin/zfs/../../../cddl/contrib/opensolaris/li b/libumem/common = -I/usr/src/cddl/sbin/zfs/../../../cddl/contrib/opensolaris/lib/libnvpair = -I/usr/src/cddl/sbin/zfs/../../../sys/cddl/contrib/opensolaris/uts/comm on = -I/usr/src/cddl/sbin/zfs/../../../sys/cddl/contrib/opensolaris/uts/common/= fs/zfs = -I/usr/src/cddl/sbin/zfs/../../../sys/cddl/contrib/opensolaris/uts/common/= sys = -I/usr/src/cddl/sbin/zfs/../../../sys/cddl/contrib/opensolaris/common/zfs = -DNEED_SOLARIS_BOOLEAN -g -std=3Dgnu99 -fstack-protector-strong = -Wno-pointer-sign -Wno-u nknown-pragmas -L/usr/obj/usr/src/tmp/usr/lib/. = -L/usr/obj/usr/src/tmp/lib/. -L/usr/obj/usr/src/lib/libc++/. = -L/usr/lib/. -o zfs.full zfs_main.o zfs_iter.o -lg eom -ljail -lnvpair -lumem -lutil -luutil -lzfs_core -lzfs . . . --- all_subdir_cddl --- /usr/obj/usr/src/tmp/usr/lib/./libzfs.so: undefined reference to = `_libmd_SHA256_Update' /usr/obj/usr/src/tmp/usr/lib/./libzfs.so: undefined reference to = `_libmd_SHA256_Final' /usr/obj/usr/src/tmp/usr/lib/./libzfs.so: undefined reference to = `_libmd_SHA256_Init' collect2: error: ld returned 1 exit status *** [zfs.full] Error code 1 . . . --- all_subdir_sbin --- ../sys/cddl/contrib/opensolaris/uts/common = -I/usr/src/cddl/sbin/zpool/../../../sys/cddl/contrib/opensolaris/uts/commo= n/fs/zfs -I/usr/src/cddl/sbin/zpool/../../.. /sys/cddl/contrib/opensolaris/uts/common/sys = -I/usr/src/cddl/sbin/zpool/../../../cddl/contrib/opensolaris/lib/libzpool/= common -I/usr/src/cddl/sbin/zpool/../../.. /cddl/contrib/opensolaris/cmd/stat/common -DNEED_SOLARIS_BOOLEAN -g = -std=3Dgnu99 -fstack-protector-strong -Wno-pointer-sign = -Wno-unknown-pragmas -L/usr/obj/usr/sr c/tmp/usr/lib/. -L/usr/obj/usr/src/tmp/lib/. = -L/usr/obj/usr/src/lib/libc++/. -L/usr/lib/. -o zpool.full zpool_main.o = zpool_vdev.o zpool_iter.o zpool_util.o zfs_c omutil.o timestamp.o -lavl -lgeom -lnvpair -lumem -lutil -luutil = -lzfs_core -lzfs . . . --- all_subdir_cddl --- /usr/obj/usr/src/tmp/usr/lib/./libzfs.so: undefined reference to = `_libmd_SHA256_Update' /usr/obj/usr/src/tmp/usr/lib/./libzfs.so: undefined reference to = `_libmd_SHA256_Final' /usr/obj/usr/src/tmp/usr/lib/./libzfs.so: undefined reference to = `_libmd_SHA256_Init' collect2: error: ld returned 1 exit status *** [zpool.full] Error code 1 The -L's ending with /.'s are from my /etc/src.conf . They are = associated with trying to self-build on a powerpc64 PowerMac using only = powerpc64-xtoolchain-gcc's powerpc64-gcc and with WITH_LIBCPLUSPLUS: = powerpc64-gcc is acting as both the host toolchain and the = CROSS_TOOLCHAIN. No 4.2.1 gcc is present. I know this is not a usual way = of doing things. There may be better ways. But if I manage to expose = some missing dependency tracking some good came of it. Another example is zinject. I'm still going through them. The make commands were: > make -j 6 -DNO_CLEAN WITH_FAST_DEPEND=3D CROSS_TOOLCHAIN=3Dpowerpc64-gcc= WITH_LIBCPLUSPLUS=3D WITHOUT_CLANG_BOOTSTRAP=3D WITH_CLANG=3D = WITH_CLANG_IS_CC=3D WITH_LLDB=3D WITHOUT_GCC_BOOTSTRAP=3D WITHOUT_GCC=3D = WITHOUT_GNUCXX=3D WITHOUT_BOOT=3D WITHOUT_LIB32=3D buildworld = buildkernel KERNCONF=3DGENERIC64vtsc-NODEBUG TARGET=3Dpowerpc = TARGET_ARCH=3Dpowerpc64 (The NO_CLEAN is from after the first build problem and is to avoid long = rebuild times to get back to the same point.) Context details if you care: > # freebsd-version -ku; uname -aKU > 11.0-CURRENT > 11.0-CURRENT > FreeBSD FBSDG5C0 11.0-CURRENT FreeBSD 11.0-CURRENT #12 r281630M: Sat = Apr 18 01:15:13 PDT 2015 = root@FBSDG5C0:/usr/obj/usr/src/sys/GENERIC64vtsc-NODEBUG powerpc = 1100070 1100070 I am attempting an update after having been away from the PowerMacs for = months. > # svnlite info /usr/src > Path: /usr/src > Working Copy Root Path: /usr/src > URL: https://svn0.us-west.freebsd.org/base/head > Relative URL: ^/head > Repository Root: https://svn0.us-west.freebsd.org/base > Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f > Revision: 291443 > Node Kind: directory > Schedule: normal > Last Changed Author: nwhitehorn > Last Changed Rev: 291442 > Last Changed Date: 2015-11-28 23:16:08 -0800 (Sat, 28 Nov 2015) > # more /etc/src.conf > NO_WERROR=3D > WITH_DEBUG=3D > WITH_DEBUG_FILES=3D > MALLOC_PRODUCTION=3D > CC=3D/usr/local/bin/powerpc64-portbld-freebsd11.0-gcc > CXX=3D/usr/local/bin/powerpc64-portbld-freebsd11.0-g++ > CPP=3D/usr/local/bin/powerpc64-portbld-freebsd11.0-cpp > CROSS_BINUTILS_PREFIX=3D/usr/local/powerpc64-freebsd/bin/ > X_COMPILER_TYPE=3Dgcc > DEPFLAGS+=3D-isystem /usr/obj/usr/src/tmp/usr/include/. = -I/usr/obj/usr/src/tmp/usr/include/c++/v1/. -I/usr/include/c++/v1/. > L/usr/obj/usr/src/tmp/usr/lib/lib32/. > CFLAGS+=3D-isystem /usr/obj/usr/src/tmp/usr/include/. = -L/usr/obj/usr/src/tmp/usr/lib/. -L/usr/obj/usr/src/tmp/lib/. > LDFLAGS+=3D-L/usr/obj/usr/src/tmp/usr/lib/. = -L/usr/obj/usr/src/tmp/lib/. > CXXFLAGS+=3D-isystem /usr/obj/usr/src/tmp/usr/include/. = -I/usr/obj/usr/src/tmp/usr/include/c++/v1/. -std=3Dgnu++11 = -L/usr/obj/usr/src/lib/libc++/. > LDFLAGS+=3D-L/usr/obj/usr/src/lib/libc++/. > CXXFLAGS+=3D-I/usr/include/c++/v1/. -std=3Dgnu++11 -L/usr/lib/. > LDFLAGS+=3D-L/usr/lib/. > # svnlite info /usr/ports/ > Path: /usr/ports > Working Copy Root Path: /usr/ports > URL: https://svn0.us-west.freebsd.org/ports/head > Relative URL: ^/head > Repository Root: https://svn0.us-west.freebsd.org/ports > Repository UUID: 35697150-7ecd-e111-bb59-0022644237b5 > Revision: 402562 > Node Kind: directory > Schedule: normal > Last Changed Author: rene > Last Changed Rev: 402562 > Last Changed Date: 2015-11-28 15:08:03 -0800 (Sat, 28 Nov 2015) =3D=3D=3D Mark Millard markmi at dsl-only.net From owner-freebsd-ppc@freebsd.org Mon Nov 30 06:11:08 2015 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 14FFAA316ED for ; Mon, 30 Nov 2015 06:11:08 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-211-151.reflexion.net [208.70.211.151]) (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 BC8361290 for ; Mon, 30 Nov 2015 06:11:06 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 26657 invoked from network); 30 Nov 2015 06:11:06 -0000 Received: from unknown (HELO mail-cs-02.app.dca.reflexion.local) (10.81.19.2) by 0 (rfx-qmail) with SMTP; 30 Nov 2015 06:11:06 -0000 Received: by mail-cs-02.app.dca.reflexion.local (Reflexion email security v7.80.0) with SMTP; Mon, 30 Nov 2015 01:11:07 -0500 (EST) Received: (qmail 29629 invoked from network); 30 Nov 2015 06:11:06 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with SMTP; 30 Nov 2015 06:11:06 -0000 X-No-Relay: not in my network X-No-Relay: not in my network Received: from [192.168.1.8] (c-76-115-7-162.hsd1.or.comcast.net [76.115.7.162]) by iron2.pdx.net (Postfix) with ESMTPSA id CAB5BB1E001; Sun, 29 Nov 2015 22:10:58 -0800 (PST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\)) Subject: 11.0-CURRENT powerpc64 cont'd: without adding to LIBADD linking various programs are getting undefined references From: Mark Millard In-Reply-To: <8AF435C1-9F0B-4466-9210-A54D7210B30C@dsl-only.net> Date: Sun, 29 Nov 2015 22:11:04 -0800 Content-Transfer-Encoding: quoted-printable Message-Id: <693DFA8E-B19B-44E9-A0E7-C42B5DB7025B@dsl-only.net> References: <01BA3FF2-F362-48FA-B9E2-112E05CC00ED@dsl-only.net> <6AA244B9-DE60-4D8B-A08E-AADD73F9D856@dsl-only.net> <106D9CB0-D9AE-4463-A03E-3AB16583CDA7@dsl-only.net> <8AF435C1-9F0B-4466-9210-A54D7210B30C@dsl-only.net> To: FreeBSD PowerPC ML , FreeBSD Toolchain X-Mailer: Apple Mail (2.2104) X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Nov 2015 06:11:08 -0000 Note: After the below examples rescue had a much larger list of = Undefined References from various sources. At least for now I've given = up and not tried to track down what to add to get rescue to link. Explicit md references were used to avoid symbol problems in: /usr/src/cddl/sbin/zfs/Makefile /usr/src/cddl/sbin/zpool/Makefile /usr/src/cddl/usr.bin/zinject/Makefile /usr/src/cddl/usr.bin/zstreamdump/Makefile /usr/src/cddl/usr.bin/ztest/Makefile /usr/src/cddl/usr.sbin/zdb/Makefile /usr/src/cddl/usr.sbin/zhack/Makefile (A separate submittal covered the first few of those in more detail.) libcrypto use had similar issues, for example: > Index: /usr/src/sbin/atm/atmconfig/Makefile > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > --- /usr/src/sbin/atm/atmconfig/Makefile (revision 291443) > +++ /usr/src/sbin/atm/atmconfig/Makefile (working copy) > @@ -17,7 +17,7 @@ > .if !defined(RESCUE) && ${MK_BSNMP} !=3D "no" > CFLAGS+=3D -DWITH_BSNMP > SRCS+=3D oid.h atmconfig_device.c > -LIBADD+=3D bsnmp > +LIBADD+=3D crypto bsnmp > . if ${MK_DYNAMICROOT} =3D=3D "no" && ${MK_OPENSSL} !=3D "no" > LIBADD+=3D crypto > . endif Without the addition the result was: > --- all_subdir_sbin --- > /usr/local/bin/powerpc64-portbld-freebsd11.0-gcc -O2 -pipe -isystem = /usr/obj/usr/src/tmp/usr/include/. -L/usr/obj/usr/src/tmp/usr/lib/. = -L/usr/obj/usr/src/tmp/li > b/. -I/usr/obj/usr/src/sbin/atm/atmconfig -DWITH_BSNMP -g -std=3Dgnu99 = -fstack-protector-strong -Wsystem-headers -Wall -Wno-format-y2k -W = -Wno-unused-parameter -Ws > trict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type = -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wunused-parameter = -Wcast-align -Wchar-subscrip > ts -Winline -Wnested-externs -Wredundant-decls -Wold-style-definition = -Wno-pointer-sign -L/usr/obj/usr/src/tmp/usr/lib/. = -L/usr/obj/usr/src/tmp/lib/. -L/usr/obj > /usr/src/lib/libc++/. -L/usr/lib/. -o atmconfig.full main.o diag.o = natm.o atmconfig_device.o -lbsnmp . . . > --- all_subdir_sbin --- > /usr/local/bin/powerpc64-freebsd-ld: warning: libcrypto.so.8, needed = by /usr/obj/usr/src/tmp/usr/lib/./libbsnmp.so, not found (try using = -rpath or -rpath-link) > /usr/obj/usr/src/tmp/usr/lib/./libbsnmp.so: undefined reference to = `EVP_md5' > /usr/obj/usr/src/tmp/usr/lib/./libbsnmp.so: undefined reference to = `EVP_sha1' > /usr/obj/usr/src/tmp/usr/lib/./libbsnmp.so: undefined reference to = `EVP_DecryptInit' > /usr/obj/usr/src/tmp/usr/lib/./libbsnmp.so: undefined reference to = `EVP_DigestInit' > /usr/obj/usr/src/tmp/usr/lib/./libbsnmp.so: undefined reference to = `EVP_EncryptFinal' > /usr/obj/usr/src/tmp/usr/lib/./libbsnmp.so: undefined reference to = `EVP_EncryptUpdate' > /usr/obj/usr/src/tmp/usr/lib/./libbsnmp.so: undefined reference to = `EVP_DigestUpdate' > /usr/obj/usr/src/tmp/usr/lib/./libbsnmp.so: undefined reference to = `EVP_CIPHER_CTX_set_padding' > /usr/obj/usr/src/tmp/usr/lib/./libbsnmp.so: undefined reference to = `EVP_DigestFinal' > /usr/obj/usr/src/tmp/usr/lib/./libbsnmp.so: undefined reference to = `EVP_DecryptFinal' > /usr/obj/usr/src/tmp/usr/lib/./libbsnmp.so: undefined reference to = `EVP_aes_128_cfb128' > /usr/obj/usr/src/tmp/usr/lib/./libbsnmp.so: undefined reference to = `EVP_DecryptUpdate' > /usr/obj/usr/src/tmp/usr/lib/./libbsnmp.so: undefined reference to = `EVP_des_cbc' > /usr/obj/usr/src/tmp/usr/lib/./libbsnmp.so: undefined reference to = `EVP_EncryptInit' > /usr/obj/usr/src/tmp/usr/lib/./libbsnmp.so: undefined reference to = `EVP_MD_CTX_cleanup' > /usr/obj/usr/src/tmp/usr/lib/./libbsnmp.so: undefined reference to = `EVP_CIPHER_CTX_cleanup' > collect2: error: ld returned 1 exit status > *** [atmconfig.full] Error code 1 The -L's ending with /.'s are from my /etc/src.conf . They are = associated with trying to self-build on a powerpc64 PowerMac using only = powerpc64-xtoolchain-gcc's powerpc64-gcc WITH_LIBCPLUSPLUS: = powerpc64-gcc is acting as both the host toolchain and the = CROSS_TOOLCHAIN. No 4.2.1 gcc is present. I know this is not a usual way = of doing things. There may be better ways. But if I manage to expose = some missing dependency tracking some good came of it. And there was the need to add sbuf explicitly for its indirect use, such = as for: > Index: /usr/src/sbin/iscontrol/Makefile > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > --- /usr/src/sbin/iscontrol/Makefile (revision 291443) > +++ /usr/src/sbin/iscontrol/Makefile (working copy) > @@ -2,7 +2,7 @@ > =20 > SRCS=3D iscontrol.c pdu.c fsm.c config.c login.c auth_subr.c misc.c > PROG=3D iscontrol > -LIBADD=3D cam md > +LIBADD=3D sbuf cam md > S=3D ${.CURDIR}/../../sys > =20 > WARNS?=3D 3 Otherwise I got: > /usr/local/bin/powerpc64-portbld-freebsd11.0-gcc -O2 -pipe -isystem = /usr/obj/usr/src/tmp/usr/include/. -L/usr/obj/usr/src/tmp/usr/lib/. = -L/usr/obj/usr/src/tmp/li > b/. -I/usr/src/sbin/iscontrol/../../sys -g -std=3Dgnu99 = -fstack-protector-strong -Wsystem-headers -Wall -Wno-format-y2k -W = -Wno-unused-parameter -Wstrict-prototype > s -Wmissing-prototypes -Wpointer-arith -Wno-uninitialized = -Wno-pointer-sign -L/usr/obj/usr/src/tmp/usr/lib/. = -L/usr/obj/usr/src/tmp/lib/. -L/usr/obj/usr/src/lib > /libc++/. -L/usr/lib/. -o iscontrol.full iscontrol.o pdu.o fsm.o = config.o login.o auth_subr.o misc.o -lcam -lmd . . . > --- all_subdir_sbin --- > /usr/obj/usr/src/tmp/usr/lib/./libcam.so: undefined reference to = `sbuf_hexdump@FBSD_1.4' > collect2: error: ld returned 1 exit status Then there was both ssl and crypto for fetch: > Index: /usr/src/usr.bin/fetch/Makefile > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > --- /usr/src/usr.bin/fetch/Makefile (revision 291443) > +++ /usr/src/usr.bin/fetch/Makefile (working copy) > @@ -2,6 +2,6 @@ > =20 > PROG=3D fetch > CSTD?=3D c99 > -LIBADD=3D fetch > +LIBADD=3D ssl crypto fetch > =20 > .include without which I got: > --- all_subdir_usr.bin --- > /usr/local/bin/powerpc64-portbld-freebsd11.0-gcc -O2 -pipe -isystem = /usr/obj/usr/src/tmp/usr/include/. -L/usr/obj/usr/src/tmp/usr/lib/. = -L/usr/obj/usr/src/tmp/li > b/. -g -std=3Diso9899:1999 -fstack-protector-strong -Wsystem-headers = -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes = -Wmissing-prototypes -Wpoin > ter-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow = -Wunused-parameter -Wcast-align -Wchar-subscripts -Winline = -Wnested-externs -Wredundant-dec > ls -Wold-style-definition -Wno-pointer-sign = -L/usr/obj/usr/src/tmp/usr/lib/. -L/usr/obj/usr/src/tmp/lib/. = -L/usr/obj/usr/src/lib/libc++/. -L/usr/lib/. -o fetch. > full fetch.o -lfetch . . . > --- all_subdir_usr.bin --- > /usr/local/bin/powerpc64-freebsd-ld: warning: libssl.so.8, needed by = /usr/obj/usr/src/tmp/usr/lib/./libfetch.so, not found (try using -rpath = or -rpath-link) > /usr/local/bin/powerpc64-freebsd-ld: warning: libcrypto.so.8, needed = by /usr/obj/usr/src/tmp/usr/lib/./libfetch.so, not found (try using = -rpath or -rpath-link) > /usr/obj/usr/src/tmp/usr/lib/./libfetch.so: undefined reference to = `X509_LOOKUP_file' > /usr/obj/usr/src/tmp/usr/lib/./libfetch.so: undefined reference to = `ASN1_STRING_length' > /usr/obj/usr/src/tmp/usr/lib/./libfetch.so: undefined reference to = `SSL_get_error' > /usr/obj/usr/src/tmp/usr/lib/./libfetch.so: undefined reference to = `CRYPTO_free' > /usr/obj/usr/src/tmp/usr/lib/./libfetch.so: undefined reference to = `SSL_write' > /usr/obj/usr/src/tmp/usr/lib/./libfetch.so: undefined reference to = `SSLv23_client_method' > /usr/obj/usr/src/tmp/usr/lib/./libfetch.so: undefined reference to = `sk_value' > /usr/obj/usr/src/tmp/usr/lib/./libfetch.so: undefined reference to = `MD5_Final' > /usr/obj/usr/src/tmp/usr/lib/./libfetch.so: undefined reference to = `SSL_free' > /usr/obj/usr/src/tmp/usr/lib/./libfetch.so: undefined reference to = `X509_STORE_add_lookup' > /usr/obj/usr/src/tmp/usr/lib/./libfetch.so: undefined reference to = `SSL_CTX_use_certificate_chain_file' > /usr/obj/usr/src/tmp/usr/lib/./libfetch.so: undefined reference to = `SSL_set_fd' > /usr/obj/usr/src/tmp/usr/lib/./libfetch.so: undefined reference to = `X509_NAME_ENTRY_get_data' > /usr/obj/usr/src/tmp/usr/lib/./libfetch.so: undefined reference to = `SSL_CTX_set_verify' > /usr/obj/usr/src/tmp/usr/lib/./libfetch.so: undefined reference to = `X509_NAME_oneline' > /usr/obj/usr/src/tmp/usr/lib/./libfetch.so: undefined reference to = `ASN1_STRING_data' > /usr/obj/usr/src/tmp/usr/lib/./libfetch.so: undefined reference to = `X509_get_subject_name' > /usr/obj/usr/src/tmp/usr/lib/./libfetch.so: undefined reference to = `X509_get_issuer_name' > /usr/obj/usr/src/tmp/usr/lib/./libfetch.so: undefined reference to = `SSL_get_version' > /usr/obj/usr/src/tmp/usr/lib/./libfetch.so: undefined reference to = `SSL_library_init' > /usr/obj/usr/src/tmp/usr/lib/./libfetch.so: undefined reference to = `SSL_read' > /usr/obj/usr/src/tmp/usr/lib/./libfetch.so: undefined reference to = `X509_STORE_CTX_get_current_cert' > /usr/obj/usr/src/tmp/usr/lib/./libfetch.so: undefined reference to = `SSL_get_current_cipher' > /usr/obj/usr/src/tmp/usr/lib/./libfetch.so: undefined reference to = `SSL_CTX_ctrl' > /usr/obj/usr/src/tmp/usr/lib/./libfetch.so: undefined reference to = `SSL_new' > /usr/obj/usr/src/tmp/usr/lib/./libfetch.so: undefined reference to = `SSL_set_connect_state' > /usr/obj/usr/src/tmp/usr/lib/./libfetch.so: undefined reference to = `SSL_shutdown' > /usr/obj/usr/src/tmp/usr/lib/./libfetch.so: undefined reference to = `GENERAL_NAMES_free' > /usr/obj/usr/src/tmp/usr/lib/./libfetch.so: undefined reference to = `SSL_CTX_new' > /usr/obj/usr/src/tmp/usr/lib/./libfetch.so: undefined reference to = `SSL_get_peer_certificate' > /usr/obj/usr/src/tmp/usr/lib/./libfetch.so: undefined reference to = `X509_NAME_get_entry' > /usr/obj/usr/src/tmp/usr/lib/./libfetch.so: undefined reference to = `SSL_CTX_load_verify_locations' > /usr/obj/usr/src/tmp/usr/lib/./libfetch.so: undefined reference to = `X509_get_ext_d2i' > /usr/obj/usr/src/tmp/usr/lib/./libfetch.so: undefined reference to = `X509_load_crl_file' > /usr/obj/usr/src/tmp/usr/lib/./libfetch.so: undefined reference to = `SSL_ctrl' > /usr/obj/usr/src/tmp/usr/lib/./libfetch.so: undefined reference to = `X509_STORE_set_flags' > /usr/obj/usr/src/tmp/usr/lib/./libfetch.so: undefined reference to = `SSL_CTX_use_PrivateKey_file' > /usr/obj/usr/src/tmp/usr/lib/./libfetch.so: undefined reference to = `X509_free' > /usr/obj/usr/src/tmp/usr/lib/./libfetch.so: undefined reference to = `X509_NAME_get_index_by_NID' > /usr/obj/usr/src/tmp/usr/lib/./libfetch.so: undefined reference to = `sk_num' > /usr/obj/usr/src/tmp/usr/lib/./libfetch.so: undefined reference to = `SSL_connect' > /usr/obj/usr/src/tmp/usr/lib/./libfetch.so: undefined reference to = `SSL_CTX_free' > /usr/obj/usr/src/tmp/usr/lib/./libfetch.so: undefined reference to = `SSL_load_error_strings' > /usr/obj/usr/src/tmp/usr/lib/./libfetch.so: undefined reference to = `SSL_CTX_get_cert_store' > /usr/obj/usr/src/tmp/usr/lib/./libfetch.so: undefined reference to = `MD5_Init' > /usr/obj/usr/src/tmp/usr/lib/./libfetch.so: undefined reference to = `SSL_CIPHER_get_name' > /usr/obj/usr/src/tmp/usr/lib/./libfetch.so: undefined reference to = `ERR_print_errors_fp' > /usr/obj/usr/src/tmp/usr/lib/./libfetch.so: undefined reference to = `MD5_Update' > /usr/obj/usr/src/tmp/usr/lib/./libfetch.so: undefined reference to = `ASN1_STRING_to_UTF8' > collect2: error: ld returned 1 exit status The make commands were: > make -j 6 -DNO_CLEAN WITH_FAST_DEPEND=3D CROSS_TOOLCHAIN=3Dpowerpc64-gcc= WITH_LIBCPLUSPLUS=3D WITHOUT_CLANG_BOOTSTRAP=3D WITH_CLANG=3D = WITH_CLANG_IS_CC=3D WITH_LLDB=3D WITHOUT_GCC_BOOTSTRAP=3D WITHOUT_GCC=3D = WITHOUT_GNUCXX=3D WITHOUT_BOOT=3D WITHOUT_LIB32=3D buildworld = buildkernel KERNCONF=3DGENERIC64vtsc-NODEBUG TARGET=3Dpowerpc = TARGET_ARCH=3Dpowerpc64 (The NO_CLEAN is from after the first build problem and is to avoid long = rebuild times to get back to the same point.) Context details if you care: > # freebsd-version -ku; uname -aKU > 11.0-CURRENT > 11.0-CURRENT > FreeBSD FBSDG5C0 11.0-CURRENT FreeBSD 11.0-CURRENT #12 r281630M: Sat = Apr 18 01:15:13 PDT 2015 = root@FBSDG5C0:/usr/obj/usr/src/sys/GENERIC64vtsc-NODEBUG powerpc = 1100070 1100070 I am attempting an update after having been away from the PowerMacs for = months. > # svnlite info /usr/src > Path: /usr/src > Working Copy Root Path: /usr/src > URL: https://svn0.us-west.freebsd.org/base/head > Relative URL: ^/head > Repository Root: https://svn0.us-west.freebsd.org/base > Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f > Revision: 291443 > Node Kind: directory > Schedule: normal > Last Changed Author: nwhitehorn > Last Changed Rev: 291442 > Last Changed Date: 2015-11-28 23:16:08 -0800 (Sat, 28 Nov 2015) > # more /etc/src.conf > NO_WERROR=3D > WITH_DEBUG=3D > WITH_DEBUG_FILES=3D > MALLOC_PRODUCTION=3D > CC=3D/usr/local/bin/powerpc64-portbld-freebsd11.0-gcc > CXX=3D/usr/local/bin/powerpc64-portbld-freebsd11.0-g++ > CPP=3D/usr/local/bin/powerpc64-portbld-freebsd11.0-cpp > CROSS_BINUTILS_PREFIX=3D/usr/local/powerpc64-freebsd/bin/ > X_COMPILER_TYPE=3Dgcc > DEPFLAGS+=3D-isystem /usr/obj/usr/src/tmp/usr/include/. = -I/usr/obj/usr/src/tmp/usr/include/c++/v1/. -I/usr/include/c++/v1/. > L/usr/obj/usr/src/tmp/usr/lib/lib32/. > CFLAGS+=3D-isystem /usr/obj/usr/src/tmp/usr/include/. = -L/usr/obj/usr/src/tmp/usr/lib/. -L/usr/obj/usr/src/tmp/lib/. > LDFLAGS+=3D-L/usr/obj/usr/src/tmp/usr/lib/. = -L/usr/obj/usr/src/tmp/lib/. > CXXFLAGS+=3D-isystem /usr/obj/usr/src/tmp/usr/include/. = -I/usr/obj/usr/src/tmp/usr/include/c++/v1/. -std=3Dgnu++11 = -L/usr/obj/usr/src/lib/libc++/. > LDFLAGS+=3D-L/usr/obj/usr/src/lib/libc++/. > CXXFLAGS+=3D-I/usr/include/c++/v1/. -std=3Dgnu++11 -L/usr/lib/. > LDFLAGS+=3D-L/usr/lib/. > # svnlite info /usr/ports/ > Path: /usr/ports > Working Copy Root Path: /usr/ports > URL: https://svn0.us-west.freebsd.org/ports/head > Relative URL: ^/head > Repository Root: https://svn0.us-west.freebsd.org/ports > Repository UUID: 35697150-7ecd-e111-bb59-0022644237b5 > Revision: 402562 > Node Kind: directory > Schedule: normal > Last Changed Author: rene > Last Changed Rev: 402562 > Last Changed Date: 2015-11-28 15:08:03 -0800 (Sat, 28 Nov 2015) =3D=3D=3D Mark Millard markmi at dsl-only.net From owner-freebsd-ppc@freebsd.org Mon Nov 30 06:42:19 2015 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 23856A31DF7 for ; Mon, 30 Nov 2015 06:42:19 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-211-151.reflexion.net [208.70.211.151]) (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 D47A51FCD for ; Mon, 30 Nov 2015 06:42:17 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 7930 invoked from network); 30 Nov 2015 06:42:19 -0000 Received: from unknown (HELO mail-cs-01.app.dca.reflexion.local) (10.81.19.1) by 0 (rfx-qmail) with SMTP; 30 Nov 2015 06:42:19 -0000 Received: by mail-cs-01.app.dca.reflexion.local (Reflexion email security v7.80.0) with SMTP; Mon, 30 Nov 2015 01:42:18 -0500 (EST) Received: (qmail 3957 invoked from network); 30 Nov 2015 06:42:18 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with SMTP; 30 Nov 2015 06:42:18 -0000 X-No-Relay: not in my network X-No-Relay: not in my network Received: from [192.168.1.8] (c-76-115-7-162.hsd1.or.comcast.net [76.115.7.162]) by iron2.pdx.net (Postfix) with ESMTPSA id E737BB1E001; Sun, 29 Nov 2015 22:42:09 -0800 (PST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\)) Subject: Re: 11.0-CURRENT powerpc64 cont'd: without adding to LIBADD linking various programs are getting undefined references From: Mark Millard In-Reply-To: <693DFA8E-B19B-44E9-A0E7-C42B5DB7025B@dsl-only.net> Date: Sun, 29 Nov 2015 22:42:15 -0800 Content-Transfer-Encoding: quoted-printable Message-Id: References: <01BA3FF2-F362-48FA-B9E2-112E05CC00ED@dsl-only.net> <6AA244B9-DE60-4D8B-A08E-AADD73F9D856@dsl-only.net> <106D9CB0-D9AE-4463-A03E-3AB16583CDA7@dsl-only.net> <8AF435C1-9F0B-4466-9210-A54D7210B30C@dsl-only.net> <693DFA8E-B19B-44E9-A0E7-C42B5DB7025B@dsl-only.net> To: FreeBSD PowerPC ML , FreeBSD Toolchain X-Mailer: Apple Mail (2.2104) X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Nov 2015 06:42:19 -0000 A top-post to make this new toolchain material easy to find. To skip to = the original material skip down to the "=3D =3D =3D" text. But you may = want to read the below for context first. pkg info reports: > powerpc64-binutils-2.25.1 GNU binutils for powerpc64 = cross-development > powerpc64-gcc-5.2.0 Cross GNU Compiler Collection for = powerpc64 I've been attempting to use only those, not the below compilers/tools. Also around are: > binutils-2.25.1 GNU binary tools > gcc49-4.9.4.s20151125_1 GNU Compiler Collection 4.9 There are no other C/C++ compiler ports present. The 2015-Apr-18 vintage 11.0-CURRENT I was trying to update has: > # clang --version > FreeBSD clang version 3.6.0 (tags/RELEASE_360/final 230434) 20150225 > Target: powerpc64-unknown-freebsd11.0 > Thread model: posix but does not have gcc 4.2.1 at all. powerpc64-gcc is linked to instead, = for example: > # gcc --version > gcc (FreeBSD Ports Collection for powerpc64) 5.2.0 > Copyright (C) 2015 Free Software Foundation, Inc. > This is free software; see the source for copying conditions. There = is NO > warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR = PURPOSE. gcc5 is not around because it and powerpc64-gcc-5.2.0 conflict on at = least one file. That is why it is gcc49 as the more general gcc port. This is a WITH_LIBCPLUSPLUS context. =3D =3D =3D The original material . . . =3D =3D =3D Note: After the below examples rescue had a much larger list of = Undefined References from various sources. At least for now I've given = up and not tried to track down what to add to get rescue to link. Explicit md references were used to avoid symbol problems in: /usr/src/cddl/sbin/zfs/Makefile /usr/src/cddl/sbin/zpool/Makefile /usr/src/cddl/usr.bin/zinject/Makefile /usr/src/cddl/usr.bin/zstreamdump/Makefile /usr/src/cddl/usr.bin/ztest/Makefile /usr/src/cddl/usr.sbin/zdb/Makefile /usr/src/cddl/usr.sbin/zhack/Makefile (A separate submittal covered the first few of those in more detail.) libcrypto use had similar issues, for example: > Index: /usr/src/sbin/atm/atmconfig/Makefile > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > --- /usr/src/sbin/atm/atmconfig/Makefile (revision 291443) > +++ /usr/src/sbin/atm/atmconfig/Makefile (working copy) > @@ -17,7 +17,7 @@ > .if !defined(RESCUE) && ${MK_BSNMP} !=3D "no" > CFLAGS+=3D -DWITH_BSNMP > SRCS+=3D oid.h atmconfig_device.c > -LIBADD+=3D bsnmp > +LIBADD+=3D crypto bsnmp > . if ${MK_DYNAMICROOT} =3D=3D "no" && ${MK_OPENSSL} !=3D "no" > LIBADD+=3D crypto > . endif Without the addition the result was: > --- all_subdir_sbin --- > /usr/local/bin/powerpc64-portbld-freebsd11.0-gcc -O2 -pipe -isystem = /usr/obj/usr/src/tmp/usr/include/. -L/usr/obj/usr/src/tmp/usr/lib/. = -L/usr/obj/usr/src/tmp/li > b/. -I/usr/obj/usr/src/sbin/atm/atmconfig -DWITH_BSNMP -g -std=3Dgnu99 = -fstack-protector-strong -Wsystem-headers -Wall -Wno-format-y2k -W = -Wno-unused-parameter -Ws > trict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type = -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wunused-parameter = -Wcast-align -Wchar-subscrip > ts -Winline -Wnested-externs -Wredundant-decls -Wold-style-definition = -Wno-pointer-sign -L/usr/obj/usr/src/tmp/usr/lib/. = -L/usr/obj/usr/src/tmp/lib/. -L/usr/obj > /usr/src/lib/libc++/. -L/usr/lib/. -o atmconfig.full main.o diag.o = natm.o atmconfig_device.o -lbsnmp . . . > --- all_subdir_sbin --- > /usr/local/bin/powerpc64-freebsd-ld: warning: libcrypto.so.8, needed = by /usr/obj/usr/src/tmp/usr/lib/./libbsnmp.so, not found (try using = -rpath or -rpath-link) > /usr/obj/usr/src/tmp/usr/lib/./libbsnmp.so: undefined reference to = `EVP_md5' > /usr/obj/usr/src/tmp/usr/lib/./libbsnmp.so: undefined reference to = `EVP_sha1' > /usr/obj/usr/src/tmp/usr/lib/./libbsnmp.so: undefined reference to = `EVP_DecryptInit' > /usr/obj/usr/src/tmp/usr/lib/./libbsnmp.so: undefined reference to = `EVP_DigestInit' > /usr/obj/usr/src/tmp/usr/lib/./libbsnmp.so: undefined reference to = `EVP_EncryptFinal' > /usr/obj/usr/src/tmp/usr/lib/./libbsnmp.so: undefined reference to = `EVP_EncryptUpdate' > /usr/obj/usr/src/tmp/usr/lib/./libbsnmp.so: undefined reference to = `EVP_DigestUpdate' > /usr/obj/usr/src/tmp/usr/lib/./libbsnmp.so: undefined reference to = `EVP_CIPHER_CTX_set_padding' > /usr/obj/usr/src/tmp/usr/lib/./libbsnmp.so: undefined reference to = `EVP_DigestFinal' > /usr/obj/usr/src/tmp/usr/lib/./libbsnmp.so: undefined reference to = `EVP_DecryptFinal' > /usr/obj/usr/src/tmp/usr/lib/./libbsnmp.so: undefined reference to = `EVP_aes_128_cfb128' > /usr/obj/usr/src/tmp/usr/lib/./libbsnmp.so: undefined reference to = `EVP_DecryptUpdate' > /usr/obj/usr/src/tmp/usr/lib/./libbsnmp.so: undefined reference to = `EVP_des_cbc' > /usr/obj/usr/src/tmp/usr/lib/./libbsnmp.so: undefined reference to = `EVP_EncryptInit' > /usr/obj/usr/src/tmp/usr/lib/./libbsnmp.so: undefined reference to = `EVP_MD_CTX_cleanup' > /usr/obj/usr/src/tmp/usr/lib/./libbsnmp.so: undefined reference to = `EVP_CIPHER_CTX_cleanup' > collect2: error: ld returned 1 exit status > *** [atmconfig.full] Error code 1 The -L's ending with /.'s are from my /etc/src.conf . They are = associated with trying to self-build on a powerpc64 PowerMac using only = powerpc64-xtoolchain-gcc's powerpc64-gcc WITH_LIBCPLUSPLUS: = powerpc64-gcc is acting as both the host toolchain and the = CROSS_TOOLCHAIN. No 4.2.1 gcc is present. I know this is not a usual way = of doing things. There may be better ways. But if I manage to expose = some missing dependency tracking some good came of it. And there was the need to add sbuf explicitly for its indirect use, such = as for: > Index: /usr/src/sbin/iscontrol/Makefile > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > --- /usr/src/sbin/iscontrol/Makefile (revision 291443) > +++ /usr/src/sbin/iscontrol/Makefile (working copy) > @@ -2,7 +2,7 @@ >=20 > SRCS=3D iscontrol.c pdu.c fsm.c config.c login.c auth_subr.c misc.c > PROG=3D iscontrol > -LIBADD=3D cam md > +LIBADD=3D sbuf cam md > S=3D ${.CURDIR}/../../sys >=20 > WARNS?=3D 3 Otherwise I got: > /usr/local/bin/powerpc64-portbld-freebsd11.0-gcc -O2 -pipe -isystem = /usr/obj/usr/src/tmp/usr/include/. -L/usr/obj/usr/src/tmp/usr/lib/. = -L/usr/obj/usr/src/tmp/li > b/. -I/usr/src/sbin/iscontrol/../../sys -g -std=3Dgnu99 = -fstack-protector-strong -Wsystem-headers -Wall -Wno-format-y2k -W = -Wno-unused-parameter -Wstrict-prototype > s -Wmissing-prototypes -Wpointer-arith -Wno-uninitialized = -Wno-pointer-sign -L/usr/obj/usr/src/tmp/usr/lib/. = -L/usr/obj/usr/src/tmp/lib/. -L/usr/obj/usr/src/lib > /libc++/. -L/usr/lib/. -o iscontrol.full iscontrol.o pdu.o fsm.o = config.o login.o auth_subr.o misc.o -lcam -lmd . . . > --- all_subdir_sbin --- > /usr/obj/usr/src/tmp/usr/lib/./libcam.so: undefined reference to = `sbuf_hexdump@FBSD_1.4' > collect2: error: ld returned 1 exit status Then there was both ssl and crypto for fetch: > Index: /usr/src/usr.bin/fetch/Makefile > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > --- /usr/src/usr.bin/fetch/Makefile (revision 291443) > +++ /usr/src/usr.bin/fetch/Makefile (working copy) > @@ -2,6 +2,6 @@ >=20 > PROG=3D fetch > CSTD?=3D c99 > -LIBADD=3D fetch > +LIBADD=3D ssl crypto fetch >=20 > .include without which I got: > --- all_subdir_usr.bin --- > /usr/local/bin/powerpc64-portbld-freebsd11.0-gcc -O2 -pipe -isystem = /usr/obj/usr/src/tmp/usr/include/. -L/usr/obj/usr/src/tmp/usr/lib/. = -L/usr/obj/usr/src/tmp/li > b/. -g -std=3Diso9899:1999 -fstack-protector-strong -Wsystem-headers = -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes = -Wmissing-prototypes -Wpoin > ter-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow = -Wunused-parameter -Wcast-align -Wchar-subscripts -Winline = -Wnested-externs -Wredundant-dec > ls -Wold-style-definition -Wno-pointer-sign = -L/usr/obj/usr/src/tmp/usr/lib/. -L/usr/obj/usr/src/tmp/lib/. = -L/usr/obj/usr/src/lib/libc++/. -L/usr/lib/. -o fetch. > full fetch.o -lfetch . . . > --- all_subdir_usr.bin --- > /usr/local/bin/powerpc64-freebsd-ld: warning: libssl.so.8, needed by = /usr/obj/usr/src/tmp/usr/lib/./libfetch.so, not found (try using -rpath = or -rpath-link) > /usr/local/bin/powerpc64-freebsd-ld: warning: libcrypto.so.8, needed = by /usr/obj/usr/src/tmp/usr/lib/./libfetch.so, not found (try using = -rpath or -rpath-link) > /usr/obj/usr/src/tmp/usr/lib/./libfetch.so: undefined reference to = `X509_LOOKUP_file' > /usr/obj/usr/src/tmp/usr/lib/./libfetch.so: undefined reference to = `ASN1_STRING_length' > /usr/obj/usr/src/tmp/usr/lib/./libfetch.so: undefined reference to = `SSL_get_error' > /usr/obj/usr/src/tmp/usr/lib/./libfetch.so: undefined reference to = `CRYPTO_free' > /usr/obj/usr/src/tmp/usr/lib/./libfetch.so: undefined reference to = `SSL_write' > /usr/obj/usr/src/tmp/usr/lib/./libfetch.so: undefined reference to = `SSLv23_client_method' > /usr/obj/usr/src/tmp/usr/lib/./libfetch.so: undefined reference to = `sk_value' > /usr/obj/usr/src/tmp/usr/lib/./libfetch.so: undefined reference to = `MD5_Final' > /usr/obj/usr/src/tmp/usr/lib/./libfetch.so: undefined reference to = `SSL_free' > /usr/obj/usr/src/tmp/usr/lib/./libfetch.so: undefined reference to = `X509_STORE_add_lookup' > /usr/obj/usr/src/tmp/usr/lib/./libfetch.so: undefined reference to = `SSL_CTX_use_certificate_chain_file' > /usr/obj/usr/src/tmp/usr/lib/./libfetch.so: undefined reference to = `SSL_set_fd' > /usr/obj/usr/src/tmp/usr/lib/./libfetch.so: undefined reference to = `X509_NAME_ENTRY_get_data' > /usr/obj/usr/src/tmp/usr/lib/./libfetch.so: undefined reference to = `SSL_CTX_set_verify' > /usr/obj/usr/src/tmp/usr/lib/./libfetch.so: undefined reference to = `X509_NAME_oneline' > /usr/obj/usr/src/tmp/usr/lib/./libfetch.so: undefined reference to = `ASN1_STRING_data' > /usr/obj/usr/src/tmp/usr/lib/./libfetch.so: undefined reference to = `X509_get_subject_name' > /usr/obj/usr/src/tmp/usr/lib/./libfetch.so: undefined reference to = `X509_get_issuer_name' > /usr/obj/usr/src/tmp/usr/lib/./libfetch.so: undefined reference to = `SSL_get_version' > /usr/obj/usr/src/tmp/usr/lib/./libfetch.so: undefined reference to = `SSL_library_init' > /usr/obj/usr/src/tmp/usr/lib/./libfetch.so: undefined reference to = `SSL_read' > /usr/obj/usr/src/tmp/usr/lib/./libfetch.so: undefined reference to = `X509_STORE_CTX_get_current_cert' > /usr/obj/usr/src/tmp/usr/lib/./libfetch.so: undefined reference to = `SSL_get_current_cipher' > /usr/obj/usr/src/tmp/usr/lib/./libfetch.so: undefined reference to = `SSL_CTX_ctrl' > /usr/obj/usr/src/tmp/usr/lib/./libfetch.so: undefined reference to = `SSL_new' > /usr/obj/usr/src/tmp/usr/lib/./libfetch.so: undefined reference to = `SSL_set_connect_state' > /usr/obj/usr/src/tmp/usr/lib/./libfetch.so: undefined reference to = `SSL_shutdown' > /usr/obj/usr/src/tmp/usr/lib/./libfetch.so: undefined reference to = `GENERAL_NAMES_free' > /usr/obj/usr/src/tmp/usr/lib/./libfetch.so: undefined reference to = `SSL_CTX_new' > /usr/obj/usr/src/tmp/usr/lib/./libfetch.so: undefined reference to = `SSL_get_peer_certificate' > /usr/obj/usr/src/tmp/usr/lib/./libfetch.so: undefined reference to = `X509_NAME_get_entry' > /usr/obj/usr/src/tmp/usr/lib/./libfetch.so: undefined reference to = `SSL_CTX_load_verify_locations' > /usr/obj/usr/src/tmp/usr/lib/./libfetch.so: undefined reference to = `X509_get_ext_d2i' > /usr/obj/usr/src/tmp/usr/lib/./libfetch.so: undefined reference to = `X509_load_crl_file' > /usr/obj/usr/src/tmp/usr/lib/./libfetch.so: undefined reference to = `SSL_ctrl' > /usr/obj/usr/src/tmp/usr/lib/./libfetch.so: undefined reference to = `X509_STORE_set_flags' > /usr/obj/usr/src/tmp/usr/lib/./libfetch.so: undefined reference to = `SSL_CTX_use_PrivateKey_file' > /usr/obj/usr/src/tmp/usr/lib/./libfetch.so: undefined reference to = `X509_free' > /usr/obj/usr/src/tmp/usr/lib/./libfetch.so: undefined reference to = `X509_NAME_get_index_by_NID' > /usr/obj/usr/src/tmp/usr/lib/./libfetch.so: undefined reference to = `sk_num' > /usr/obj/usr/src/tmp/usr/lib/./libfetch.so: undefined reference to = `SSL_connect' > /usr/obj/usr/src/tmp/usr/lib/./libfetch.so: undefined reference to = `SSL_CTX_free' > /usr/obj/usr/src/tmp/usr/lib/./libfetch.so: undefined reference to = `SSL_load_error_strings' > /usr/obj/usr/src/tmp/usr/lib/./libfetch.so: undefined reference to = `SSL_CTX_get_cert_store' > /usr/obj/usr/src/tmp/usr/lib/./libfetch.so: undefined reference to = `MD5_Init' > /usr/obj/usr/src/tmp/usr/lib/./libfetch.so: undefined reference to = `SSL_CIPHER_get_name' > /usr/obj/usr/src/tmp/usr/lib/./libfetch.so: undefined reference to = `ERR_print_errors_fp' > /usr/obj/usr/src/tmp/usr/lib/./libfetch.so: undefined reference to = `MD5_Update' > /usr/obj/usr/src/tmp/usr/lib/./libfetch.so: undefined reference to = `ASN1_STRING_to_UTF8' > collect2: error: ld returned 1 exit status The make commands were: > make -j 6 -DNO_CLEAN WITH_FAST_DEPEND=3D CROSS_TOOLCHAIN=3Dpowerpc64-gcc= WITH_LIBCPLUSPLUS=3D WITHOUT_CLANG_BOOTSTRAP=3D WITH_CLANG=3D = WITH_CLANG_IS_CC=3D WITH_LLDB=3D WITHOUT_GCC_BOOTSTRAP=3D WITHOUT_GCC=3D = WITHOUT_GNUCXX=3D WITHOUT_BOOT=3D WITHOUT_LIB32=3D buildworld = buildkernel KERNCONF=3DGENERIC64vtsc-NODEBUG TARGET=3Dpowerpc = TARGET_ARCH=3Dpowerpc64 (The NO_CLEAN is from after the first build problem and is to avoid long = rebuild times to get back to the same point.) Context details if you care: > # freebsd-version -ku; uname -aKU > 11.0-CURRENT > 11.0-CURRENT > FreeBSD FBSDG5C0 11.0-CURRENT FreeBSD 11.0-CURRENT #12 r281630M: Sat = Apr 18 01:15:13 PDT 2015 = root@FBSDG5C0:/usr/obj/usr/src/sys/GENERIC64vtsc-NODEBUG powerpc = 1100070 1100070 I am attempting an update after having been away from the PowerMacs for = months. > # svnlite info /usr/src > Path: /usr/src > Working Copy Root Path: /usr/src > URL: https://svn0.us-west.freebsd.org/base/head > Relative URL: ^/head > Repository Root: https://svn0.us-west.freebsd.org/base > Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f > Revision: 291443 > Node Kind: directory > Schedule: normal > Last Changed Author: nwhitehorn > Last Changed Rev: 291442 > Last Changed Date: 2015-11-28 23:16:08 -0800 (Sat, 28 Nov 2015) > # more /etc/src.conf > NO_WERROR=3D > WITH_DEBUG=3D > WITH_DEBUG_FILES=3D > MALLOC_PRODUCTION=3D > CC=3D/usr/local/bin/powerpc64-portbld-freebsd11.0-gcc > CXX=3D/usr/local/bin/powerpc64-portbld-freebsd11.0-g++ > CPP=3D/usr/local/bin/powerpc64-portbld-freebsd11.0-cpp > CROSS_BINUTILS_PREFIX=3D/usr/local/powerpc64-freebsd/bin/ > X_COMPILER_TYPE=3Dgcc > DEPFLAGS+=3D-isystem /usr/obj/usr/src/tmp/usr/include/. = -I/usr/obj/usr/src/tmp/usr/include/c++/v1/. -I/usr/include/c++/v1/. > L/usr/obj/usr/src/tmp/usr/lib/lib32/. > CFLAGS+=3D-isystem /usr/obj/usr/src/tmp/usr/include/. = -L/usr/obj/usr/src/tmp/usr/lib/. -L/usr/obj/usr/src/tmp/lib/. > LDFLAGS+=3D-L/usr/obj/usr/src/tmp/usr/lib/. = -L/usr/obj/usr/src/tmp/lib/. > CXXFLAGS+=3D-isystem /usr/obj/usr/src/tmp/usr/include/. = -I/usr/obj/usr/src/tmp/usr/include/c++/v1/. -std=3Dgnu++11 = -L/usr/obj/usr/src/lib/libc++/. > LDFLAGS+=3D-L/usr/obj/usr/src/lib/libc++/. > CXXFLAGS+=3D-I/usr/include/c++/v1/. -std=3Dgnu++11 -L/usr/lib/. > LDFLAGS+=3D-L/usr/lib/. > # svnlite info /usr/ports/ > Path: /usr/ports > Working Copy Root Path: /usr/ports > URL: https://svn0.us-west.freebsd.org/ports/head > Relative URL: ^/head > Repository Root: https://svn0.us-west.freebsd.org/ports > Repository UUID: 35697150-7ecd-e111-bb59-0022644237b5 > Revision: 402562 > Node Kind: directory > Schedule: normal > Last Changed Author: rene > Last Changed Rev: 402562 > Last Changed Date: 2015-11-28 15:08:03 -0800 (Sat, 28 Nov 2015) =3D=3D=3D Mark Millard markmi at dsl-only.net From owner-freebsd-ppc@freebsd.org Mon Nov 30 18:26:45 2015 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 C4F44A3DADC for ; Mon, 30 Nov 2015 18:26:45 +0000 (UTC) (envelope-from superbisquit@gmail.com) Received: from mail-vk0-x22d.google.com (mail-vk0-x22d.google.com [IPv6:2607:f8b0:400c:c05::22d]) (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 7E38A1A18 for ; Mon, 30 Nov 2015 18:26:45 +0000 (UTC) (envelope-from superbisquit@gmail.com) Received: by vkay187 with SMTP id y187so107587186vka.3 for ; Mon, 30 Nov 2015 10:26:44 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=a2kt0XT5SK39DxwrOYiL9PDLe36L6DTSFFqX7ONcyWE=; b=yhJzWNFRn4exxiFQGWNgZE3hUL3s7fSHewT0dxyXoH7Jlb2cnY88D7fbWHU8pFFKZZ PizbgsX2s8je4gNdolQryCITohHnRTzMwSsYNzmlsXLg5px+3LbKYY203braEDb5aUwZ 1wHP6zbGxgBk4/I+hVeDek0caEFQFUWK1p4Dbhq3W0kpWvblyrV3agMxY12Ix3w6GloL kySQ4CodFH9bCJTeIEvhxteJ93K3pTsdcVLKI/irb+fWdu5Id6TVcXp+f8/gudzXdjsz Vt+NxedY2IE6jkuuu1GJb/v8kPrvUeTjeXnU1M9+cevFkQv2fbBRnKs35byTl59FuQWq pCNg== MIME-Version: 1.0 X-Received: by 10.31.141.65 with SMTP id p62mr9054232vkd.93.1448908004427; Mon, 30 Nov 2015 10:26:44 -0800 (PST) Received: by 10.103.9.195 with HTTP; Mon, 30 Nov 2015 10:26:44 -0800 (PST) In-Reply-To: <20151128134041.07d5a85bdaecefb92f740114@getmail.no> References: <20151128134041.07d5a85bdaecefb92f740114@getmail.no> Date: Mon, 30 Nov 2015 13:26:44 -0500 Message-ID: Subject: Re: About the Linux PowerPC Laptop Project From: Joe Nosay To: Torfinn Ingolfsen Cc: FreeBSD PowerPC ML Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Nov 2015 18:26:46 -0000 Looks like we have a challenge. On Sat, Nov 28, 2015 at 7:40 AM, Torfinn Ingolfsen < torfinn.ingolfsen@getmail.no> wrote: > On Fri, 27 Nov 2015 15:26:54 -0500 > Joe Nosay wrote: > > > What is the current state? Motherboard testing? Needing a physical shell? > > Or what? > > AFAICT from their website and forum, they don't have any hardware yet, and > are looking into starting a crowdfunding campaign to produce a notebook by > the end of 2016. > > References: > http://www.powerpc-notebook.org/ > -- > Torfinn Ingolfsen > _______________________________________________ > freebsd-ppc@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-ppc > To unsubscribe, send any mail to "freebsd-ppc-unsubscribe@freebsd.org" > From owner-freebsd-ppc@freebsd.org Wed Dec 2 17:39:02 2015 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 45171A3F0D7; Wed, 2 Dec 2015 17:39:02 +0000 (UTC) (envelope-from superbisquit@gmail.com) Received: from mail-vk0-x243.google.com (mail-vk0-x243.google.com [IPv6:2607:f8b0:400c:c05::243]) (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 F095B1243; Wed, 2 Dec 2015 17:39:01 +0000 (UTC) (envelope-from superbisquit@gmail.com) Received: by vkca188 with SMTP id a188so2546650vkc.1; Wed, 02 Dec 2015 09:39:00 -0800 (PST) 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=fz5J5j39PUi8np3IesmrtrsjRftFSWBXtdLgUVzOpwk=; b=0pyet/eBN5NA6BxGik1nV2Ual8jWdilbylNG85IMw760MVrdvxhssqxvJtf1DdeP46 SzLte8bQhY+efJsTNZgFCON7kLPwfH90YqgBwEW88yM0RmmCbWJ7x90i7AT9a2fC3VUb 8RfvSlI43rxomZ7trLytYMGjR4nTQhPoDkj37361DWrmUp0LmF4if23DKAQlpUpTWffS h8MIi7ap8PsVQUg5BSv2sZ8hbVLP8k0oOPkKvMB76nZ4P5C5kK799+5thQaqfkHKxbG4 haY/Br2HBdM8/Kbr0CUv0TSUtMVl0iHvah3Sbjc1KldAEO1y3GXinMUCEfNz1mOSpNV2 QoPQ== MIME-Version: 1.0 X-Received: by 10.31.49.147 with SMTP id x141mr3014324vkx.1.1449077940848; Wed, 02 Dec 2015 09:39:00 -0800 (PST) Received: by 10.103.9.195 with HTTP; Wed, 2 Dec 2015 09:39:00 -0800 (PST) Date: Wed, 2 Dec 2015 12:39:00 -0500 Message-ID: Subject: A proposal and a challenge From: Joe Nosay To: FreeBSD PowerPC ML , Eric Oyen , FreeBSD Hackers , freebsd-advocacy@freebsd.org, "www@openbsd.org" , Bill Buros , vinux-support@googlegroups.com, "SELCommunityAffairs@am.sony.com" , SCA_CSR@sonyusa.com, "qemu-ppc@nongnu.org" , Torfinn Ingolfsen , Debian powerpc Mailinglist , Juergen Lock , outro.pessoa@gmail.com, Paul Davis , team@powerpc-notebook.org X-Mailman-Approved-At: Wed, 02 Dec 2015 18:26:36 +0000 Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Dec 2015 17:39:02 -0000 I know that everyone is familiar with the one laptop per child program; and, that is good. Let's take it one step further. The debian team wants to build a powerpc laptop. FreeBSD is working on the POWER8 with the PPC team. The problem is convincing IBM to publicly open the CPU for a good purpose. What's the sale's pitch? Let it be for education. Four operating systems on a single machine - the apm layout is capable of doing it with a boot, main, and swap. That's only twelve spaces used. Yes, it can be concentrated down to 64 GB. What can be done with it? It's a POWER machine, load-store, learn. 64 bit. How many free registers usually? About five? Yes? Enough for one application. Two would do for the application and system. Let's make it real. Two chips. Four processors each. Running about 2.0 to 2.25 GHz. Let the kernel match that. Debian at 1Khz - unless someone can do a patch to make the kernel go the necessary mile. Open and Net BSD have their own thing; so, this is for FreeBSD for the kernel rate. Latency should match frequency. GRUB should be able to handle four options on a screen. Oh, Open graphics and sound. Accessibility. Development. Creativity. Show it. Let them know what it can do. Sound. Music. Art. Design. Programming. Let them see it from the start to finish. Make it affordable. For students, children, people to learn. All of you can do this. Why not me? I am not able to afford it. Yet, the rest of you are able to do such. It will pay for itself and you know it. Don't reply, just think on it. You know my requirements: Don't pay me, just do it. And respect. Ladies and gentlemen, thank you for taking the time to read this. Enjoy life. From owner-freebsd-ppc@freebsd.org Wed Dec 2 19:13:10 2015 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 7DC23A3E414; Wed, 2 Dec 2015 19:13:10 +0000 (UTC) (envelope-from lsorense@csclub.uwaterloo.ca) Received: from mail.csclub.uwaterloo.ca (mail.csclub.uwaterloo.ca [129.97.134.52]) by mx1.freebsd.org (Postfix) with ESMTP id 559921B4A; Wed, 2 Dec 2015 19:13:10 +0000 (UTC) (envelope-from lsorense@csclub.uwaterloo.ca) Received: from caffeine.csclub.uwaterloo.ca (caffeine.csclub.uwaterloo.ca [129.97.134.17]) by mail.csclub.uwaterloo.ca (Postfix) with SMTP id 8DCC22DD20; Wed, 2 Dec 2015 14:05:53 -0500 (EST) Received: by caffeine.csclub.uwaterloo.ca (sSMTP sendmail emulation); Wed, 02 Dec 2015 14:05:53 -0500 From: "Lennart Sorensen" Date: Wed, 2 Dec 2015 14:05:53 -0500 To: Joe Nosay Cc: FreeBSD PowerPC ML , Eric Oyen , FreeBSD Hackers , freebsd-advocacy@freebsd.org, "www@openbsd.org" , Bill Buros , vinux-support@googlegroups.com, "SELCommunityAffairs@am.sony.com" , SCA_CSR@sonyusa.com, "qemu-ppc@nongnu.org" , Torfinn Ingolfsen , Debian powerpc Mailinglist , Juergen Lock , outro.pessoa@gmail.com, Paul Davis , team@powerpc-notebook.org Subject: Re: A proposal and a challenge Message-ID: <20151202190553.GC25177@csclub.uwaterloo.ca> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) X-Mailman-Approved-At: Wed, 02 Dec 2015 19:57:55 +0000 X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Dec 2015 19:13:10 -0000 On Wed, Dec 02, 2015 at 12:39:00PM -0500, Joe Nosay wrote: > I know that everyone is familiar with the one laptop per child program; > and, that is good. Let's take it one step further. The debian team wants to > build a powerpc laptop. FreeBSD is working on the POWER8 with the PPC team. > The problem is convincing IBM to publicly open the CPU for a good purpose. > What's the sale's pitch? Let it be for education. Do you know what the power consumption of a POWER8 chip is? > Four operating systems on a single machine - the apm layout is capable of > doing it with a boot, main, and swap. That's only twelve spaces used. > Yes, it can be concentrated down to 64 GB. > What can be done with it? > It's a POWER machine, load-store, learn. ARM and MIPS are load-store machines too, and usually much cheaper and more power friendly. Sure powerpc has 32 registers and arm only has 16, but so what? That's what each core has and many things have multiple cores these days. Mips has 32 as well. > 64 bit. How many free registers usually? About five? Yes? > Enough for one application. Two would do for the application and system. > Let's make it real. Two chips. Four processors each. > Running about 2.0 to 2.25 GHz. ARM chips certainly exist that are 64bit and run that kind of speeds. Not sure what speeds mips are at these days but it has had 64bit versions for a long time. > Let the kernel match that. Debian at 1Khz - unless someone can do a patch > to make the kernel go the necessary mile. > Open and Net BSD have their own thing; so, this is for FreeBSD for the > kernel rate. Latency should match frequency. I have no idea what BSD has to do with this, but then again I am not sure what you are even trying to describe. Besides have you heard of kvm? Virtual machines are a commodity these days and simple to do. > GRUB should be able to handle four options on a screen. > > Oh, Open graphics and sound. > Accessibility. Development. Creativity. > Show it. > > Let them know what it can do. > > Sound. Music. > > Art. Design. > > Programming. > > Let them see it from the start to finish. > > > Make it affordable. > > For students, children, people to learn. > > All of you can do this. > > Why not me? > > I am not able to afford it. > > Yet, the rest of you are able to do such. > > It will pay for itself and you know it. Well OLPC certainly seems to have been a flop done by someone without a clue what actual problems needed to be solved. > Don't reply, just think on it. > > You know my requirements: Don't pay me, just do it. > > > And respect. > > > > Ladies and gentlemen, thank you for taking the time to read this. > Enjoy life. I wish it had made sense what I read, but it did not. -- Len Sorensen From owner-freebsd-ppc@freebsd.org Thu Dec 3 11:57:34 2015 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 45FF6A403ED for ; Thu, 3 Dec 2015 11:57:34 +0000 (UTC) (envelope-from wojtek@puchar.net) Received: from puchar.net (puchar.net [188.252.31.250]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "puchar.net", Issuer "puchar.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 30BA81D74 for ; Thu, 3 Dec 2015 11:57:32 +0000 (UTC) (envelope-from wojtek@puchar.net) Received: Received: from 127.0.0.1 (localhost [127.0.0.1]) by puchar.net (8.15.2/8.14.9) with ESMTPS id tB3BPLiB079798 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 3 Dec 2015 12:25:22 +0100 (CET) (envelope-from wojtek@puchar.net) Received: from laptop.wojtek.intra (localhost [127.0.0.1]) by laptop.wojtek.intra (8.14.9/8.14.9) with ESMTP id tB3BPP3H005262; Thu, 3 Dec 2015 12:25:25 +0100 (CET) (envelope-from wojtek@puchar.net) Received: from localhost (wojtek@localhost) by laptop.wojtek.intra (8.14.9/8.14.9/Submit) with ESMTP id tB3BPFLF005259; Thu, 3 Dec 2015 12:25:15 +0100 (CET) (envelope-from wojtek@puchar.net) X-Authentication-Warning: laptop.wojtek.intra: wojtek owned process doing -bs Date: Thu, 3 Dec 2015 12:25:15 +0100 (CET) From: Wojciech Puchar X-X-Sender: wojtek@laptop.wojtek.intra To: Joe Nosay cc: FreeBSD PowerPC ML , Eric Oyen , FreeBSD Hackers , freebsd-advocacy@freebsd.org, "www@openbsd.org" , Bill Buros , vinux-support@googlegroups.com, "SELCommunityAffairs@am.sony.com" , SCA_CSR@sonyusa.com, "qemu-ppc@nongnu.org" , Torfinn Ingolfsen , Debian powerpc Mailinglist , Juergen Lock , outro.pessoa@gmail.com, Paul Davis , team@powerpc-notebook.org Subject: Re: A proposal and a challenge In-Reply-To: Message-ID: References: User-Agent: Alpine 2.20 (BSF 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (puchar.net [10.0.1.1]); Thu, 03 Dec 2015 12:25:22 +0100 (CET) X-Mailman-Approved-At: Thu, 03 Dec 2015 12:21:04 +0000 X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Dec 2015 11:57:34 -0000 > I know that everyone is familiar with the one laptop per child program; > and, that is good. Really? Poor children, make them poorer. From owner-freebsd-ppc@freebsd.org Thu Dec 3 12:36:26 2015 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 DC044A3E50B for ; Thu, 3 Dec 2015 12:36:26 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-211-152.reflexion.net [208.70.211.152]) (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 9AE9119EC for ; Thu, 3 Dec 2015 12:36:26 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 29743 invoked from network); 3 Dec 2015 12:36:19 -0000 Received: from unknown (HELO rtc-sm-01.app.dca.reflexion.local) (10.81.150.1) by 0 (rfx-qmail) with SMTP; 3 Dec 2015 12:36:19 -0000 Received: by rtc-sm-01.app.dca.reflexion.local (Reflexion email security v7.80.0) with SMTP; Thu, 03 Dec 2015 07:36:19 -0500 (EST) Received: (qmail 11908 invoked from network); 3 Dec 2015 12:36:19 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with SMTP; 3 Dec 2015 12:36:19 -0000 X-No-Relay: not in my network X-No-Relay: not in my network Received: from [192.168.1.8] (c-76-115-7-162.hsd1.or.comcast.net [76.115.7.162]) by iron2.pdx.net (Postfix) with ESMTPSA id 886C71C43D2; Thu, 3 Dec 2015 04:36:10 -0800 (PST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\)) Subject: 11.0-CURRENT -r291685 installworld: ld-elf.so.1 update leads to Signal 11's on Quad core G5 PowerMac From: Mark Millard In-Reply-To: Date: Thu, 3 Dec 2015 04:36:17 -0800 Content-Transfer-Encoding: quoted-printable Message-Id: <0DFE7349-6954-4E9C-8FD3-52EFCF40DFD9@dsl-only.net> References: <01BA3FF2-F362-48FA-B9E2-112E05CC00ED@dsl-only.net> <6AA244B9-DE60-4D8B-A08E-AADD73F9D856@dsl-only.net> <106D9CB0-D9AE-4463-A03E-3AB16583CDA7@dsl-only.net> To: Nathan Whitehorn , FreeBSD PowerPC ML X-Mailer: Apple Mail (2.2104) X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Dec 2015 12:36:27 -0000 Just FYI: My attempt to update from 11.0 -r281630 via buildworld and = installworld to -r291685 based on powerpc64-gcc as the system and = (self-hosted) cross-compiler on a G5 PowerMac got: > =3D=3D=3D> libexec/rtld-elf (install) > chflags -h noschg /usr/libexec/ld-elf.so.1 > install -s -o root -g wheel -m 555 -C -b -fschg -S ld-elf.so.1 = /libexec/ld-elf.so.1 > install -T debug -o root -g wheel -m 444 ld-elf.so.1.debug = /usr/lib/debug/libexec/ld-elf.so.1.debug > install -o root -g wheel -m 444 rtld.1.gz /usr/share/man/man1/ > *** Signal 11 >=20 > Stop. > make[5]: stopped in /usr/src/libexec/rtld-elf > *** Error code 1 This looks the same as I got earlier for -r291637: loading non-static = programs fails when the new ld-elf.so.1 is in use. But if I'm the only one getting such results after the adjustments that = you made then something else about my attempt is likely involved. It has = taken some odd activity to even compile/link for my jump from a = 2015-Apr-18 11.0-CURRENT context to modern via (the updated) = powerpc64-gcc. So my context might not be the best evidence. Using /rescue/* programs to put back the ld-elf.so.1.old gets things = going again. So now I have a partially updated world. (The kernel built = and installed fine earlier, my various update problems have been with = world.) Context details if you care: Via /etc/src.conf powerpc64-gcc is also in use as the host compiler: no = gcc 4.2.1 present and clang not used. Before I'd done buildkernel and installkernel things were back at: > # freebsd-version -ku; uname -aKU > 11.0-CURRENT > 11.0-CURRENT > FreeBSD FBSDG5C0 11.0-CURRENT FreeBSD 11.0-CURRENT #12 r281630M: Sat = Apr 18 01:15:13 PDT 2015 = root@FBSDG5C0:/usr/obj/usr/src/sys/GENERIC64vtsc-NODEBUG powerpc = 1100070 1100070 After updating the kernel (the first time) when I'd still not been able = to complete a buildworld: > # freebsd-version -ku; uname -aKU > 11.0-CURRENT > 11.0-CURRENT > FreeBSD FBSDG5C0 11.0-CURRENT FreeBSD 11.0-CURRENT #13 r291624M: Tue = Dec 1 17:19:04 PST 2015 = root@FBSDG5C0:/usr/obj/usr/src/sys/GENERIC64vtsc-NODEBUG powerpc = 1100091 1100070 Now (build world completed but installworld did not; more recent kernel = build): > $ freebsd-version -ku; uname -aKU > 11.0-CURRENT > 11.0-CURRENT > FreeBSD FBSDG5C0 11.0-CURRENT FreeBSD 11.0-CURRENT #15 r291685M: Thu = Dec 3 03:06:52 PST 2015 = root@FBSDG5C0:/usr/obj/usr/src/sys/GENERIC64vtsc-NODEBUG powerpc = 1100091 1100070 > # svnlite info /usr/src > Path: /usr/src > Working Copy Root Path: /usr/src > URL: https://svn0.us-west.freebsd.org/base/head > Relative URL: ^/head > Repository Root: https://svn0.us-west.freebsd.org/base > Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f > Revision: 291685 > Node Kind: directory > Schedule: normal > Last Changed Author: kib > Last Changed Rev: 291685 > Last Changed Date: 2015-12-03 02:33:57 -0800 (Thu, 03 Dec 2015) > # more /etc/src.conf > NO_WERROR=3D > WITH_DEBUG=3D > WITH_DEBUG_FILES=3D > MALLOC_PRODUCTION=3D > CC=3D/usr/local/bin/powerpc64-portbld-freebsd11.0-gcc > CXX=3D/usr/local/bin/powerpc64-portbld-freebsd11.0-g++ > CPP=3D/usr/local/bin/powerpc64-portbld-freebsd11.0-cpp > CROSS_BINUTILS_PREFIX=3D/usr/local/powerpc64-freebsd/bin/ > X_COMPILER_TYPE=3Dgcc > DEPFLAGS+=3D -isystem /usr/obj/usr/src/tmp/usr/include/. = -I/usr/obj/usr/src/tmp/usr/include/c++/v1/. -I/usr/include/c++/v1/. > CFLAGS+=3D -isystem /usr/obj/usr/src/tmp/usr/include/. -Wl,-rpath-link = -Wl,/usr/obj/usr/src/tmp/usr/lib/. -Wl,-rpath-link = -Wl,/usr/obj/usr/src/tmp/lib/. -L/usr/obj/usr/src/tmp/usr/lib/. = -L/usr/obj/usr/src/tmp/lib/. > LDFLAGS+=3D -Wl,-rpath-link -Wl,/usr/obj/usr/src/tmp/usr/lib/. = -Wl,-rpath-link -Wl,/usr/obj/usr/src/tmp/lib/. = -L/usr/obj/usr/src/tmp/usr/lib/. -L/usr/obj/usr/src/tmp/lib/. > CXXFLAGS+=3D -isystem /usr/obj/usr/src/tmp/usr/include/. = -I/usr/obj/usr/src/tmp/usr/include/c++/v1/. -std=3Dgnu++11 = -L/usr/obj/usr/src/lib/libc++/. > # svnlite info /usr/ports > Path: /usr/ports > Working Copy Root Path: /usr/ports > URL: https://svn0.us-west.freebsd.org/ports/head > Relative URL: ^/head > Repository Root: https://svn0.us-west.freebsd.org/ports > Repository UUID: 35697150-7ecd-e111-bb59-0022644237b5 > Revision: 402806 > Node Kind: directory > Schedule: normal > Last Changed Author: miwi > Last Changed Rev: 402806 > Last Changed Date: 2015-12-01 17:26:49 -0800 (Tue, 01 Dec 2015) =3D=3D=3D Mark Millard markmi at dsl-only.net From owner-freebsd-ppc@freebsd.org Thu Dec 3 14:44:19 2015 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 82A74A3F3AB; Thu, 3 Dec 2015 14:44:19 +0000 (UTC) (envelope-from cym224@gmail.com) Received: from mail-wm0-x244.google.com (mail-wm0-x244.google.com [IPv6:2a00:1450:400c:c09::244]) (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 1818A1039; Thu, 3 Dec 2015 14:44:19 +0000 (UTC) (envelope-from cym224@gmail.com) Received: by wmeo63 with SMTP id o63so4283738wme.2; Thu, 03 Dec 2015 06:44:17 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=ZTObLQ4CZ/mbui/SThlmqkW+ypI2kSwlhsbFcvGeiag=; b=tka5ZMu0IzeLxCXMvso8RDRMZBPRBkcmQGUCEsxt1Gp/bSoggY2wLo2IKD8v0C65DT 687kZ0srUYMgh5YDUT64vjOLqCmaS0JrhGJJUtckOaxKYS3PtOjXrDydPUMZYH4DNc6R 5o6tzTBP6qWttW5qQ+gdrENVuVKp+Oc99+m74Sg7zxcTp2KozWcdwztWPZuzp2pvQZNK mngj5A0kNTirkNl/o3p66NMQXpypwuyuZfWrDGmd/lBRYMDVO2mUEKY3lfsi2Vk2Mpqi KaqIJzDqGoG8ViTxqIQrxoUEwDCk8BtY+QTs5gxXIce/6BOnbLjS/DQqdIlR/jFMAFMP OpRw== MIME-Version: 1.0 X-Received: by 10.28.210.74 with SMTP id j71mr12408058wmg.96.1449153857477; Thu, 03 Dec 2015 06:44:17 -0800 (PST) Received: by 10.28.107.13 with HTTP; Thu, 3 Dec 2015 06:44:17 -0800 (PST) In-Reply-To: References: Date: Thu, 3 Dec 2015 09:44:17 -0500 Message-ID: Subject: Re: A proposal and a challenge From: Nemo To: Joe Nosay Cc: FreeBSD PowerPC ML , Eric Oyen , FreeBSD Hackers , freebsd-advocacy@freebsd.org, "www@openbsd.org" , Bill Buros , vinux-support@googlegroups.com, "SELCommunityAffairs@am.sony.com" , SCA_CSR@sonyusa.com, "qemu-ppc@nongnu.org" , Torfinn Ingolfsen , Debian powerpc Mailinglist , Juergen Lock , outro.pessoa@gmail.com, Paul Davis , team@powerpc-notebook.org Content-Type: text/plain; charset=UTF-8 X-Mailman-Approved-At: Thu, 03 Dec 2015 15:18:43 +0000 X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Dec 2015 14:44:19 -0000 On 2 December 2015 at 12:39, Joe Nosay wrote (in part): > The problem is convincing IBM to publicly open the CPU for a good purpose. OpenPower, perhaps? N. From owner-freebsd-ppc@freebsd.org Fri Dec 4 07:10:56 2015 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 22CF2A407A5 for ; Fri, 4 Dec 2015 07:10:56 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-211-152.reflexion.net [208.70.211.152]) (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 AD3E3118E for ; Fri, 4 Dec 2015 07:10:55 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 19596 invoked from network); 4 Dec 2015 07:10:53 -0000 Received: from unknown (HELO mail-cs-02.app.dca.reflexion.local) (10.81.19.2) by 0 (rfx-qmail) with SMTP; 4 Dec 2015 07:10:53 -0000 Received: by mail-cs-02.app.dca.reflexion.local (Reflexion email security v7.80.0) with SMTP; Fri, 04 Dec 2015 02:10:55 -0500 (EST) Received: (qmail 27575 invoked from network); 4 Dec 2015 07:10:55 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with SMTP; 4 Dec 2015 07:10:55 -0000 X-No-Relay: not in my network X-No-Relay: not in my network X-No-Relay: not in my network Received: from [192.168.1.8] (c-76-115-7-162.hsd1.or.comcast.net [76.115.7.162]) by iron2.pdx.net (Postfix) with ESMTPSA id 126801C43BC; Thu, 3 Dec 2015 23:10:40 -0800 (PST) From: Mark Millard Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Subject: svn commit: r291739 - head/share/mk vs. /usr/src/lib/libc/tests/ssp for powerpc64/gcc builds Message-Id: <2361A90E-50F3-4411-88FE-DF15FA94B42D@dsl-only.net> Date: Thu, 3 Dec 2015 23:10:52 -0800 To: FreeBSD PowerPC ML , FreeBSD Toolchain , svn-src-head@freebsd.org Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\)) X-Mailer: Apple Mail (2.2104) X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Dec 2015 07:10:56 -0000 The change to > Log: > Add assertion for when LIBADD should be used rather than = LDADD/DPADD. resulted in my self-hosted powerpc64 buildworld attempt getting: > --- cleandir_subdir_ssp --- > make[6]: "/usr/src/share/mk/src.libnames.mk" line 479: = /usr/src/lib/libc/tests/ssp: Invalid LIBADD used which may need to be = added to src.libnames.mk: > ssp via head/lib/libc/tests/ssp/Makefile having: > .elif ${COMPILER_TYPE} =3D=3D "gcc" > CFLAGS.h_raw+=3D --param ssp-buffer-size=3D1 > LIBADD+=3D ssp > .endif =3D=3D=3D Mark Millard markmi at dsl-only.net From owner-freebsd-ppc@freebsd.org Sat Dec 5 10:24:53 2015 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 CA2D2A412CB for ; Sat, 5 Dec 2015 10:24:53 +0000 (UTC) (envelope-from andy.silva@snscommunication.com) Received: from mailer238.gate85.rs.smtp.com (mailer238.gate85.rs.smtp.com [74.91.85.238]) by mx1.freebsd.org (Postfix) with ESMTP id 655AA164F for ; Sat, 5 Dec 2015 10:24:53 +0000 (UTC) (envelope-from andy.silva@snscommunication.com) X-MSFBL: ZnJlZWJzZC1wcGNAZnJlZWJzZC5vcmdANzRfOTFfODVfMjM4QFNuc3RlbGVjb21f ZGVkaWNhdGVkX3Bvb2xA DKIM-Signature: v=1; a=rsa-sha256; d=smtp.com; s=smtpcomcustomers; c=relaxed/simple; q=dns/txt; i=@smtp.com; t=1449311092; h=From:Subject:To:Date:MIME-Version:Content-Type; bh=hSkgOsTr9y9ms/7nL6zDqVVTYAcF0EdIa80eXghxTDg=; b=ifzPt21TCPQCUp+lZrS74ihttEKCLrsvTjRTKE07uzcWFMbQXdalSihQzkbqoR/z 05yFVGVfDX7q2LiXDijHzD6Jn2mEQcGgkVY4gCoQFioAigvs4vUwDxUEhLUidkkI i/h4yZW9Cs8zWJEN3x+b+1jEo/bdI6hE3o58xloZM2E=; Received: from [154.20.125.37] ([154.20.125.37:61479] helo=d154-20-125-37.bchsia.telus.net) by rs-ord-mta03-1.smtp.com (envelope-from ) (ecelerity 3.3.2.44647 r(44647)) with ESMTPA id 0B/D8-32479-47BB2665; Sat, 05 Dec 2015 10:24:52 +0000 MIME-Version: 1.0 From: "Andy Silva" Reply-To: andy.silva@snscommunication.com To: freebsd-ppc@freebsd.org Subject: The LPWA (Low Power Wide Area) Networks Ecosystem: 2015 - 2030 - Opportunities, Challenges, Strategies, Industry Verticals & Forecasts (Report) X-Mailer: Smart_Send_2_0_138 Date: Sat, 5 Dec 2015 02:24:50 -0800 Message-ID: <2720508118680290295899@Ankur> X-SMTPCOM-Tracking-Number: cb02ea8f-8ff7-484d-a1de-1d0c3af7156c Feedback-ID: 6008902:SMTPCOM X-SMTPCOM-Sender-ID: 6008902 X-SMTPCOM-Spam-Policy: SMTP.com is a paid relay service. We do not tolerate UCE of any kind. Please report it ASAP to abuse@smtp.com Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Dec 2015 10:24:53 -0000 The LPWA (Low Power Wide Area) Networks Ecosystem: 2015 =96 2030 =96 Opport= unities, Challenges, Strategies, Industry Verticals & Forecasts Hello=20 Hope you are doing well.=20 I wanted to bring to your attention the latest SNS Research report in which= you might be interested, " The LPWA (Low Power Wide Area) Networks Ecosyst= em: 2015 =96 2030 =96 Opportunities, Challenges, Strategies, Industry Verti= cals & Forecasts."=20 I believe this report will be highly applicable for you. If you would like = to see the report sample or have any questions, please let me know. =20 Report Information: Release Date: November 2015 Number of Pages: 192 Number of Tables and Figures: 51 Report Overview: Until recently, most M2M and IoT services have largely relied on licensed c= ellular, wireline and satellite networks for their wide area connectivity r= equirements. Cellular networks, in particular, have enjoyed significant suc= cess in the arena. However, for many low bandwidth IoT applications, tradit= ional cellular networks are deemed too expensive due excessive power consum= ption and complex protocols that lower battery life. As a result, a number = of LPWA (Low Power Wide Area) alternatives have emerged that specifically s= eek to address these concerns. LPWA networks are optimized to provide wide area coverage with minimal powe= r consumption. Typically reliant on unlicensed frequencies, LPWA devices ha= ve low data rates, long battery lives and can operate unattended for long p= eriods of time. Already prevalent in IoT applications such as smart metering, lighting cont= rol and parking management, LPWA networks are expected to make a significan= t contribution to the M2M and IoT ecosystem, with an estimated $27 Billion = in service revenue by 2020. The =93LPWA (Low Power Wide Area) Networks Ecosystem: 2015 =96 2030 =96 Opp= ortunities, Challenges, Strategies, Industry Verticals & Forecasts=94 repor= t presents an in-depth assessment of the LPWA networks ecosystem including = LPWA technologies, key trends, market drivers, challenges, vertical market = applications, deployment case studies, regulatory landscape, standardizatio= n, opportunities, future roadmap, value chain, ecosystem player profiles an= d strategies. The report also presents market size forecasts from 2015 till= 2030. The forecasts are segmented for 9 vertical markets and 6 regions. The report comes with an associated Excel datasheet suite covering quantita= tive data from all numeric forecasts presented in the report. =20 Key Findings: The report has the following key findings: Already prevalent in IoT applications such as smart metering, lighting cont= rol and parking management, LPWA networks are expected to make a significan= t contribution to the M2M and IoT ecosystem, with an estimated $27 Billion = in service revenue by 2020. As of Q4=922015, SNS Research estimates the cost of a typical LPWA module t= o be $5-20, depending on the specific technology. As LPWA network deploymen= ts mature, we expect that the cost per module can drop down to as low as $1= -2 in volume quantities. At present, a majority of LPWA networks operate in license-exempt spectrum = primarily in sub-GHz bands. There are a number of ongoing initiatives that = call for regulators to dedicate spectrum bands exclusively for LPWA network= s as mass market adoption of unlicensed LPWA networks can result in signifi= cant interference. Besides optimizing their cellular networks for M2M services, mobile operato= rs are increasingly investing in their own carrier-grade LPWA networks to s= upport low bandwidth IoT applications. Topics Covered: The report covers the following topics: LPWA networks ecosystem Market drivers and barriers LPWA technologies, spectrum bands and key trends Assessment of competing cellular, satellite, wireline and short range netwo= rking technologies Vertical market applications, opportunities and deployment case studies Regulatory landscape and standardization Industry roadmap and value chain Profiles and strategies of over 80 leading ecosystem players Strategic recommendations for ecosystem players Market analysis and forecasts from 2015 till 2030 Historical Revenue & Forecast Segmentation: Connection and service revenue forecasts are provided for the following sub= markets: Vertical Markets Agriculture Asset Management & Logistics Automotive & Transportation Consumer Applications & Home Automation Energy & Utilities Healthcare Intelligent Buildings & Infrastructure Public Safety, Security & Surveillance Retail & Vending Others Regional Markets Asia Pacific Eastern Europe Middle East & Africa Latin & Central America North America Western Europe Key Questions Answered: The report provides answers to the following key questions: How big is the LPWA networks opportunity=3F What trends, challenges and barriers are influencing its growth=3F How is the ecosystem evolving by segment and region=3F What will the market size be in 2020 and at what rate will it grow=3F Which regions and submarkets will see the highest percentage of growth=3F How are smart city initiatives driving LPWA network investments=3F What are the key performance characteristics of LPWA technologies such as S= igfox, LoRa and NB-IOT=3F How does regulation impact the adoption of LPWA networks=3F Do LPWA networks pose a threat to cellular network technologies=3F Who are the key market players and what are their strategies=3F What strategies should LPWA technology providers, mobile operators, MVNOs, = aggregators, IoT platform providers and other ecosystem players adopt to re= main competitive=3F Report Pricing: Single User License: USD 2,500 Company Wide License: USD 3,500 Ordering Process: Please contact Andy Silva on andy.silva@snscommunication.com Provide the following information: 1. Report Title - 2. Report License - (Single User/Company Wide) 3. Name - 4. Email - 5. Job Title - 6. Company - 7. Invoice Address - Please contact me if you have any questions, or wish to purchase a copy. Ta= ble of contents and List of figures mentioned below for your better inside. I look forward to hearing from you. Kind Regards Andy Silva Marketing Executive Signals and Systems Telecom Reef Tower Jumeirah Lake Towers Sheikh Zayed Road Dubai, UAE =20 ___________________________________________________________________________= __________________________________________________________________________ =20 Table of Content =20 1.1 Executive Summary 1.2 Topics Covered 1.3 Historical Revenue & Forecast Segmentation 1.4 Key Questions Answered 1.5 Key Findings 1.6 Methodology 1.7 Target Audience 1.8 Companies & Organizations Mentioned =20 Chapter 2: An Overview of LPWA Networks 2.1 M2M Networks & the IoT Vision 2.1.1 What is M2M Technology=3F 2.1.2 The IoT Vision 2.1.3 M2M & IoT Architecture 2.2 The Limitations of Traditional M2M Networking Technologies 2.3 What are LPWA Networks=3F 2.4 Key Characteristics of LPWA Networks 2.4.1 Long Range & Strong Propagation 2.4.2 Star Network Topology 2.4.3 Low Data Rates 2.4.4 Low Power Consumption 2.4.5 Battery Life Requirements 2.4.6 Scalability 2.4.7 Low Cost Modules & Infrastructure 2.4.8 Supplementary Features 2.5 Market Growth Drivers 2.5.1 Addressing Low Throughput IoT Use Cases 2.5.2 Cost Saving Potential 2.5.3 Energy Saving: Towards Green IoT Networks 2.5.4 The 2G Sunset 2.5.5 Regulatory Initiatives & Mandates 2.5.6 Interest from Vertical Markets 2.5.7 Commitments by Industry Giants 2.6 Market Barriers 2.6.1 Lack of Standardization 2.6.2 Interference Concerns 2.6.3 Low Revenue per Connection 2.6.4 Integration Complexities =20 Chapter 3: LPWA Networking Technologies 3.1 UNB (Ultra Narrow Band) 3.1.1 Sigfox 3.1.2 Telensa 3.2 LoRa Alliance 3.2.1 Semtech=92s LoRA RF Platform 3.2.2 LoRaWAN 3.2.3 Link Labs=92 Symphony Link 3.3 Weightless SIG 3.3.1 Weightless-W 3.3.2 Weightless-N 3.3.3 Weightless-P 3.4 Ingenu=92s RPMA (Random Phase Multiple Access) 3.5 3GPP Technologies 3.5.1 NB-IOT (Narrow Band IOT) 3.5.2 Clean-Slate Approach: New Air Interface 3.5.3 NB-LTE (Narrow Band LTE) 3.5.4 EC-GSM (Extended Coverage GSM) 3.6 IEEE 802.11 ah & af 3.7 Spectrum Options for LPWA Networks 3.7.1 ISM (Industrial, Scientific, and Medical Radio) Bands 3.7.2 TVWS (TV White Spaces) 3.7.3 Licensed Spectrum 3.8 Competing M2M Networking Technologies 3.8.1 Traditional Cellular Networks 3.8.1.1 2G & 3G 3.8.1.2 LTE 3.8.1.3 5G 3.8.2 Satellite Communications 3.8.3 Wireline Networks 3.8.4 Short Range Networks 3.8.4.1 WiFi 3.8.4.2 Bluetooth 3.8.4.3 ZigBee 3.8.5 Others =20 Chapter 4: Vertical Market Applications, Opportunities & Case Studies 4.1 Agriculture 4.1.1 Precision Agriculture 4.1.2 Livestock Management 4.1.3 Agricultural Equipment Monitoring 4.2 Asset Management & Logistics 4.2.1 Maintaining Real-Time Asset Inventories 4.2.2 Supply Chain Visibility 4.2.3 Tracking Containers & Goods 4.2.4 Monitoring of Shipment Conditions 4.2.5 Other Applications 4.3 Automotive & Transportation 4.3.1 Tracking & Location Services 4.3.2 Remote Vehicle Management 4.3.3 Safety & Security 4.3.4 Other Applications 4.4 Consumer Applications & Home Automation 4.4.1 Wide Area Tracking 4.4.2 Sports & Fitness 4.4.3 Smart Homes & Intelligent Appliances 4.5 Energy & Utilities 4.5.1 Smart Metering 4.5.2 Applications in the Oil & Gas Sector 4.6 Healthcare 4.6.1 Health & Wellness Monitoring 4.6.2 Diagnostic Tools 4.6.3 Connected Prescription Reminders 4.6.4 Other Applications 4.7 Intelligent Buildings & Infrastructure 4.7.1 Intelligent Buildings 4.7.2 Public Infrastructure Management 4.7.3 Parking Management 4.7.4 Lighting Control 4.7.5 Waste Management 4.7.6 Environmental Monitoring & Other Applications 4.8 Public Safety, Security & Surveillance 4.8.1 Perimeter Access Control 4.8.2 Connected Security Alarms 4.8.3 Other Applications 4.9 Retail & Vending 4.9.1 POS (Point of Sale) Applications 4.9.2 Intelligent Shopping 4.9.3 Smart Restocking 4.9.4 Other Applications 4.10 Other Verticals 4.11 LPWA Deployment Case Studies 4.11.1 BT: Creating the UK=92s First IoT Enabled Smart City 4.11.2 Du: Supporting Smart City Initiatives with LPWA Networking 4.11.3 Enevo: Waste Logistics Optimization 4.11.4 Securitas: LPWA Powered Home Security Monitoring 4.11.5 Senet: Optimizing Fuel Delivery with LPWA Networking 4.11.6 Smarteo Water: Enabling Smart Metering with LPWA Networking 4.11.7 Telensa: Smart Parking & Street Lighting 4.11.8 The Things Network: Crowdsouring IoT Networks =20 Chapter 5: Regulatory Landscape 5.1 3GPP (3rd Generation Partnership Project) 5.2 LoRa Alliance 5.3 Weightless SIG 5.4 IEEE (Institute of Electrical and Electronics Engineers) 5.5 Wireless IoT Forum 5.6 GSMA =20 Chapter 6: Industry Roadmap & Value Chain 6.1 Industry Roadmap 6.1.1 2015 =96 2020: Initial Rollouts to Support Smart City Applications 6.1.2 2020 =96 2025: Moving Towards Licensed Spectrum & Technologies 6.1.3 2025 =96 2030 & Beyond: Cannibalizing Legacy Cellular M2M Connectio= ns 6.2 Value Chain 6.2.1 Enabling Technology 6.2.1.1 Hardware Providers 6.2.1.2 Software Providers 6.2.2 Connectivity 6.2.2.1 Mobile Operators 6.2.2.2 MVNOs & Aggregators 6.2.3 Service Enablement 6.2.3.1 CDP (Connected Device Platform) Providers 6.2.3.2 Application Platform Providers 6.2.4 Vertical Solutions 6.2.4.1 System Integrators 6.2.4.2 Vertical Market Specialists 6.2.5 Other Ecosystem Players 6.2.5.1 Cloud Platform Providers 6.2.5.2 Big Data & Analytics Specialists 6.2.5.3 Supplementary Service Providers =20 Chapter 7: Key Market Players 7.1 Accellus Communication Networks 7.2 Actility 7.3 Adeunis RF 7.4 Aerea 7.5 AMBER Wireless 7.6 Arkessa 7.7 Arqiva 7.8 AT&T 7.9 Atim 7.10 Atmel Corporation 7.11 Augtek 7.12 AXSEM 7.13 Bouygues Telecom 7.14 BT Group 7.15 Cellnex Telecom (Abertis Telecom) 7.16 CG-Wireless 7.17 Cisco Systems 7.18 Digi International 7.19 DT (Deutsche Telekom) 7.20 Du (Emirates Integrated Telecommunications Company) 7.21 Elster Group 7.22 Eolane 7.23 Ericsson 7.24 Etisalat Group 7.25 Eutelsat 7.26 FLASHNET 7.27 Helium Systems 7.28 Homerider Systems 7.29 Hope RF (Hope Microelectronics) 7.30 Huawei 7.31 IBM 7.32 IMST 7.33 Ingenu 7.34 Intel Corporation 7.35 Kerlink 7.36 KPN 7.37 Libelium 7.38 Link Labs 7.39 M2COMM (M=B2Communication) 7.40 M2M Spectrum Networks 7.41 Microchip Technology 7.42 Multi-Tech Systems 7.43 Nemeus 7.44 Nettrotter 7.45 NNNCo (National Narrowband Network Communications) 7.46 Nokia 7.47 NTT DoCoMo 7.48 Nwave Technologies 7.49 Orange 7.50 OrbiWise 7.51 PicoWAN 7.52 Plextek 7.53 Proximus Group 7.54 Qowiso 7.55 Qualcomm 7.56 Radiocrafts 7.57 Sagemcom 7.58 Samsara Networks 7.59 Samsung Electronics 7.60 Semtech Corporation 7.61 Senet 7.62 Sierra Wireless 7.63 Sigfox 7.64 Silicon Labs (Silicon Laboratories) 7.65 SimpleCell Networks 7.66 Singtel 7.67 SK Telecom 7.68 Stream Technologies 7.69 Swisscom 7.70 Tata Communications 7.71 Tele2 7.72 Telecom Design 7.73 Telecom Italia 7.74 Telef=F3nica 7.75 Telensa 7.76 Telit Communications 7.77 Telkom SA 7.78 Telstra Corporation 7.79 The Things Network 7.80 TI (Texas Instruments) 7.81 U-blox 7.82 Vodafone Group 7.83 WAVIoT =20 Chapter 8: Market Analysis & Forecasts 8.1 Global Outlook of LPWA Networks 8.1.1 LPWA Network Connections 8.1.2 LPWA Network IoT Service Revenue 8.2 Connectivity vs. Application Services 8.2.1 Connectivity Revenue 8.2.2 IoT Application Service Revenue 8.3 Vertical Market Segmentation 8.3.1 Agriculture 8.3.2 Asset Management & Logistics 8.3.3 Automotive & Transportation 8.3.4 Consumer Applications & Home Automation 8.3.5 Energy & Utilities 8.3.6 Healthcare 8.3.7 Intelligent Buildings & Infrastructure 8.3.8 Public Safety, Security & Surveillance 8.3.9 Retail & Vending 8.3.10 Others 8.4 Regional Segmentation 8.4.1 Asia Pacific 8.4.2 Eastern Europe 8.4.3 Middle East & Africa 8.4.4 Latin & Central America 8.4.5 North America 8.4.6 Western Europe =20 Chapter 9: Conclusion & Strategic Recommendations 9.1 Why is the Market Poised to Grow=3F 9.2 Competitive Industry Landscape: Acquisitions, Alliances & Consolidation 9.3 Prospects of Licensed Spectrum for LPWA Networks 9.4 SWOT Analysis: LPWA vs. Competing Technologies 9.5 Geographic Outlook: Which Regions Offer the Highest Growth Potential=3F 9.6 Reducing LPWA Module Costs 9.7 Smart City Infrastructure Projects: Driving LPWA Network Rollouts 9.8 Impact on Mobile Operators: Opportunities & Challenges 9.9 Strategic Recommendations 9.9.1 LPWA Technology Providers 9.9.2 Other Enabling Technology Providers 9.9.3 Mobile Operators 9.9.4 MVNOs & Aggregators 9.9.5 IoT Platform Providers 9.9.6 System Integrators & Vertical Market Specialists =20 List of Figures Figure 1: The IoT Vision Figure 2: M2M & IoT Network Architecture Figure 3: Global Wide Area M2M Connections by Technology: 2015 =96 2030 Figure 4: Telensa=92s Smart Lighting Solution Figure 5: LoRaWAN Architecture Figure 6: Comparison of Weightless Open LPWA Standards Figure 7: LPWA Networks Industry Roadmap Figure 8: LPWA Networks Value Chain Figure 9: Global LPWA Network Connections: 2015 - 2030 (Millions) Figure 10: Global LPWA Network IoT Service Revenue: 2015 - 2030 ($ Billion) Figure 11: Global LPWA Network IoT Service Revenue by Submarket: 2015 - 203= 0 ($ Billion) Figure 12: Global LPWA Network Connectivity Revenue: 2015 - 2030 ($ Billion) Figure 13: Global LPWA Network IoT Application Service Revenue: 2015 - 2030= ($ Billion) Figure 14: Global LPWA Network Connections by Vertical: 2015 - 2030 (Millio= ns) Figure 15: Global LPWA Network IoT Service Revenue by Vertical: 2015 - 2030= ($ Billion) Figure 16: Global LPWA Network Connections in Agriculture: 2015 - 2030 (Mil= lions) Figure 17: Global LPWA Network IoT Service Revenue in Agriculture: 2015 - 2= 030 ($ Billion) Figure 18: Global LPWA Network Connections in Asset Management & Logistics:= 2015 - 2030 (Millions) Figure 19: Global LPWA Network IoT Service Revenue in Asset Management & Lo= gistics: 2015 - 2030 ($ Billion) Figure 20: Global LPWA Network Connections in Automotive & Transportation: = 2015 - 2030 (Millions) Figure 21: Global LPWA Network IoT Service Revenue in Automotive & Transpor= tation: 2015 - 2030 ($ Billion) Figure 22: Global LPWA Network Connections in Consumer Applications & Home = Automation: 2015 - 2030 (Millions) Figure 23: Global LPWA Network IoT Service Revenue in Consumer Applications= & Home Automation: 2015 - 2030 ($ Billion) Figure 24: Global LPWA Network Connections in Energy & Utilities: 2015 - 20= 30 (Millions) Figure 25: Global LPWA Network IoT Service Revenue in Energy & Utilities: 2= 015 - 2030 ($ Billion) Figure 26: Global LPWA Network Connections in Healthcare: 2015 - 2030 (Mill= ions) Figure 27: Global LPWA Network IoT Service Revenue in Healthcare: 2015 - 20= 30 ($ Billion) Figure 28: Global LPWA Network Connections in Intelligent Buildings & Infra= structure: 2015 - 2030 (Millions) Figure 29: Global LPWA Network IoT Service Revenue in Intelligent Buildings= & Infrastructure: 2015 - 2030 ($ Billion) Figure 30: Global LPWA Network Connections in Public Safety, Security & Sur= veillance: 2015 - 2030 (Millions) Figure 31: Global LPWA Network IoT Service Revenue in Public Safety, Securi= ty & Surveillance: 2015 - 2030 ($ Billion) Figure 32: Global LPWA Network Connections in Retail & Vending: 2015 - 2030= (Millions) Figure 33: Global LPWA Network IoT Service Revenue in Retail & Vending: 201= 5 - 2030 ($ Billion) Figure 34: Global LPWA Network Connections in Other Verticals: 2015 - 2030 = (Millions) Figure 35: Global LPWA Network IoT Service Revenue in Other Verticals: 2015= - 2030 ($ Billion) Figure 36: LPWA Network Connections by Region: 2015 - 2030 (Millions) Figure 37: LPWA Network IoT Service Revenue by Region: 2015 - 2030 ($ Billi= on) Figure 38: Asia Pacific LPWA Network Connections: 2015 - 2030 (Millions) Figure 39: Asia Pacific LPWA Network IoT Service Revenue: 2015 - 2030 ($ Bi= llion) Figure 40: Eastern Europe LPWA Network Connections: 2015 - 2030 (Millions) Figure 41: Eastern Europe LPWA Network IoT Service Revenue: 2015 - 2030 ($ = Billion) Figure 42: Middle East & Africa LPWA Network Connections: 2015 - 2030 (Mill= ions) Figure 43: Middle East & Africa LPWA Network IoT Service Revenue: 2015 - 20= 30 ($ Billion) Figure 44: Latin & Central America LPWA Network Connections: 2015 - 2030 (M= illions) Figure 45: Latin & Central America LPWA Network IoT Service Revenue: 2015 -= 2030 ($ Billion) Figure 46: North America LPWA Network Connections: 2015 - 2030 (Millions) Figure 47: North America LPWA Network IoT Service Revenue: 2015 - 2030 ($ B= illion) Figure 48: Western Europe LPWA Network Connections: 2015 - 2030 (Millions) Figure 49: Western Europe LPWA Network IoT Service Revenue: 2015 - 2030 ($ = Billion) Figure 50: SWOT Matrix: LPWA vs. Competing M2M Networking Technologies Figure 51: Price Breakdown of an LPWA Module =20 Thank you once again and looking forward to hearing from you. =20 Kind Regards =20 Andy Silva Marketing Executive Signals and Systems Telecom andy.silva@snscommunication.com Reef Tower Jumeirah Lake Towers Sheikh Zayed Road Dubai, UAE =20 =20 To unsubscribe send an email with unsubscribe in the subject line to: remov= e@snsreports.com