From: Shahab Vahedi <shahab.vahedi@gmail.com>
To: Claude Robitaille <claude-robitaille@hotmail.com>
Cc: Gdb <gdb@sourceware.org>
Subject: Re: Building gdbserver
Date: Sun, 17 Apr 2022 12:23:44 +0200 [thread overview]
Message-ID: <YlvqsIlxJAlUpM71@gmail.com> (raw)
In-Reply-To: <DS7PR07MB7686262DE7AE7FE0A763C6AAF7F09@DS7PR07MB7686.namprd07.prod.outlook.com>
Hi Claude,
On Sun, Apr 17, 2022 at 03:35:52AM +0000, Claude Robitaille via Gdb wrote:
> Hi, I am trying to cross compile gdbserver.
>
> I am using this little script I did:
>
>
> #!/bin/bash
> #source in binutils-gdb
>
> mkdir gdbserver.build
> cd gdbserver.build
>
> ../binutils-gdb/gdbserver/configure --host=x86_64-w64-mingw32
> make
>
>
> But I get this error at the beginning of make
>
> Makefile:110: ../gnulib/Makefile.gnulib.inc: No such file or directory
> make: *** No rule to make target '../gnulib/Makefile.gnulib.inc'. Stop.
>
> I did try different with different release but most of them don't even go that far; is gdbserver new in binutils-gdb? Is it supposed to be compilable?
You have to use the top level configure. Something along the lines:
$ cd gdbserver.build
$ ../binutils-gdb/configure --host=x86_64-w64-mingw32
$ make all-gdbserver
$ make install-gdbserver DESTDIR=<whatever_makes_sense_for_you>
You can find more details in gdbserver's README file [1].
Cheers,
Shahab
[1]
https://sourceware.org/git/?p=binutils-gdb.git;a=blob;f=gdbserver/README;hb=HEAD#l81
next prev parent reply other threads:[~2022-04-17 10:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-17 3:35 Claude Robitaille
2022-04-17 10:23 ` Shahab Vahedi [this message]
2022-04-17 15:12 ` Claude Robitaille
2022-04-17 17:19 ` Shahab Vahedi
2022-04-17 18:07 ` Claude Robitaille
2022-04-17 19:40 ` Claude Robitaille
2022-04-18 1:40 ` Claude Robitaille
2022-04-18 15:38 ` Pedro Alves
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=YlvqsIlxJAlUpM71@gmail.com \
--to=shahab.vahedi@gmail.com \
--cc=claude-robitaille@hotmail.com \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).