| ID: | 5829 |
| From: | rs...@disroot.org |
| Date: | Thu, 01 Sep 2022 16:23:16 +0200 |
| Subject: | Re: [pcb-rnd] pcb-rnd on OpenBSD |
| in-reply-to: | 5826 from rn...@igor2.repo.hu |
| replies: | 5831 from rn...@igor2.repo.hu |
rnd2@igor2.repo.hu wrote: >=20 > Anyway, let's look at one of these that looks relevant: >=20 > >pcb-rnd:/usr/X11R6/lib/libX11.so.16.1: /usr/X11R6/lib/libX11.so.18.0 : W= ARNING: symbol(_XimXTransSocketINETFuncs) size mismatch, relink your progra= m >=20 > if I understand it correctly, this is the dynamic linker saying that=20 > pcb-rnd executable was originally linked against binary version 16.1 of=20= > libX11.so, but your system currently has version 18.0 and the new version= =20 > is potentially binary-incompatible with the old. >=20 > It asks you to re-link pcb-rnd, which is a reasonable thing to do in that= =20 > situation. We don't have a "make relink", so what you could do is this: >=20 > 1. go to pcb-rnd trunk/src >=20 > 2. rm pcb-rnd >=20 > 3. make >=20 > This should not recompile anything, only link the executable again. >=20 > > > > > >I don't understand if these messages are related to the pcb-rnd program=20= > >itself, or if it points to some deeper system-wide problem. Can anybody=20= > >comment on this? >=20 > If it is what I think it is, then it's sort of normal operation: you=20 > compiled pcb-rnd from source on a (specific state of) system then upgrade= d=20 > the system but not pcb-rnd. Your dynamic linker figures that upon startup= =2E The thing is that I have not upgraded the system in the meanwhile. The behaviour is as described immediately after the compilation of the program;= ie, not even removing pcb-rnd in the src directory and running make changes the= matter. [I actually had this idea, too, and I recompiled both librnd and pcb-rnd, starting from the .tar.gz in both cases again, but to no avail= ...] =20 Thanks Ruda
Reply subtree:
5829 Re: [pcb-rnd] pcb-rnd on OpenBSD from rs...@disroot.org
5831 Re: [pcb-rnd] pcb-rnd on OpenBSD from rn...@igor2.repo.hu