This Time Self-Hosted
dark mode light mode Search

New autoconf, new problems

So a new release of autoconf is in the tree, it’s version 2.62. Guess what? It’s far from glitches-free. Although I suppose the biggest problem is from programs that bend the rules autoconf gives you.

While the warnings it spews up during Amarok build are, well, just a warning, which will probably be fixed before a version of autoconf making those problems fatal, there are subtle bugs that might appear, like –bug #217154 which made PAM fail to build. I suppose before autoconf 2.62 can go stable, Linux-PAM 1.0.0-r1 has to, too. I could just start the stabling process now by making the last 0.99 version using PAM the stable candidate, but I admit I wanted some more time than that.

I expect more problems to come out in the next days, we’ll see about that though. In the mean time I’m here to warn you that there might be problems related to autoconf, so don’t panic if something does not build out of the box, especially if it’s an old version that is just being rebuilt.

Comments 2
  1. Hey, there! Uh… yeah… markey told me to get a hold of you, because, frankly, whoever has been doing the amarok ebuilds sucks. I’m a sabayon (gentoo-derivitave) user, and I like having everything nice and new. Could you come back? 😀

  2. If you have any problem with Amarok’s ebuild – or any other ebuild for what matters – the right place to report that is the Gentoo Bugzilla.On the other hand, frankly, I don’t give a shit about Sabayon, as I suppose _they_ are getting the ebuild wrong. I’m still maintaining it and I haven’t received a single complain beside Amazon problems in quite a while.

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.