Contributed by jose on from the careful-upgrade dept.
Bye-bye libc_r. libc_r and libnpthread go away. libpthread takes their place. The -pthread option to gcc uses libpthread. ppc portion of patch from drahn@ (thanks). gcc portions of patch OK espie@. Ports testing (no bad effects!) by naddy@ best build sequence is: build gcc, build system, build ports remove /usr/lib/lib{c_r,npthread}.*. Note, once libc_r and libnpthread is removed threaded ports will stop working until they have been re-built using the libpthread and the updated gcc. That's why the above build sequence is recommended.So, the next time you upgrade keep this in mind. This should fix a few applications, by the way, which use threading extensively.
(Comments are closed)
By Anonymous Coward () on
Comments
By Eduardo Augusto Alvarenga () eduardo@thrx.dyndns.org on mailto:eduardo@thrx.dyndns.org
Is there anything like 'make key=libpthread show' in ports?
Comments
By Anonymous Coward () on
By Anonymous Coward () on
If you can't figure it out, you should either learn how to do it yourself, or not run -current.
Comments
By James () quel@gnu.org on http://quel.linux-dude.com
quel
Comments
By Anonymous Coward () on
By bbcrack () on
By djm () on
-current isn't like "Debian unstable" or any of those other perpetually-beta Linux distributions, it is intended for developers. You are usually building shit which people committed to CVS days or hours ago - you are totally on your own.
If this doesn't look like your cup of tea, then use the snapshot releases - these are for people why want to try the new stuff, but not have to worry so much.
Comments
By Anonymous Coward () on
So yeah, use -current only if you know what you are doing. Everybody else has a few months to learn, and asking questions is a very valid way of doing that.
By Anonymous Coward () on
see the difference between a time wasting stupid
question and a reasonable doubt. Further more,
this is not misc@, and if you don't know what I
mean by that, then may be you shouldn't be reading
this site.
By Anonymous Coward () on
I agree that people who don't understand what they're doing should stick to -stable. But that doesn't mean they can't be interested in what's going on in current, since that's what'll be in the next release in 6 months.
People running -current and doing development themselves will understand perfectly what's going on, but others won't. So I think the OP just wanted to know what may be the practical consequence of this change in the next release.
By Marc Espie () espie@openbsd.org on `
Linker might get less confused, bugs might disappear.
A few apps also suddenly recognize libpthread because
of autoconf hackery, not sure this is a good thing.
In general, things get lighter. You just load libc and libpthread instead of libc and libc_r.
Smaller footprint, less confusion, things better in general.
Hard to tell you more, haven't looked precisely... it's impossible to focus on 4GB of source code, which is about what ports/ is these days...
but, yeah, the switch to libpthread is definitely a good thing.
If you follow -current, just test.
If you don't, hope enough people test -current.
But anyways, even if you're a lazy bum sitting on his ass, next release of OpenBSD is going to have better thread support, and that includes MORE running applications.
Comments
By Anonymous Coward () on
Comments
By Anonymous Coward () on
The answer to your question is "yes".
By AnonymousCanuck () on
Will it be much work?
Do I have to continously recompile my system?
Will this just be a waste of time?
Comments
By Anonymous Coward () on
By AC () on