On 31/01/25 19:13, Baptiste Daroussin wrote:
On Fri 31 Jan 18:18, Guido Falsi wrote:
On 27/01/25 10:56, Nuno Teixeira wrote:
Hello Rainer,
> Wouldn't this be the right time to get Bapt@ involved? After all, he has
> worked intensively on the pkg updates.
Yes it is. I'm CC'ing bapt@.
Since this issue was pestering me while testing multiple ports with
unnecessarily lengthy rebuilds I took a look.
I have posted a pull request for poudriere [1] with a fix/workaround that
works for me and allows me to have a functional build machine.
I'm not sure if this fix is completely correct, but maybe it can be useful
to other people as a work around.
[1] https://github.com/freebsd/poudriere/pull/1204
--
Guido Falsi <m...@madpilot.net>
at quick glance it sounds like a bug in pkg I ll have a look at it next week
Bapt
It looks like the issue is related to this kind of pkg output:
> pkg query %b gcc13
libubsan.so.1:32
libubsan.so.1
libstdc++.so.6:32
libstdc++.so.6
libquadmath.so.0:32
libquadmath.so.0
liblto_plugin.so
libitm.so.1:32
libitm.so.1
libgomp.so.1:32
libgomp.so.1
libgfortran.so.5:32
libgfortran.so.5
libgccjit.so.0
libgcc_s.so.1:32
libgcc_s.so.1
libcp1plugin.so.0
libcc1plugin.so.0
libcc1.so.0
libatomic.so.1:32
libatomic.so.1
libasan.so.8:32
libasan.so.8
the '*:32' lines confuse poudriere.
Posting this hoping this is helpful in fixing the issue.
--
Guido Falsi <m...@madpilot.net>
