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.

Your post must include a link to this post.

How does this work?
Write a response on your own website and include a link to this post. Then submit your response’s URL here. Your response may appear here after moderation. To update or remove it, edit or delete your original post and submit the same URL again. Learn more about Webmentions.