[EMAIL PROTECTED] wrote: >Hello, > >On Tue, Jun 28, 2005 at 10:25:36AM -0700, Duncan wrote: > > >>Exactly, and I'm an -Os person myself. However, if something goes >>haywire, I do at times try recompiling with "-march=k8 -O2 -pipe" (or even >>-O1), just to be sure. >> >>The last time I had a similar problem, it was an issue with 32-bit only, >>and due to the glibc I was using (the masked version for use with an also >>masked gcc4). The 64-bit glibc was working fine, but further updates to >>gcc or sandbox were failing, when they tried to do the config for their >>32-bit compile sections. The problem was solved by emerge --packageonly >>a previous (and unmasked) glibc version. Since I use FEATURES=buildpkg, >>that was easily done. Note that emerging a binpkg doesn't require a >>working gcc... >> >can you please post your umask? >i had the same problem because my umask was too strict >
Who, Duncan or me? Mine is 0022, both my own and root's. -- [email protected] mailing list
