public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "simark at simark dot ca" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug build/26136] when make it shows "make: *** No rule to make target '../alloc.c'. Stop"
Date: Fri, 19 Jun 2020 13:34:54 +0000 [thread overview]
Message-ID: <bug-26136-4717-pZiw59gFkZ@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-26136-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=26136
Simon Marchi <simark at simark dot ca> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |simark at simark dot ca
--- Comment #2 from Simon Marchi <simark at simark dot ca> ---
(In reply to AlanHu from comment #0)
> Command as below:
> cd gdb/gdbserver
> mkdir buid
> cd build
> ./configure --target=arm-poky-linux-gnueabi --host=arm-poky-linux-gnueabi
> make
The commands don't make sense. Apart from the "buid" / "build" typo, you seem
to be running ./configure in an empty directory, which doesn't make sense.
But it sounds like you are running gdbserver's configure script directly. You
need to run the top-level configure so that the whole tree is built.
If needed, you can pass --disable-binutils, --disable-gas, etc, to skip
building the other tools.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2020-06-19 13:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-19 2:07 [Bug build/26136] New: " hyc6643 at 126 dot com
2020-06-19 13:08 ` [Bug build/26136] " ssbssa at sourceware dot org
2020-06-19 13:34 ` simark at simark dot ca [this message]
2020-06-22 23:29 ` hyc6643 at 126 dot com
2020-06-22 23:32 ` simark at simark dot ca
2020-06-22 23:47 ` hyc6643 at 126 dot com
2020-06-23 0:15 ` hyc6643 at 126 dot com
2020-06-23 0:28 ` simark at simark dot ca
2020-08-09 20:49 ` tromey at sourceware dot org
2022-02-27 14:59 ` tromey at sourceware dot org
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=bug-26136-4717-pZiw59gFkZ@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@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).