public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: fernando@stratus.swi.com.br
To: insight@sources.redhat.com
Subject: Failure Building Insight under cygwin 1.1.2
Date: Mon, 10 Jul 2000 09:48:00 -0000	[thread overview]
Message-ID: <200007101650.NAA03211@stratus.swi.com.br> (raw)

Hi Insight,

Sorry if this question has already been discussed, but I didn't find it
in the Insight mail archives...

I'm trying to build a Insight-5.0 to use it with powerpc-eabi-gcc cross
compiler. My host is cygwin 1.1.2 running under Windows NT Server 4.0
(SP6).

I used the options: --target=powerpc-eabi --prefix=/ppctools to
configure Insight.

After a long compilation time, I received the following output:

gcc -c -g -O2 -DDEFAULT_INLINE=INLINE_LOCALS
-DWITH_HOST_BYTE_ORDER=LITTLE_ENDIAN -DWITH_SMP=5
-DHAVE_TERMIOS_STRUCTURE -DHAVE_TERMIOS_CLINE -DHAVE_DEVZERO     -I.
-I/src/gdb/insight-5.0/sim/ppc
-I/src/gdb/insight-5.0/sim/ppc/../../include -I../../bfd
-I/src/gdb/insight-5.0/sim/ppc/../../bfd -I../../gdb
-I/src/gdb/insight-5.0/sim/ppc/../../gdb
-I/src/gdb/insight-5.0/sim/ppc/../../gdb/config
-I/src/gdb/insight-5.0/sim/ppc/../../mmalloc
/src/gdb/insight-5.0/sim/ppc/sim_calls.c
In file included from /src/gdb/insight-5.0/sim/ppc/sim_calls.c:43:
/src/gdb/insight-5.0/sim/ppc/../../gdb/defs.h:60: conflicting types for
`strsignal'
/usr/lib/gcc-lib/i686-pc-cygwin/2.95.2/../../../../include/string.h:71:
previous declaration of `strsignal'
make[2]: *** [sim_calls.o] Error 1
make[2]: Leaving directory `/tmp/build/gdb/sim/ppc'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/tmp/build/gdb/sim'
make: *** [all-sim] Error 2
make: Leaving directory `/tmp/build/gdb'

I tried some workarounds to solve the problem changing file
"sim_calls.c", but without success.

Someone can give me a "light" on this question???

Thank you very much,

Fernando



                 reply	other threads:[~2000-07-10  9:48 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=200007101650.NAA03211@stratus.swi.com.br \
    --to=fernando@stratus.swi.com.br \
    --cc=insight@sources.redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).