-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 01.10.2012 14:13, YoYo Siska wrote: > On Mon, Oct 01, 2012 at 12:50:40PM +0200, meino.cra...@gmx.de > wrote: >> hi, >> >> Something broke my crossdev installation... >> >> I installed crossdev and did a >> >> crossdev --target armv7a-unknown-linux-gnueabi >> >> which produces a useable cross development toolchain. >> >> A few days ago there was an update related to thsi crossdev >> toolchain (dont remember exactly), which also installs fine. >> >> But now, calling >> >> armv7a-unknown-linux-gnueabi-gcc >> >> results in >> >> gcc-config: error: could not run/locate >> 'armv7a-unknown-linux-gnueabi-gcc' [1] 25787 exit 1 >> armv7a-unknown-linux-gnueabi-gcc >> >> . >> >> Calling >> >> armv7a-unknown-linux-gnueabi-gcc-4.7.2 >> >> gives the exspected error message "no input files". >> >> The output of >> >> gcc-config -l >> >> is >> >> [1] armv7a-unknown-linux-gnueabi-4.7.2 >> >> [2] x86_64-pc-linux-gnu-4.4.7 [3] x86_64-pc-linux-gnu-4.5.4 * >> > > seems that the armv7a compiler isn't 'active' in the gcc-config > output (no asterix after the [1] option), did you try to > 'reactivate' it with gcc-config, ie # gcc-config 1 ? > > My output here: julka ~ # gcc-config -l [1] > armv4tl-softfloat-linux-gnueabi-4.4.6 * [2] > armv4tl-softfloat-linux-gnueabi-4.5.3 > > [3] x86_64-pc-linux-gnu-4.4.4 [4] x86_64-pc-linux-gnu-4.5.3 * > > (Though it is possible the asterix won't show up if there is only > one option, but reactivating it should do anything bad...) > > >> . Before i screw up my native toolchain I better ask for help, >> how I can reactivate my crossdev toolchain, so that it is >> available via >> >> armv7a-unknown-linux-gnueabi-gcc >> >> . >> >> How can I acchieve this? >> >> Thank you very much in advance for any help! >> >> Best regards, mcc > > > > yoyo >
I can remember that I had to "reactivate" mine a while ago (maybe two weeks). Afterwards it worked again as expected. You should check afterwards, if your "system-compiler" is still the right one (and maybe reactivate it, too - I just did it without checking first). Now I have two asterisks marking gcc-versions (in different colors, if I recall correctly). WKR Hinnerk -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iQEcBAEBAgAGBQJQaYxKAAoJEJwwOFaNFkYcBGEH/A2VPYStKya4aYony/qqBl1E MAD+VCBmqE1QBOvNMDMY5bvmS79HvS2VlQfM0P8XMGGzBRFN2c0fQQFRZ5xLTd5K e+CfUoAIRmielEic2FK7dsQMXjuRluCFzyuX5kuQGyIzGSxRXHdNXSQfpoTIei+F C6AU5riB5xWt/KusB6tnTxWA+RQdQMpNSRkZtqPNOESNWQtKx6cOEwZDlbRm4jcM uq/t2+yPxiZTVzsbn/xWzI3UQvNdzqqPejP2cN6woXsBfewz1MqrTdlLsns/CPa2 yQSCzbr/LwKKT/LUEbiHRJQcF8p7pd+lvo0MlZiLY1td3mgeyk5TDfGxqkQFXfY= =0b2d -----END PGP SIGNATURE-----
