On 11/01/13 05:10, Mike Frysinger wrote: > On Wednesday 09 January 2013 06:39:37 justin wrote: >> On 09/01/13 12:29, justin wrote: >>> On 09/01/13 10:26, Diego Elio Pettenò wrote: >>>> On 09/01/2013 09:40, justin wrote: >>>>> Also the internals of the build are affected (probably through the >>>>> difference in configure). This leads to disrespected LDFLAGS and broken >>>>> tclConfig.sh. So this simple change has deep consequences. >>>> >>>> This looks like the _version_ of autoconf used is different. Is the >>>> output from the same exact system? >>> >>> Okay, did some more debugging and it seems to be not the new singly >>> inheriting eclass. >>> >>> Repeating the sequential emerge on different FS I get a completely mixed >>> result. Sometimes both compile are good, sometimes only one and sometime >>> none. >>> Could this be a problem with eautoreconf or is this autotools specifc >>> problem? >> >> I assume it is a portage problem, because the log says autoconf is run >> but configure.in didn't change. > > this sounds like bug 417355. the autom4te.cache dir gets busted (somehow). > when autotools runs, it looks at the cache dir, sees that things are up to > date, and then doesn't regen any files. > -mike >
Yeah, it was because of the double patching of configure and configure.in. Cleaning the patch made it work. Interestingly in the beginning I really could reproduce a correlation between the inherit order and this breakage. Bad that was false. Thanks justin
signature.asc
Description: OpenPGP digital signature
