Peter Humphrey <[EMAIL PROTECTED]> posted [EMAIL PROTECTED], excerpted below, on Sat, 23 Sep 2006 22:30:36 +0000:
> And I've found that module-init-tools won't compile with -combine either. > It complains about too many modules being passed. I did the same as you > and removed -combine while merging module-init-tools. Yeah. I've not done a full emerge --emptytree world with -combine in my CFLAGS, so while I know it doesn't kill a majority of packages, it apparently does kill a few. Still, for the additional optimization it enables, I consider it worth it on the others. > I did have another package fail to compile during the first emerge -e > system, but I don't remember the details. On repeating emerge -e world the > problem didn't recur (after emerge --resume --skipfirst to allow the first > invocation to finish), so I stopped thinking about it. The latest ~arch portage fixed a few circular dependency and other dependency resolution issues. It wasn't uncommon to have a few packages fail on emerge --emptytree, the first go round, due to these issues. The fixes now in portage are said to fix the most common such issues, but may not fix them all. What that all means here is that a few instances of having to invoke --skipfirst isn't unexpected, and likely weren't due to anything in the new CFLAGS or whatever. Hopefully, as a portage with the new changes eventually moves into stable, there will be fewer of those --skipfirsts necessary. -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman -- [email protected] mailing list
