Martin> You can't do that (if installing 2.12.1 means to downgrade from Martin> 2.13). gcc configuration analyses features of binutils at configure Martin> time, and relies on those features to be present at run-time. Martin> Are you sure that gcc picks up the binutils you had installed when you Martin> configured gcc? In particular, what happens if you do Martin> gcc --print-prog-name=as Martin> gcc --print-prog-name=ld Martin> Are those the once that you had in PATH when configuring? Yes. The way I install stuff on this particular machine is to build each package (gcc, binutils, etc.) in a completely separate directory, then make symbolic links to that directory from a common directory in which everything is actually executed. So gcc always thinks the linker is in a single place, and "installing binutils 2.12.1" means removing all the symlinks to the version of binutils that was previously in place and making new symlinks to the binutils 2.12.1 binaries. -- Andrew Koenig, ark@research.att.com, http://www.research.att.com/info/ark
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4