[Bug ld/22302] Unable to link glibc-2.24 for mips64-linux-gnuabi64 (assertion fail elfxx-mips.c:9011)

[broly at mac dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=22302

broly at mac dot com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |broly at mac dot com

--- Comment #2 from broly at mac dot com ---
(In reply to broly from comment #1)
> hi,
> 
> sorry to bump this, but i’ve been having the exact same problem when trying
> to make a multilib glibc using a mips64el-none-linux-gnu binutils/gcc.
> 
> specifically, if i am trying to build the o32 glibc using
> mips64el-none-linux-gnu-gcc for target mipsel-none-linux-gnu, it will fail
> exactly as-is reported here.
> 
> the n32 and o64 libraries have no issue.
> 
> i have noticed this issue for some time and the workaround (for me) was to
> simply make the target mips64el-none-linux-gnu, but set CC to
> "mips64el-none-linux-gnu-gcc -mabi=32”, which works without issue.
> 
> however i imagine this minor niggle does cause compatibility issues. 
> for example, if i use this package manager ‘entware’, where programs are
> compiled against (another, likely non-multilib) glibc library for the same
> target (mipsel-none-linux-gnu), the manager downloads glibc again likely
> because the programs on this package manager are not compatible with my
> glibc due to the target mismatch.
> 
> the same issue (so this is verified to affect linux platforms as well) has
> been reported for debian, but was closed due to lack of resources:
> 
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905436
> <https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905436>
> 
> i am hoping the developers here can shed some insight as to why setting the
> target to ‘mips64el-none-linux-gnu’ is successful, but
> ‘mipsel-none-linux-gnu’ is not, even when the remaining arguments input to
> ./configure are unchanged (CC is ‘mips64el-none-linux-gnu-gcc -mabi=32’ in
> both situations)
> 
> bless,
> g

the above post is by me, by the way. so this bug should be changed to
'confirm'. it is definitely an issue for mips multilib targets.

-- 
You are receiving this mail because:
You are on the CC list for the bug.