From: asmwarrior <asmwarrior@gmail.com>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb@sourceware.org,
MinGW Users List <mingw-users@lists.sourceforge.net>,
Chris Sutcliffe <ir0nh34d@gmail.com>,
Xun Xun <xunxun1982@gmail.com>
Subject: Re: gdb (gdbserver.exe) build problem under msys
Date: Thu, 27 Oct 2011 14:48:00 -0000 [thread overview]
Message-ID: <4EA90AEB.1020609@gmail.com> (raw)
In-Reply-To: <201110261536.18038.pedro@codesourcery.com>
Hi, all, I have solved my problem.
It's quite simple problem due to the Line Ending.
As some days ago, I updated the MSYSGit to a new version, and then MsysGit by default will convert the Linux LF line ending to Windows CRLF format. (when I used this new MSYSGit to pull from the remote gdb git, the new updated file in my local copy will have CRLF format). So, I found that in the source tree, the file gdb/gdbserver/config.in has the CRLF format, and this will result a wrong file in the build tree gdb/gdbserver/config.h.
(I have used to run the "config.status --debug" to see whether the awk script works fine to replace macros in config.in)
Changing all the related files to LF format solved the problem, and now all was built successfully.
Sorry, for the inconvenience.
In fact, I have meet such kind of problem one years ago, see: (The problem bite me again today)
See the post of mine on how to solve such problem.
http://sourceware.org/ml/gdb/2010-12/msg00043.html
Thank you!
Asmwarrior
ollydbg from codeblocks' forum
next prev parent reply other threads:[~2011-10-27 7:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-26 14:36 asmwarrior
2011-10-26 14:49 ` Pedro Alves
2011-10-27 0:55 ` Asmwarrior
2011-10-27 2:31 ` Asmwarrior
2011-10-27 7:10 ` Asmwarrior
2011-10-27 14:48 ` asmwarrior [this message]
2011-10-26 16:37 ` Joel Brobecker
2011-10-26 19:10 ` Pedro Alves
2011-10-26 23:10 ` Petr Hluzín
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=4EA90AEB.1020609@gmail.com \
--to=asmwarrior@gmail.com \
--cc=gdb@sourceware.org \
--cc=ir0nh34d@gmail.com \
--cc=mingw-users@lists.sourceforge.net \
--cc=pedro@codesourcery.com \
--cc=xunxun1982@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