os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Add 2017Q2 entry on ports on non-x86 from linimon

Browse source
This commit is contained in:
Benjamin Kaduk 2017-07-02 21:49:30 +00:00
parent b651895a1f
commit 06ce7e1a3b
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=50435
1 changed files with 57 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

57
en_US.ISO8859-1/htdocs/news/status/report-2017-04-2017-06.xml
View file

@ -488,4 +488,61 @@
accurate representations.</p> accurate representations.</p>
</body> </body>
</project> </project>
<project cat='ports'>
<title>Updating Port Metadata for non-x86 Architectures</title>
<contact>
<person>
<name>
<given>Mark</given>
<common>Linimon</common>
</name>
<email>linimon@FreeBSD.org</email>
</person>
</contact>
<links>
<url href="http://thunderx1.nyi.FreeBSD.org/jail.html?mastername=110arm64-default">aarch64 Poudriere Machine</url>
<url href="http://beefy8.nyi.FreeBSD.org/jail.html?mastername=head-armv6-default">armv6 Poudriere Machine</url>
</links>
<body>
<p>I have been analyzing the error logs from ports builds for
all non-x86 architectures, including both the logs published
on the package build cluster and also other builds of
powerpc64 and sparc64.</p>
<p>From this analysis, I have marked almost all the failing
ports as either <tt>BROKEN</tt> or
<tt>NOT_FOR</tt>/<tt>ONLY_FOR</tt>, as appropriate.</p>
<p>The intent of this work is not to make life harder for
anyone, but rather, in fact, the opposite. With these
definitions in place, it is possible to scan the poudriere
bulk build output (the &quot;Ignored ports&quot; portion, in
particular) and see quickly what ports are failing to build
and why. Previously, finding the exact reason why a build
failed needed some research (<tt>portsmon</tt> only models
failure messages on amd64). Additionally, it is extremely
difficult to work through several hundred logs that simply say
&quot;failed to compile&quot;, &quot;failed to link&quot;, and
so forth.</p>
<p>This is part of an effort to identify where we need further
work to bring sufficient Ports Collection support to, e.g.,
armv6 and aarch64 to bring them closer to true Tier-1
status.</p>
<p>To further facilitate locating patterns in the Poudriere
output, I have begun reworking some existing
<tt>BROKEN</tt>/<tt>NOT_FOR</tt>/<tt>ONLY_FOR</tt> messages so
that they will sort more easily. This includes sorting the
order of the <tt>ARCH</tt> definitions.</p>
<p>Many people have been doing great work on fixing the
individual ports. I hope that my work makes their jobs
somewhat easier.</p>
</body>
</project>
</report> </report>