Summary: | attempt to compile new version of glibc dies with "bad register name" | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Kendric Beachey <kendric.beachey> |
Component: | [OLD] Core system | Assignee: | AMD64 Project <amd64> |
Status: | RESOLVED WORKSFORME | ||
Severity: | blocker | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Kendric Beachey
2005-09-15 20:04:13 UTC
try again with -r2 no response, so i assume -r2 did the trick. if not, please reopen How odd--it appears my response to the "-r2" suggestion was not recorded. I sent it via email rather than the web interface. Here it is again: Sorry to be dense, but...what? :-) Is that a command line option, or a new ebuild revision number, or the square of the negative value of the radius, or...? with -r2 Mike meant 2.3.5-r2, the latest stable glibc (In reply to comment #4) > with -r2 Mike meant 2.3.5-r2, the latest stable glibc Thanks for the clarification. :-) It appears that after doing `emerge sync` and thereby picking up 2.3.5-r2, the process has completed successfully. Hooray! |