Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: teawater@gmail.com
Cc: Kai.Tietz@onevision.com, gdb-patches@sourceware.org
Subject: Re: Build failure for x86_64-pc-mingw32 target
Date: Wed, 06 May 2009 10:19:00 -0000	[thread overview]
Message-ID: <200905061019.n46AJ52j007031@brahms.sibelius.xs4all.nl> (raw)
In-Reply-To: <daef60380905060205h6bc1c9d5n4ea58c921f80d5ea@mail.gmail.com> 	(message from Hui Zhu on Wed, 6 May 2009 17:05:09 +0800)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1680 bytes --]

> Date: Wed, 6 May 2009 17:05:09 +0800
> From: Hui Zhu <teawater@gmail.com>
> 
> mingw32 don't have bzero?
> Could you please help me try to build some code that have bzero in mingw?

Probably best to replace bzero with memset.

> On Wed, May 6, 2009 at 16:50, Kai Tietz <Kai.Tietz@onevision.com> wrote:
> > Hello,
> >
> > I noticed a failure while building gdb for x64 target. It seems to be an
> > new regression.
> >
> > x86_64-pc-mingw32-gcc -g -O2 -D__USE_MINGW_ACCESS   -I. -I../../src/gdb
> > -I../../
> > src/gdb/common -I../../src/gdb/config
> > -DLOCALEDIR="\"/usr/local/share/locale\""
> > -DHAVE_CONFIG_H -I../../src/gdb/../include/opcode
> > -I../../src/gdb/../readline/..
> >  -I../bfd -I../../src/gdb/../bfd -I../../src/gdb/../include
> > -I../libdecnumber -I
> > ../../src/gdb/../libdecnumber -I./../intl -I../../src/gdb/gnulib -Ignulib
> > -DMI_
> > OUT=1  -Wall -Wdeclaration-after-statement -Wpointer-arith
> > -Wformat-nonliteral -
> > Wno-pointer-sign -Wno-unused -Wno-switch -Wno-char-subscripts -Wno-format
> > -Werro
> > r -c -o i386-tdep.o -MT i386-tdep.o -MMD -MP -MF .deps/i386-tdep.Tpo
> > ../../src/g
> > db/i386-tdep.c
> > cc1: warnings being treated as errors
> > ../../src/gdb/i386-tdep.c: In function 'i386_process_record':
> > ../../src/gdb/i386-tdep.c:2996: error: implicit declaration of function
> > 'bzero'
> > ../../src/gdb/i386-tdep.c:2996: error: incompatible implicit declaration
> > of buil
> > t-in function 'bzero'
> > make[2]: *** [i386-tdep.o] Error 1
> >
> > Cheers,
> > Kai
> >
> > |  (\_/)  This is Bunny. Copy and paste Bunny
> > | (='.'=) into your signature to help him gain
> > | (")_(") world domination.
> >
> >
> 
> 


      parent reply	other threads:[~2009-05-06 10:19 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-30  6:38 [RFA] Fix memory leak in gdbserver Doug Evans
2009-04-30  9:28 ` Pedro Alves
2009-05-06  8:50   ` Build failure for x86_64-pc-mingw32 target Kai Tietz
2009-05-06  9:05     ` Hui Zhu
2009-05-06  9:37       ` Pedro Alves
2009-05-06 10:46         ` Hui Zhu
2009-05-06 11:20           ` Hui Zhu
2009-05-06 11:36             ` Kai Tietz
2009-05-06 16:03         ` [ARI] Add "bzero" (was: "Re: Build failure for x86_64-pc-mingw32 target") Joel Brobecker
2009-05-06 16:53           ` Joel Brobecker
2009-05-06 18:11           ` Eli Zaretskii
2009-05-06 18:37             ` Joel Brobecker
2009-05-18 19:24           ` [ARI] Add "bzero" Tom Tromey
2009-05-20  5:19             ` Joel Brobecker
2009-05-21  0:27             ` Joel Brobecker
2009-05-27 18:15               ` Tom Tromey
2009-05-06 10:19       ` Mark Kettenis [this message]

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=200905061019.n46AJ52j007031@brahms.sibelius.xs4all.nl \
    --to=mark.kettenis@xs4all.nl \
    --cc=Kai.Tietz@onevision.com \
    --cc=gdb-patches@sourceware.org \
    --cc=teawater@gmail.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