| 1 |
> From: Rigo |
| 2 |
> Sent: Wednesday, August 07, 2002 6:00 AM |
| 3 |
> |
| 4 |
> I just read this on the forums...Anybody any comments ? |
| 5 |
> |
| 6 |
> Regards, Rigo |
| 7 |
> <SNIP> |
| 8 |
> I |
| 9 |
> installed a cvs snap of gcc-3.1.1 (about to be released - yeah |
| 10 |
> right!) |
| 11 |
> |
| 12 |
> Build of glibc-2.2.5 will bomb unless the following patch is |
| 13 |
> applied. I stole this from the stable glibc-2.2.6 branch of |
| 14 |
> cvs. And for the record, this is slightly different to the |
| 15 |
> patch the gentoo guys are using. Their's is wrong. |
| 16 |
|
| 17 |
|
| 18 |
I use the "-march=athlon-tbird" flag and never noticed this or any other |
| 19 |
problem. |
| 20 |
I had gcc-3.1.1 installed and recompiled glibc-2.2.5 without any major |
| 21 |
issue. I now have gcc-3.2 installed with glibc-2.2.5 and still have no |
| 22 |
problem. When I upgrade gcc I normally like to recompile all libraries |
| 23 |
and most applications. |
| 24 |
|
| 25 |
By the looks of this, this issue may only show when compiling with the |
| 26 |
"i686" flag. |
| 27 |
|
| 28 |
|
| 29 |
Cheers, |
| 30 |
|
| 31 |
Michael |
| 32 |
michael@××××××.com |
Archives