Date: Thu, 7 Apr 2022 07:09:37 +0200 From: Mark Tinka <mark@tinka.africa> To: Kevin Oberman <rkoberman@gmail.com> Cc: "freebsd-questions@freebsd.org" <freebsd-questions@freebsd.org> Subject: Re: libxml2 Port Blocking Upgrades Message-ID: <8d1e18fb-9888-25bb-87dd-b3ac2f47559f@tinka.africa> In-Reply-To: <CAN6yY1s3q3bRUNm_hZzxFB1Y_1i5z-F2dyCUYYxvWRcbs7WjMw@mail.gmail.com> References: <77f02d06-0252-e8d2-f53f-0fa39fc0d58b@tinka.africa> <CAN6yY1s3q3bRUNm_hZzxFB1Y_1i5z-F2dyCUYYxvWRcbs7WjMw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
This is a multi-part message in MIME format.
--------------xHKxza0e50oirmhsukJRgYqH
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
On 4/7/22 01:22, Kevin Oberman wrote:
>
> I don't think that 262853 is the source of the problem, though I'm not
> sure from the provided information. A build with MAKE_JOBS_UNSAFE and
> some earlier bit of the log MIGHT make this clearer.
I tried this, and the issue was exactly the same.
> As far as I can tell, the libxml2 port does not install any .a libs,
> only the shareables (.so).
True. On systems that were not affected by this, no .a libs exist. On
others that are, .a libs are being looked for, and since they don't
exist, the update stops.
>
> In any case, I re-installed libxslt one minute and 25 seconds after
> the libxml2 commit with no issues on my 13-Stable system.
I tried this and it didn't work either. libxslt is still looking for
libxml2.a
Mark.
--------------xHKxza0e50oirmhsukJRgYqH
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<br>
<br>
<div class="moz-cite-prefix">On 4/7/22 01:22, Kevin Oberman wrote:<br>
<br>
</div>
<blockquote type="cite"
cite="mid:CAN6yY1s3q3bRUNm_hZzxFB1Y_1i5z-F2dyCUYYxvWRcbs7WjMw@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr"><br>
<div style="font-family:tahoma,sans-serif;font-size:small"
class="gmail_default">I don't think that 262853 is the source
of the problem, though I'm not sure from the provided
information. A build with MAKE_JOBS_UNSAFE and some earlier
bit of the log MIGHT make this clearer.</div>
</div>
</blockquote>
<br>
I tried this, and the issue was exactly the same.<br>
<br>
<br>
<blockquote type="cite"
cite="mid:CAN6yY1s3q3bRUNm_hZzxFB1Y_1i5z-F2dyCUYYxvWRcbs7WjMw@mail.gmail.com">
<div dir="ltr">
<div style="font-family:tahoma,sans-serif;font-size:small"
class="gmail_default"> As far as I can tell, the libxml2 port
does not install any .a libs, only the shareables (.so).<br>
</div>
</div>
</blockquote>
<br>
True. On systems that were not affected by this, no .a libs exist.
On others that are, .a libs are being looked for, and since they
don't exist, the update stops.<br>
<br>
<br>
<blockquote type="cite"
cite="mid:CAN6yY1s3q3bRUNm_hZzxFB1Y_1i5z-F2dyCUYYxvWRcbs7WjMw@mail.gmail.com">
<div dir="ltr">
<div><br>
</div>
<div>
<div style="font-family:tahoma,sans-serif;font-size:small"
class="gmail_default">In any case, I re-installed libxslt
one minute and 25 seconds after the libxml2 commit with no
issues on my 13-Stable system.<br>
</div>
</div>
</div>
</blockquote>
<br>
I tried this and it didn't work either. libxslt is still looking for
libxml2.a<br>
<br>
Mark.<br>
</body>
</html>
--------------xHKxza0e50oirmhsukJRgYqH--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?8d1e18fb-9888-25bb-87dd-b3ac2f47559f>