12.3.2014 12:54, Harry Prevor kirjoitti:
Alas, there was unfortunately a previous chapter to my story. Before
posting this message, I had tried to run "../gcc-4.8.2/configure
--prefix=/usr/local --disable-nls --enable-languages=c,c++" instead,
but I was just getting a very similar error[1]. I asked in the IRC
channel on Freenode, and someone there suggested that I add
"mips-unknown-linux-gnu" to the configure line. He said it may have
had to do with my "uname -a" being "broken"; it currently outputs
"Linux marielle 3.5.3-gnu #1 PREEMPT Tue Aug 28 10:49:41 UTC 2012
mips64 GNU/Linux". Not sure if there's something wrong with that.
Ok, you can check what the configury system would tell your system
being via running :
./config.guess
in the main gcc-4.8.2 source directory.
Oddly enough, if I run that script, I do get "mips64el-unknown-linux-gnu", so very confused as to what the issue is here.
You can spy how the current GCC was configured via 'gcc -v'. I could
guess a 'mipsel-linux-gnu' or
'mipsel-linux-gnueabi' being used in its configure command. Or things to
define the default output
and CPU to be a 32-bit one instead of the expected 64-bit....
Just for curiosity I checked what the 'gcc-4.3_4.3.5-4_mipsel.deb'
package from 2012 (like your
system) was and saw it being configured using all the three system names
being the same :
--build=mipsel-linux-gnu --host=mipsel-linux-gnu
--target=mipsel-linux-gnu
(using 'strings gcc-4.3 | less' and searching for 'configure') You
should check also the other options
used with the existing native GCC whether they could be needed...
