From: asmwarrior <asmwarrior@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb@sourceware.org
Subject: Re: gdb build error under msys+mingw: strip can't handle gdb-add-index.exe
Date: Tue, 11 Sep 2018 03:20:00 -0000 [thread overview]
Message-ID: <aa74329d-babb-54ca-a871-3b7e54231e61@gmail.com> (raw)
In-Reply-To: <83lg89q0s1.fsf@gnu.org>
On Mon Sep 10 2018 15:17:34 GMT+0800, Eli Zaretskii wrote:
>> From: asmwarrior <asmwarrior@gmail.com>
>> Date: Tue, 24 Jul 2018 22:13:43 +0800
>>
>> if test "x$transformed_name" = x; then \
>> transformed_name=gdb-add-index ; \
>> else \
>> true ; \
>> fi ; \
>> install -s ../../binutils-gdb/gdb/contrib/gdb-add-index.sh \
>> /d/code/build_gdb/bin2017/mingw/bin/$transformed_name.exe
>> D:\code\i686-5.4.0-release-posix-dwarf-rt_v5-rev0\mingw32\bin\strip.exe:d:/code/
>> build_gdb/bin2017/mingw/bin/gdb-add-index.exe: File format not recognized
>> install: strip failed
>> make[1]: *** [install-only] Error 1
>> make[1]: Leaving directory `/d/code/build_gdb/mybuildcpp2/gdb'
>> make: *** [install] Error 2
>> make: Leaving directory `/d/code/build_gdb/mybuildcpp2/gdb'
>>
>>
>> Where does the file gdb-add-index.exe come from? How to solve this issue?
>> Any ideas? Thanks.
> This was due to a bug in gdb/Makefile.in, now fixed.
>
> Thanks.
Hi, Eli, thanks for the fix.
Also, please close this GDB bug report:
23516 – gdb build error under msys+mingw: strip can't handle gdb-add-index.exe - https://sourceware.org/bugzilla/show_bug.cgi?id=23516
Asmwarrior
next prev parent reply other threads:[~2018-09-11 3:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-24 14:14 asmwarrior
2018-07-24 14:18 ` asmwarrior
2018-07-24 14:46 ` Eli Zaretskii
2018-09-10 7:17 ` Eli Zaretskii
2018-09-11 3:20 ` asmwarrior [this message]
2018-09-11 7:44 ` Eli Zaretskii
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=aa74329d-babb-54ca-a871-3b7e54231e61@gmail.com \
--to=asmwarrior@gmail.com \
--cc=eliz@gnu.org \
--cc=gdb@sourceware.org \
/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