bug-binutils
[Top][All Lists]
Advanced

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

[Bug binutils/29218] New: libiberty cannot find __imp___acrt_iob_func fo


From: euloanty at live dot com
Subject: [Bug binutils/29218] New: libiberty cannot find __imp___acrt_iob_func for x86_64-w64-mingw32 cross toolchain for canadian compilation
Date: Wed, 01 Jun 2022 17:10:17 +0000

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

            Bug ID: 29218
           Summary: libiberty cannot find __imp___acrt_iob_func for
                    x86_64-w64-mingw32 cross toolchain for canadian
                    compilation
           Product: binutils
           Version: unspecified
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: binutils
          Assignee: unassigned at sourceware dot org
          Reporter: euloanty at live dot com
  Target Milestone: ---

/usr/local/lib/gcc/x86_64-pc-linux-gnu/13.0.0/../../../../x86_64-pc-linux-gnu/bin/ld:
../libiberty/libiberty.a(xmalloc.o): in function `fprintf':
/home/cqwrteur/toolchains/native/x86_64-w64-mingw32/x86_64-w64-mingw32/include/stdio.h:361:
undefined reference to `__mingw_vfprintf'
/usr/local/lib/gcc/x86_64-pc-linux-gnu/13.0.0/../../../../x86_64-pc-linux-gnu/bin/ld:
../libiberty/libiberty.a(xmalloc.o): in function `xmalloc_failed':
/home/cqwrteur/toolchains_build/build/x86_64-w64-mingw32/i586-msdosdjgpp/binutils-gdb/libiberty/../../../../../binutils-gdb/libiberty/xmalloc.c:134:
undefined reference to `__imp___acrt_iob_func'
collect2: error: ld returned 1 exit status
make[3]: *** [Makefile:2488: doc/chew.stamp] Error 1
make[3]: Leaving directory
'/home/cqwrteur/toolchains_build/build/x86_64-w64-mingw32/i586-msdosdjgpp/binutils-gdb/bfd'
make[2]: *** [Makefile:1939: info-recursive] Error 1
make[2]: Leaving directory
'/home/cqwrteur/toolchains_build/build/x86_64-w64-mingw32/i586-msdosdjgpp/binutils-gdb/bfd'
make[1]: *** [Makefile:3071: all-bfd] Error 2
make[1]: *** Waiting for unfinished jobs....
yes

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