bug-binutils
[Top][All Lists]
Advanced

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

[Bug binutils/26107] New: Compilation failure in pdp11.c


From: markus.boeck02 at gmail dot com
Subject: [Bug binutils/26107] New: Compilation failure in pdp11.c
Date: Wed, 10 Jun 2020 17:54:38 +0000

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

            Bug ID: 26107
           Summary: Compilation failure in pdp11.c
           Product: binutils
           Version: 2.35 (HEAD)
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: binutils
          Assignee: unassigned at sourceware dot org
          Reporter: markus.boeck02 at gmail dot com
  Target Milestone: ---

When trying to compile gdb using the --enable-targets=all option I have
encountered following compilation failure inside of bfd:

/bin/bash ./libtool  --tag=CC   --mode=compile
/mnt/c/GCC-Build/NewestLinux/bin/x86_64-w64-mingw32-gcc-9 -DHAVE_CONFIG_H -I.
-I../../bfd  -DBINDIR='"/mnt/c/GDB/bin"' -DLIBDIR='"/mnt/c/GDB/lib"' -I.
-I../../bfd -I../../bfd/../include  -DHAVE_all_vecs -I./../intl   -W -Wall
-Wstrict-prototypes -Wmissing-prototypes -Wshadow -Wstack-usage=262144
-Wno-format -Werror -I../../bfd/../zlib -static -I/mnt/c/Python27/include -g
-O3 -march=native -fdebug-prefix-map=/mnt/c=C:
-I/mnt/c/GDB-Build/libexpat/expat/install/include -D__USE_MINGW_ACCESS -MT
vax1knetbsd.lo -MD -MP -MF .deps/vax1knetbsd.Tpo -c -o vax1knetbsd.lo
../../bfd/vax1knetbsd.c
../../bfd/pdp11.c:339:13: error: implicit declaration of function 'index'
[-Werror=implicit-function-declaration]
  339 |     return (index(name, ':') != NULL);
      |             ^~~~~
../../bfd/pdp11.c:339:13: error: incompatible implicit declaration of built-in
function 'index' [-Werror]

Compiler used is current trunk version of GCC 9 using the x86_64-w64-mingw32
target. Tested on current trunk branch of binutils-gdb at revision
84df1f9dcb8ef24cc38db4cc0939e99752c4e42b.

-- 
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]