This is the mail archive of the
gcc-help@gcc.gnu.org
mailing list for the GCC project.
Re: Compilation errors building gcc on mipsel
- From: Harry Prevor <habs at sdf dot org>
- To: gcc-help at gcc dot gnu dot org
- Date: Thu, 13 Mar 2014 10:19:42 +0000
- Subject: Re: Compilation errors building gcc on mipsel
- Authentication-results: sourceware.org; auth=none
- References: <20140311235106 dot GB381 at SDF dot ORG> <53201699 dot 4050102 at wippies dot com> <20140312105402 dot GC381 at SDF dot ORG> <5320F616 dot 8090401 at gmail dot com>
On Wed, Mar 12, 2014 at 05:04:38PM -0700, David Daney wrote:
> You are running on a 64-bit kernel.
>
> You need to run "linux32":
>
> # uname -m
> mips64
> # linux32
> # uname -m
> mips
>
> Once you get uname -n reporting a 32-bit environment (i.e. "mips"
> instead of "mips64"), configure should do a better job.
I think that this is probably the core of the issue, but unfortunately these steps didn't seem to do the trick.
I deleted my build directory entirely and then created a new one. I ran "linux32", then switched to a bash shell.
Just to make sure, I checked "uname -m" before starting the ./configure (this time it was just "../gcc-4.8.2/configure --prefix=/usr/local --disable-nls --enable-languages=c,c++") and it returned just "mips" (as well as uname -a), so I thought I would be good. But unfortunately, after leaving it "make"ing overnight, the build still errored out with the same "ABI is incompatible with that of the selected emulation" errors. :-(
I even checked the config.guess script after the build failure, and even that returned just "mipsel-unknown-linux-gnu" this time.
Any idea what could be going wrong here?
--
Harry Prevor