From: Ralf Corsepius <ralf.corsepius@rtems.org>
To: Joel Sherrill <joel.sherrill@OARcorp.com>
Cc: "gdb@sourceware.org" <gdb@sourceware.org>
Subject: [gdb-7.5.91] mips sim fails to build on mingw32
Date: Fri, 15 Mar 2013 12:52:00 -0000 [thread overview]
Message-ID: <514318D8.8050309@rtems.org> (raw)
In-Reply-To: <5140894E.6000308@oarcorp.com>
Hi,
The mips sim fails to build on mingw:
...
x86_64-w64-mingw32-gcc -DHAVE_CONFIG_H -DPROFILE=1 -DWITH_PROFILE=-1
-DWITH_ALIGNMENT=NONSTRICT_ALIGNMENT -DWITH_TARGET_WORD_BITSIZE=32
-DWITH_TARGET_WORD_MSB=31 -DWITH_DEFAULT_TARGET_BYTE_ORDER=BIG_ENDIAN
-DWITH_FLOATING_POINT=HARD_FLOATING_POINT
-DWITH_TARGET_FLOATING_POINT_BITSIZE=32 -DWITH_HW=0
-DWITH_HOST_BYTE_ORDER=0 -DDEFAULT_INLINE=0 -DWITH_RESERVED_BITS=1
-DWITH_SMP=0 -Wall -Wdeclaration-after-statement -Wpointer-arith
-Wformat-nonliteral -Wno-pointer-sign -Wno-unused -Wunused-value
-Wunused-function -Wno-switch -Wno-char-subscripts -Wmissing-prototypes
-Wno-format -DMIPS_MACH_DEFAULT=bfd_mach_mips8000 -I.
-I../../../gdb-7.5.91/sim/mips -I../common
-I../../../gdb-7.5.91/sim/mips/../common -I../../include
-I../../../gdb-7.5.91/sim/mips/../..//include -I../../bfd
-I../../../gdb-7.5.91/sim/mips/../..//bfd -I../../opcodes
-I../../../gdb-7.5.91/sim/mips/../..//opcodes -O2 -g -pipe -Wall
-Wp,-D_FORTIFY_SOURCE=2 -fexceptions --param=ssp-buffer-size=4
-mms-bitfields -D__USE_MINGW_ACCESS -c -o interp.o -MT interp.o -MMD -MP
-MF .deps/interp.Tpo ../../../gdb-7.5.91/sim/mips/interp.c
../../../gdb-7.5.91/sim/mips/../common/dv-sockser.c:44:24: fatal error:
netinet/in.h: No such file or directory
ATM, I assume this patch to be the cause (sim/mips):
2012-09-03 Joel Sherrill <joel.sherrill@oarcorp.com>
* configure.ac: Always link against dv-sockser.o.
* configure: Regenerate.
From what I can gather from comparing sim/mips/configure.ac to other
sim/*/configure.ac (e.g. bfin/configure.ac),
dv-sockser.o needs to be suppressed for mingw32-* targets?
Ralf
next prev parent reply other threads:[~2013-03-15 12:52 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-12 23:17 GDB 7.5.91 available for testing Joel Brobecker
2013-03-13 14:42 ` sim/erc32/Makefile.in patch - was " Joel Sherrill
2013-03-13 18:18 ` Joel Brobecker
2013-03-14 21:12 ` Mike Frysinger
[not found] ` <5140894E.6000308@oarcorp.com>
2013-03-15 12:52 ` Ralf Corsepius [this message]
2013-03-15 18:13 ` [gdb-7.5.91] mips sim fails to build on mingw32 Mike Frysinger
2013-03-15 18:32 ` Ralf Corsepius
2013-03-15 18:38 Joel Sherrill
[not found] ` <5143F627.3030905@rtems.org>
2013-03-16 6:56 ` Ralf Corsepius
2013-03-16 15:08 ` Joel Sherrill
2013-03-16 18:11 ` Joel Brobecker
2013-03-16 18:48 ` Joel Sherrill
2013-03-16 23:24 ` Mike Frysinger
2013-03-17 1:03 ` Joel Brobecker
2013-03-17 15:10 ` Mike Frysinger
2013-03-17 1:13 ` Joel Sherrill
2013-03-17 15:09 ` Mike Frysinger
2013-03-17 16:02 ` Joel Brobecker
2013-03-17 16:11 ` Joel Sherrill
2013-03-17 4:16 ` Ralf Corsepius
2013-03-17 16:05 ` Joel Sherrill
[not found] ` <201303181405.55098.vapier@gentoo.org>
2013-03-20 17:51 ` Joel Sherrill
2013-03-20 18:29 ` Mike Frysinger
2013-03-20 18:48 ` Joel Sherrill
2013-03-27 11:21 ` Pedro Alves
2013-03-27 17:00 ` Mike Frysinger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=514318D8.8050309@rtems.org \
--to=ralf.corsepius@rtems.org \
--cc=gdb@sourceware.org \
--cc=joel.sherrill@OARcorp.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox