Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 22 Oct 2024 22:52:26 +0200 (CEST)
From:      Ronald Klop <ronald-lists@klop.ws>
To:        Mark Millard <marklmi@yahoo.com>
Cc:        FreeBSD Mailing List <freebsd-ports@freebsd.org>, Antoine Brodin <antoine@freebsd.org>, Philip Paeps <philip@freebsd.org>, FreeBSD ARM List <freebsd-arm@freebsd.org>
Subject:   Re: ampere2's main-armv7 crashed after only 3  min 51 sec, nothing started to build; libdm.so.{6->7} issues
Message-ID:  <1902543396.49319.1729630346915@localhost>
In-Reply-To: <4FDD9A40-B415-42B5-BA89-B89565C2A168@yahoo.com>

next in thread | previous in thread | raw e-mail | index | archive | help
------=_Part_49318_2106664272.1729630346910
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Ampere2 is building armv7 again
https://pkg-status.freebsd.org/ampere2/build.html?mastername=main-armv7-default&build=p94c4ac6b071b_sc87b3f0006
BTW: I made a graph that shows how old a pkg repo is per architecture.It shows that arm/aarch64 is significantly older than i386/amd64.  But also that armv7 is way behind the rest now.

https://www.klop.ws/pkgstats/pkg-age.html

Regards,Ronald

Van: Mark Millard <marklmi@yahoo.com>
Datum: 14 oktober 2024 01:41
Aan: Ronald Klop <ronald-lists@klop.ws>
CC: Antoine Brodin <antoine@freebsd.org>, FreeBSD Mailing List <freebsd-ports@freebsd.org>, FreeBSD ARM List <freebsd-arm@freebsd.org>, Philip Paeps <philip@freebsd.org>
Onderwerp: Re: ampere2's main-armv7 crashed after only 3  min 51 sec, nothing started to build; libdm.so.{6->7} issues

> 
> 
> On Oct 13, 2024, at 13:18, Ronald Klop  wrote:
> 
> > On ampere3 armv7 builds crashed in the same way. 
> > 
> > https://pkg-status.freebsd.org/ampere3/
> > 
> > Regards,
> > Ronald
> > 
> >> Van: Mark Millard 
> >> Datum: 13 oktober 2024 22:13
> >> Aan: Antoine Brodin , FreeBSD Mailing List , FreeBSD ARM List 
> >> CC: Philip Paeps 
> >> Onderwerp: ampere2's main-armv7 crashed after only 3 min 51 sec, nothing started to build; libdm.so.{6->7} issues
> >> 
> >> main-armv7 crashed before it was at a stage that has public log files to look
> >> at.
> >> 
> >> I report this mostly because the currently distributed main-packages for ports
> >> that involve use of libmd.so.6 are broken because main now has/uses libmd.so.7
> >> instead --so libmd.so.6 tends to be missing. Even when libmd.so.6 and
> >> libmd.so.7 both exist, the pkg (non -static) command is broken from the
> >> recursive dependencies ending up referencing both. (pkg-static works but pkg
> >> does not.)
> >> 
> >> It might be that the crash is because of the libmd.so.6 to libmd.so.7 change
> >> in main. But I've no access to logs to look at.
> >> 
> >> It would be good to avoid having another main-arm64 bulk -a happen before
> >> main-armv7 has a chance to produce main-armv7 packages with libmd.so.7
> >> references so that ports are again good for (modern) main-FreeBSD [so: 15].
> >> 
> >> But it seems that, for main-arm* port-packages, either:
> >> 
> >> 0) various distributed ports are incompatible with libmd.so.7 based
> >>     main-FreeBSD (the current context for main-armv7)
> >> 
> >> vs.
> >> 
> >> 1) various distributed ports will be incompatible with libmd.so.6
> >>      based main-FreeBSD (so: older main/15 FreeBSD installations):
> >>      the future contexts for main-armv7 and main-arm64 (and more).
> >> 
> >> 
> >> FYI: The libmd.so.{6->7} change dates back to 2024-Sep-30 in FreeBSD's main.
> >> But the __FreeBSD_version 150002{3->4} change did not happen until
> >> 2024-Oct-02.
> >> 
> >> 
> >> main-powerpc-default's status for such:
> >> 
> >> Looks like FreeBSD:15:powerpc/latest/ was last updated on 2024-Mar-07
> >> and so might not have the issue --by no longer having port-package
> >> updates of any kind. (32-bit powerpc is not to be supported by
> >> releng/15.0 as I understand: The only 32-bit platform will be armv7
> >> as I understand.)
> 
> Looks like I should have done a wider exploration instead
> of presuming just main-armv7 was broken.
> 
> An interesting point is that none of the *-armv7-quarterly
> jails have failed so far. Just the *-armv7-default have
> failed:
> 
> main-armv7-default p149fe86b8e79_s149e1af6a ,
> 141releng-armv7-default 1f84c1fae602 ,
> 133releng-armv7-default 1f84c1fae602 .
> 
> I'll note that the arm64 ones did not fail:
> 
> main-arm64-default p149fe86b8e79_s149e1af6ae4
> 141arm64-default 1f84c1fae602 ,
> 133arm64-default 1f84c1fae602 .
> 
> 133releng-armv7-default is the oldest failure for this issue:
> Sun, 06 Oct 2024 23:33:31 GMT start with elapsed: 00:05:26 .
> 
> 133releng-armv7-default had a  prior build: Thu, 19 Sep 2024 19:55:19 GMT 58:03:54
> 
> 141releng-armv7-default had no prior build attempts ( was: 140releng-armv7-default ).
> 
>      main-armv7-default had a  prior build: Thu, 03 Oct 2024 04:21:42 GMT 61:50:05
> 
> 
> I wonder what a common change is across the failing examples.
> 
> 
> ===
> Mark Millard
> marklmi at yahoo.com
> 
> 
> 
> 
> 
------=_Part_49318_2106664272.1729630346910
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: quoted-printable

<html><head></head><body>Ampere2 is building armv7 again<br class=3D"rw_ext=
ra"><br><a href=3D"https://pkg-status.freebsd.org/ampere2/build.html?master=
name=3Dmain-armv7-default&amp;build=3Dp94c4ac6b071b_sc87b3f0006">https://pk=
g-status.freebsd.org/ampere2/build.html?mastername=3Dmain-armv7-default&amp=
;build=3Dp94c4ac6b071b_sc87b3f0006</a><br class=3D"rw_extra"><br>BTW: I mad=
e a graph that shows how old a pkg repo is per architecture.<br class=3D"rw=
_extra">It shows that arm/aarch64 is significantly older than i386/amd64. &=
nbsp;But also that armv7 is way behind the rest now.<br><div><a href=3D"htt=
ps://www.klop.ws/pkgstats/pkg-age.html">https://www.klop.ws/pkgstats/pkg-ag=
e.html</a><br><br>Regards,<br class=3D"rw_extra">Ronald<br class=3D"rw_extr=
a"><br><p><small><strong>Van:</strong> Mark Millard &lt;marklmi@yahoo.com&g=
t;<br><strong>Datum:</strong> 14 oktober 2024 01:41<br><strong>Aan:</strong=
> Ronald Klop &lt;ronald-lists@klop.ws&gt;<br><strong>CC:</strong> Antoine =
Brodin &lt;antoine@freebsd.org&gt;, FreeBSD Mailing List &lt;freebsd-ports@=
freebsd.org&gt;, FreeBSD ARM List &lt;freebsd-arm@freebsd.org&gt;, Philip P=
aeps &lt;philip@freebsd.org&gt;<br><strong>Onderwerp:</strong> Re: ampere2'=
s main-armv7 crashed after only 3  min 51 sec, nothing started to build; li=
bdm.so.{6-&gt;7} issues<br></small></p><blockquote style=3D"margin-left: 5p=
x; border-left: 3px solid #ccc; margin-right: 0px; padding-left: 5px;"><div=
 class=3D"MessageRFC822Viewer" id=3D"P"><!-- P -->
<!-- processMimeMessage --><div class=3D"TextPlainViewer" id=3D"P.P"><!-- P=
.P -->On Oct 13, 2024, at 13:18, Ronald Klop <ronald-lists@klop.ws> wrote:<=
br>
<br>
&gt; On ampere3 armv7 builds crashed in the same way. <br>
&gt; <br>
&gt; <a href=3D"https://pkg-status.freebsd.org/ampere3/">https://pkg-status=
.freebsd.org/ampere3/</a><br>
&gt; <br>
&gt; Regards,<br>
&gt; Ronald<br>
&gt; <br>
&gt;&gt; Van: Mark Millard <marklmi@yahoo.com><br>
&gt;&gt; Datum: 13 oktober 2024 22:13<br>
&gt;&gt; Aan: Antoine Brodin <antoine@freebsd.org>, FreeBSD Mailing List <f=
reebsd-ports@freebsd.org>, FreeBSD ARM List <freebsd-arm@freebsd.org><br>
&gt;&gt; CC: Philip Paeps <philip@freebsd.org><br>
&gt;&gt; Onderwerp: ampere2's main-armv7 crashed after only 3 min 51 sec, n=
othing started to build; libdm.so.{6-&gt;7} issues<br>
&gt;&gt; <br>
&gt;&gt; main-armv7 crashed before it was at a stage that has public log fi=
les to look<br>
&gt;&gt; at.<br>
&gt;&gt; <br>
&gt;&gt; I report this mostly because the currently distributed main-packag=
es for ports<br>
&gt;&gt; that involve use of libmd.so.6 are broken because main now has/use=
s libmd.so.7<br>
&gt;&gt; instead --so libmd.so.6 tends to be missing. Even when libmd.so.6 =
and<br>
&gt;&gt; libmd.so.7 both exist, the pkg (non -static) command is broken fro=
m the<br>
&gt;&gt; recursive dependencies ending up referencing both. (pkg-static wor=
ks but pkg<br>
&gt;&gt; does not.)<br>
&gt;&gt; <br>
&gt;&gt; It might be that the crash is because of the libmd.so.6 to libmd.s=
o.7 change<br>
&gt;&gt; in main. But I've no access to logs to look at.<br>
&gt;&gt; <br>
&gt;&gt; It would be good to avoid having another main-arm64 bulk -a happen=
 before<br>
&gt;&gt; main-armv7 has a chance to produce main-armv7 packages with libmd.=
so.7<br>
&gt;&gt; references so that ports are again good for (modern) main-FreeBSD =
[so: 15].<br>
&gt;&gt; <br>
&gt;&gt; But it seems that, for main-arm* port-packages, either:<br>
&gt;&gt; <br>
&gt;&gt; 0) various distributed ports are incompatible with libmd.so.7 base=
d<br>
&gt;&gt; &nbsp;&nbsp;&nbsp;&nbsp;main-FreeBSD (the current context for main=
-armv7)<br>
&gt;&gt; <br>
&gt;&gt; vs.<br>
&gt;&gt; <br>
&gt;&gt; 1) various distributed ports will be incompatible with libmd.so.6<=
br>
&gt;&gt; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;based main-FreeBSD (so: older main/1=
5 FreeBSD installations):<br>
&gt;&gt; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;the future contexts for main-armv7 a=
nd main-arm64 (and more).<br>
&gt;&gt; <br>
&gt;&gt; <br>
&gt;&gt; FYI: The libmd.so.{6-&gt;7} change dates back to 2024-Sep-30 in Fr=
eeBSD's main.<br>
&gt;&gt; But the __FreeBSD_version 150002{3-&gt;4} change did not happen un=
til<br>
&gt;&gt; 2024-Oct-02.<br>
&gt;&gt; <br>
&gt;&gt; <br>
&gt;&gt; main-powerpc-default's status for such:<br>
&gt;&gt; <br>
&gt;&gt; Looks like FreeBSD:15:powerpc/latest/ was last updated on 2024-Mar=
-07<br>
&gt;&gt; and so might not have the issue --by no longer having port-package=
<br>
&gt;&gt; updates of any kind. (32-bit powerpc is not to be supported by<br>
&gt;&gt; releng/15.0 as I understand: The only 32-bit platform will be armv=
7<br>
&gt;&gt; as I understand.)<br>
<br>
Looks like I should have done a wider exploration instead<br>
of presuming just main-armv7 was broken.<br>
<br>
An interesting point is that none of the *-armv7-quarterly<br>
jails have failed so far. Just the *-armv7-default have<br>
failed:<br>
<br>
main-armv7-default p149fe86b8e79_s149e1af6a ,<br>
141releng-armv7-default 1f84c1fae602 ,<br>
133releng-armv7-default 1f84c1fae602 .<br>
<br>
I'll note that the arm64 ones did not fail:<br>
<br>
main-arm64-default p149fe86b8e79_s149e1af6ae4<br>
141arm64-default 1f84c1fae602 ,<br>
133arm64-default 1f84c1fae602 .<br>
<br>
133releng-armv7-default is the oldest failure for this issue:<br>
Sun, 06 Oct 2024 23:33:31 GMT start with elapsed: 00:05:26 .<br>
<br>
133releng-armv7-default had a &nbsp;prior build: Thu, 19 Sep 2024 19:55:19 =
GMT 58:03:54<br>
<br>
141releng-armv7-default had no prior build attempts ( was: 140releng-armv7-=
default ).<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;main-armv7-default had a &nbsp;prior build: T=
hu, 03 Oct 2024 04:21:42 GMT 61:50:05<br>
<br>
<br>
I wonder what a common change is across the failing examples.<br>
<br>
<br>
=3D=3D=3D<br>
Mark Millard<br>
marklmi at yahoo.com<br>
<br>
</philip@freebsd.org></freebsd-arm@freebsd.org></freebsd-ports@freebsd.org>=
</antoine@freebsd.org></marklmi@yahoo.com></ronald-lists@klop.ws></div><!--=
 TextPlainViewer -->
<hr>
</div><!-- MessageRFC822Viewer -->
</blockquote><br><br><br></div></body></html>
------=_Part_49318_2106664272.1729630346910--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1902543396.49319.1729630346915>