bug-binutils
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Bug binutils/22966] New: MIPS -mplt -msym32 is resulting in assertion l


From: raajeshdasari at gmail dot com
Subject: [Bug binutils/22966] New: MIPS -mplt -msym32 is resulting in assertion ld.orig: BFD 2.29.1 assertion fail binutils-2.29.1 /bfd/elfxx-mips.c:11234
Date: Wed, 14 Mar 2018 12:00:19 +0000

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

            Bug ID: 22966
           Summary: MIPS -mplt -msym32 is resulting in assertion ld.orig:
                    BFD 2.29.1 assertion fail binutils-2.29.1
                    /bfd/elfxx-mips.c:11234
           Product: binutils
           Version: 2.29
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: binutils
          Assignee: unassigned at sourceware dot org
          Reporter: raajeshdasari at gmail dot com
  Target Milestone: ---

Compiling a simple helloworld.c with -mplt & -msys32 is resulting in assertion
error. Any pointers on how to get it work? 


./mips64-linux-gnu-toolchain/bin/mips64-linux-gnu-gcc
--sysroot=./mips64-linux-gnu-sysroot helloworld.c -mplt -msym32 

mips64-linux-gnu-toolchain/mips64-linux-gnu/bin/ld.orig: BFD 2.29.1 assertion
fail binutils-2.29.1 /bfd/elfxx-mips.c:11234
collect2.orig: error: ld returned 1 exit status


GCC Configured with: 
/build/distro/work/shared/gcc-4.9.4/configure --build=x86_64-build-linux-gnu
--target=mips64-linux-gnu --prefix=/build/distro/work/mips64/toolchain
--disable-nls --disable-bootstrap
--with-sysroot=/build/distro/work/mips64/toolchain/glibc/mips64-linux-gnu
--enable-languages=c,c++ --with-gmp=/usr --with-mpfr=/usr --with-mpc=/usr
--enable-shared --disable-static --with-arch=mips64 --with-abi=64
--with-float=soft --disable-multilib --with-mips-plt --disable-sim
--enable-symvers=gnu --enable-__cxa_atexit --enable-64-bit-bfb
Thread model: posix
gcc version 4.9.4

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


reply via email to

[Prev in Thread] Current Thread [Next in Thread]