[SOLVED] glew patch for unknown error wxWidgets>=3.1.5

Andy Alt · 09-03-2022, 09:24 AM

Someone reported this problem

Quote:

Versions of wxWidgets 3.1.5 and greater using glew throw a runtime glew error : unknown error and fail to display openGL

The ticket is at https://github.com/wxWidgets/wxWidgets/issues/22710

It looks like on the ticket they've agreed it's a packaging issue.

Quote:

We can't force Arch package maintainers to use it if it's necessary however, so there really isn't much we can do here. Please ask the maintainers to contact us (preferably on wx-dev mailing list) if they have any questions about this, but I don't see this as a wx bug at all, so I'm closing it.

I don't know enough to say it's a packaging issue, but the reported problem may be affecting one of the projects I contribute to, so I wanted to mention it here to get other opinions.

business_kid · 09-04-2022, 04:00 AM

From personal experience, I can say that wxwidgets can be a bitch to compile. I tried twice, for two different programs, and succeeded once.

It sounds like you should be onto wx-dev, and not us. Does it compile on Arch from a tarball? Also, 'unknown error' is a strange one. Linux is usually very diagnostic, giving diagnostic errors, and passing them up the food chain. It sounds like at some stage of the compile a child process returned no error.

Andy Alt · 09-04-2022, 10:00 PM

The issue *may* be affecting a binary in a project that I'm just a minor contributor to. It links to glew and wx.

Quote:

Using wxWidgets version [3.2.0.1]
Error [main]: glewInit failed: Unknown error
Segmentation fault (core dumped)