Hi list!

At the next build of MinGW encountered this error:
E:/msys/local/lib/libcloog-isl.a(libcloog_isl_la-domain.o):domain.c:(.text+0x1088):
undefined reference to `snprintf'
E:/msys/local/lib/libcloog-isl.a(libcloog_isl_la-domain.o):domain.c:(.text+0x1113):
undefined reference to `snprintf'
E:/msys/local/lib/libcloog-isl.a(libcloog_isl_la-domain.o):domain.c:(.text+0x24f0):
undefined reference to `snprintf'
E:/msys/local/lib/libcloog-isl.a(libcloog_isl_la-domain.o):domain.c:(.text+0x2549):
undefined reference to `snprintf'
E:\msys\local\i686-pc-mingw32\bin\ld.exe:
E:/msys/local/lib/libcloog-isl.a(libcloog_isl_la-domain.o): bad reloc
address 0x20 in section `.eh_frame'
E:\msys\local\i686-pc-mingw32\bin\ld.exe: final link failed: Invalid operation
collect2: ld returned 1 exit status
make[3]: *** [cc1.exe] Error 1

I suspect that it's caused by "bad reloc address 0x20 in section .eh_frame"
The error appears on all-stage2-gcc on link cc1.exe.
Full link command:
/building/build/gcc-4.6.1/./prev-gcc/xgcc
   -B/building/build/gcc-4.6.1/./prev-gcc/ \
   -B/usr/local/i686-pc-mingw32/bin/ \
   -L/building/build/gcc-4.6.1/i686-pc-mingw32/winsup/mingw \
   -L/building/build/gcc-4.6.1/i686-pc-mingw32/winsup/w32api/lib \
   -isystem /building/src/gcc-4.6.1/winsup/mingw/include \
   -isystem /building/src/gcc-4.6.1/winsup/w32api/include \
   -B/usr/local/i686-pc-mingw32/bin/ \
   -B/usr/local/i686-pc-mingw32/lib/ \
   -isystem /usr/local/i686-pc-mingw32/include \
   -isystem /usr/local/i686-pc-mingw32/sys-include \
   -g \
   -O2 \
   -D__USE_MINGW_ACCESS \
   -Wno-pedantic-ms-format \
   -gtoggle \
   -DIN_GCC \
   -W \
   -Wall \
   -Wwrite-strings \
   -Wcast-qual \
   -Wstrict-prototypes \
   -Wmissing-prototypes \
   -Wmissing-format-attribute \
   -pedantic \
   -Wno-long-long \
   -Wno-variadic-macros \
   -Wno-overlength-strings \
   -Wold-style-definition \
   -Wc++-compat \
   -DHAVE_CONFIG_H \
   -Wl,--stack,12582912 \
   \
   -o cc1.exe \
   \
   c-lang.o \
   c-family/stub-objc.o \
   attribs.o \
   c-errors.o \
   c-decl.o \
   c-typeck.o \
   c-convert.o \
   c-aux-info.o \
   c-objc-common.o \
   c-parser.o \
   tree-mudflap.o \
   c-family/c-common.o \
   c-family/c-cppbuiltin.o \
   c-family/c-dump.o \
   c-family/c-format.o \
   c-family/c-gimplify.o \
   c-family/c-lex.o \
   c-family/c-omp.o \
   c-family/c-opts.o \
   c-family/c-pch.o \
   c-family/c-ppoutput.o \
   c-family/c-pragma.o \
   c-family/c-pretty-print.o \
   c-family/c-semantics.o \
   c-family/c-ada-spec.o \
   i386-c.o msformat-c.o \
        cc1-checksum.o \
   main.o  \
   libbackend.a \
   ../libcpp/libcpp.a \
   ../libdecnumber/libdecnumber.a \
   ../libcpp/libcpp.a \
   /usr/local/lib/libiconv.a \
   -L/usr/local/lib \
   ../libiberty/libiberty.a \
   ../libdecnumber/libdecnumber.a \
   -L/e/mingw/lib \
   -lstdc++ \
   -L/usr/local/lib \
   -lcloog-isl \
   -lisl \
   -lppl_c \
   -lppl \
   -lgmpxx \
   -lmpc \
   -lmpfr \
   -lgmp \
   -L/e/mingw/lib \
   -lstdc++ \
   -L../zlib \
   -lz


binutils version: 2.22.51-20120110
configure with:
CFLAGS="-pipe -O3 -mtune=core2 -fomit-frame-pointer
-momit-leaf-frame-pointer -I/usr/local/include" \
LDFLAGS="-Wl,--large-address-aware -pipe -s -L/usr/local/lib" \
--target=i686-pc-mingw32 \
--prefix=/usr/local \
--disable-nls \
--with-libiconv-prefix=/usr/local \
--enable-static \
--disable-shared


I have never seen such an error, and I don't even know because of what
it could be ...
Please share your thoughts.

Thanks.

------------------------------------------------------------------------------
Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex
infrastructure or vast IT resources to deliver seamless, secure access to
virtual desktops. With this all-in-one solution, easily deploy virtual 
desktops for less than the cost of PCs and save 60% on VDI infrastructure 
costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox
_______________________________________________
Mingw-w64-public mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Reply via email to