I'm starting to wonder if I'm going out of my mind, but hopefully someone here can provide a plausible explanation ;)
On my current system I built libbonobo-2.32.1 without any issues. Now, I'm checking all the details to upgrade BLFS. But, the configure script is now not executable (mode 644) when I untar it. My logs show that the configure and build ran ok, and git shows that when I built it from my script I did a straight ./configure without any chmod or autofoo, and the last change was the version upgrade on 30th September (I actually built it on 7th December). Looking at PLD, my md5sum matches theirs. I also see that they throw a whole cartload of libtool and autofoo imprecations into their build before they run configure. But, I think thay tend to do that anyway - and in any case it doesn't seem to make the file executable. So, how is it that the configure script was executable when I untarred it on 7th December, but isn't when I untar it now ? I've tested with an older kernel (3.1.1, which was what I used for the build - I'm on 3.2.0-rc6 now), and then on an older system, but the configure script is stubbornly not executable when I untar it. Other tarballs give me an executable configure script, even the 2.32.0 version of this package. I can add a 'chmod +x configure' but I'd prefer to understand what has changed. TIA ĸen -- das eine Mal als Tragödie, das andere Mal als Farce -- http://linuxfromscratch.org/mailman/listinfo/lfs-chat FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
