<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Jun 6, 2013, at 6:39 AM, bvl wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; ">My knowledge of perl in zilch<br>and I am not confident enough with sed <br>to reverse the script shown in section 10.8<br><br>so I would be grateful if someone more expert could provide a sed ( or perl<span class="Apple-converted-space"> </span><br>script ) that readjusts the linker to use the one in the toolchain.</span></blockquote></div><br><div>All we do is dump the specs, edit it, and pipe it out to where the target gcc's specs location is.</div><div>All you need to do is remove that file.</div><div><br></div><div>$(dirname $(/tools/bin/gcc --print-libgcc-file-name))/specs should output the specs file location.</div><div><br></div><div>rm $(dirname $(/tools/bin/gcc --print-libgcc-file-name))/specs would remove it.</div><div><br></div><div>Or you can go into /tools/lib/gcc/*/* and rm specs.</div><div><br></div><div>You may want to remove the old gcc binaries and install from 4.8.0:</div><div><br></div><div>GCC has no uninstall target so you can remove in /usr/bin *gcc* *g++* /usr/lib/gcc</div><div><br></div><div>Just do a: find /usr -name 4.8.0 and see what is around.</div><div><br></div><div>Then you can verify you are using the proper gcc from /tools/bin when you enter chroot from this point:</div><div>Section 8.5 Entering the chroot (if chrooting)</div><div>Or after booting if using the booting method. 7.15</div><div><br></div><div>If the sanity check fails afterwards, then the specs file may be still in /tools</div><div><br></div><div>Sincerely,</div><div><br></div><div>William Harrington</div></body></html>