I've got your bug report, have reproduced it and am looking into it. This is a
dup of another report that was marked fixed a while back, so this is somewhat
surprising.

This appears to be a dup of #427315. Not closing as a dup, yet.

Can you please check to see if there is any difference in behaviour between
0.9.6 and 0.8.19?

I took the Fc8 src.rpm for mock-0.8.19 and rebuilt it on rawhide. Then cleared
the cached build roots, and re-ran, but it still fails:

$ mock rebuild -r fedora-devel-x86_64 /home/berrange/xenner-0.22-1.fc8.src.rpm 
INFO: mock.py version 0.8.19 starting...
State Changed: init plugins
State Changed: start
INFO: Start(/home/berrange/xenner-0.22-1.fc8.src.rpm) 
Config(fedora-development-x86_64)
State Changed: lock buildroot
State Changed: clean
State Changed: init
State Changed: lock buildroot
INFO: enabled root cache
INFO: enabled yum cache
State Changed: cleaning yum metadata
State Changed: running yum
State Changed: creating cache
State Changed: setup
ERROR: Exception(/home/berrange/xenner-0.22-1.fc8.src.rpm)
Config(fedora-development-x86_64) 2 minutes 14 seconds
INFO: Results and/or logs in: /var/lib/mock//fedora-development-x86_64/result
ERROR: Bad build req: No Package Found for /usr/include/gnu/stubs-32.h. Exiting.

Further data point. If i used  mock-0.8.19  on an F8 host, then it works fine.
So it seems to be something odd in the F9 stack that's breaking mock.

Ok, this appears to be a config file problem

Current mock sets up a config with

exclude=[!g]*.i*86 g[!l]*.i?86  gl[!i]*.i?86 gli[!b]*.i?86 glib[!c]*.i?86 


My F8 host is still using a config with 

exclude=[ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefhijklmnopqrstuvwxyz]*.i*86
g[abcdefghijkmnopqrstuvwxyz]*.i?86 glib2.i?86 glib.i?86



If I change my F8 host to use the new style exclude config, it also fails. If I
change my F9 host to use the old style exclude config, it works. 

So the defualt config file for latest mock seems to have bogus excludes.

The exclude line was changed due to another, different problem. I've been
working on IRC and we came to largely the same conclusion. The [!x] syntax in
the exclude line seems to be broken. I'll end up changing the default configs
back to the 'ugly' way.

The root problem is really yum's need to encode this magic in a single exclude
line - it makes it very hard to exclude just the right amount. It would relaly
be better as a exclude/include pair - cf imagine trying to write apache ACLs
using only the 'deny' clause and no 'allow' clause.

So perhaps its worth asking for a feature enhancement against yum to support
something like:

 order='exclude,include'
 exclude='*.i?86"
 include='glibc-*.i?86'

I've checked in a fix to the exclude= line to upstream git.

I am waiting on code review for some other changes that went into 0.9 recently
before I spin new packages for rawhide. This should hit rawhide within a week.
In the meantime, if you want the official configs, you can obtain them from git.

Thanks for reporting this bug!

There's this plugin - we just need to have a way of enabling plugins for mock
easily.

http://skvidal.fedorapeople.org/x86_64_build_exclude.py

*** Bug 440368 has been marked as a duplicate of this bug. ***

Changing version to '9' as part of upcoming Fedora 9 GA.
More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

I'm pretty sure this is fixed with the way yum now works with multilib.

This bug still exists on F14 beta using F14 x86_64 and rawhide (F15) x86_64 mock targets:
texi2html -monolithic -number tcc-doc.texi
In file included from /usr/include/features.h:385:0,
                 from /usr/include/stdlib.h:25,
                 from tcc.h:34,
                 from libtcc.c:21,
                 from tcc.c:24:
/usr/include/gnu/stubs.h:7:27: fatal error: gnu/stubs-32.h: No such file or directory
compilation terminated.