On Sat, Jul 7, 2012 at 10:35 PM, Akemi Yagi <[log in to unmask]> wrote: > I filed a bug report for this issue with respect to RHEL-6 here: > > https://bugzilla.redhat.com/show_bug.cgi?id=641739 > > I did my best to explain what the real issue was but it was also > closed as NOTABUG. One outcome was that glibc-static.i686 was > eventually made available for x86_64. > >> I'm a bit confused about why it didn't show up in the Scientific Linux >> build setups, and would like to get a better handle on how those are >> done. > > I believe that SL developers try not to modify the source if the > 'problem' can be dealt with by manipulating the build > environment/setup. I'm sure grub is not the only one that needs such > endeavour. Perhaps not: it's just the sort of thing I'd like to know about build environments. >> Unfortunately, my patch had a bug. Using "BuildRequires: >> glibc-static.i686" does not, in fact, find the .i686 version of >> glibc-static, it expects a package named "glibc-static.i686" of an >> arbitrary architecture. > > You can add "BuildRequires: /usr/lib/libc.a" as noted in comment #6 of > the above bugzilla. > > Akemi I went with the parts about getting "glibc-static.i686" installed. the "libc.a" entry was in the middle of your notes, and a bit hard to see in the middle of a sentence rather than in a separate line. It's cool.