On Tue, Feb 28, 2023 at 05:41:46PM +0000, Stuart Henderson wrote:
> On 2023/02/28 10:02, Tracey Emery wrote:
> > Ping.
> >
> > On Fri, Feb 03, 2023 at 03:53:11PM -0700, Tracey Emery wrote:
> > > Hello ports,
> > >
> > > This brings kicad and friends to 6.0.11. However, something was updated
> > > in the BSDs which crashes the footprint assignment tool. The thread
> > > regarding this can be seen here:
> > >
> > > https://gitlab.com/kicad/code/kicad/-/issues/13029
> > >
> > > The kicad folks don't seem interested in trying to figure out the root
> > > of the problem. Perhaps someone here can hunt down what is going on.
> > >
> > > As of 6.0.10 they were supposed to cherrypick a diff to keep kicad from
> > > crashing completely, but it still doesn't exists in the archive
> > > downloads. I've informed them about that as well and added a local
> > > patch:
> > >
> > > https://gitlab.com/kicad/code/kicad/-/commit/1a670f467392fb6605ce1b88316501518a256eb0
> > >
> > > If you haven't read through the end of the issues thread, a FreeBSD user
> > > found a workaround, which I've confirmed works in OpenBSD as well. To
> > > successfully open a populated footprint assignment tool, open the
> > > footprint editor first. Noting that here for our users.
>
> Reads OK but I haven't tested.
>
> Does that problem warrant a mention in the port somewhere (i.e.
> either MESSAGE or pkg-readme)?
Yes, I think that is a good idea. It is an annoying enough problem to
warrant a MESSAGE ... unless we want to pkg-readme with the above
mentioned workaround link. I'll work something up.
>
> I can't rearrange enough space on my laptop to install kicad, the
> upstream issue suggests something to do with loading libraries?
> Maybe look for clues running it with LD_DEBUG set?
>
--
Tracey Emery
No comments:
Post a Comment