libpthreadbroken, fixed

If you are running bleeding-edge DragonFly, libpthread was broken for a short period.  If you built anything in the last … 12 hours?  You may want to rebuild it.  If that doesn’t describe you, it’s a nonevent.

It’s funny that I’m reporting a short-term break in bleeding-edge operating system code as any sort of surprise.  It shows something about how stable DragonFly-master is most of the time.

One Reply to “libpthreadbroken, fixed”

  1. To be specific, if you rebuilt libc on an x86-64 system only, during the 12-hour or so period, you will need to rebuild it. You will need to rebuild statically linked threaded (only) programs as well.

Comments are closed.

To respond on your own website, enter the URL of your response which should contain a link to this post's permalink URL. Your response will then appear (possibly after moderation) on this page. Want to update or remove your response? Update or delete your post and re-enter your post's URL again. (Find out more about Webmentions.)

Mentions

  • Venkatesh Srinivas