It is installed from source code I have used the PCB program. And it was
early yesterday the problem began. Before PCB has been working on my
Raspberry Pi4 with OpenBSD 7.2. The only difference is update of OpenBSD to
current version. The system update I did before this one is a few weeks
ago, and there was no problem.
I know PCB-RND come from PCB but I tried it today and the result was almost
the same:
openbsd6$ pcb-rnd
pcb-rnd:/usr/X11R6/lib/modules/dri/swrast_dri.so: undefined symbol
'util_streaming_load_memcpy'
libGL error: MESA-LOADER: failed to open swrast: Cannot load specified
object (search paths /usr/X11R6/lib/modules/dri, suffix _dri)
libGL error: failed to load driver: swrast
(pcb-rnd:14635): GtkGLExt-WARNING **: 14:43:43.517: cannot create
GdkGLContext
(pcb-rnd:14635): GdkGLExt-CRITICAL **: 14:43:43.523:
gdk_gl_window_impl_x11_make_context_current: assertion
'GDK_IS_GL_CONTEXT_IMPL_X11 (glcontext)' failed
The program 'pcb-rnd' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadValue (integer parameter out of range for operation)'.
(Details: serial 222 error_code 2 request_code 150 minor_code 3)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the --sync command line
option to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error()
function.)
I still hope there is a solution.
Best regards
Freddy Fisker
On Thursday, 9 February 2023 12:39:16 CET, Stuart Henderson wrote:
On 2023-02-09, Freddy Fisker <f...@freddyfisker.dk> wrote:
Thanks for your interest.
I forgot to mention that the problem came after the last time I updated
OpenBSD 7.2 to current.
cad/pcb didn't get built in the last set of bulk builds due to a
dependency loop in multimedia/frei0r-plugins which has since been
fixed, please either wait for a new package snapshot and run
pkg_add -u, or build from ports, and retry.
If there's still a problem then, ports@ would be the best place for it.
