From: Gene Smith <gds@chartertn.net>
To: insight@sources.redhat.com
Subject: Re: Error while "make all": "make[2]: *** No rule to make target `/libreadline.a', needed by `gdb'. Stop."
Date: Sun, 27 May 2012 06:19:00 -0000 [thread overview]
Message-ID: <jpsh1j$2ah$1@dough.gmane.org> (raw)
In-Reply-To: <CAA6dH32ciBQcAc=9ER2UVWmHx=jL5eFhpxj=Y2WYm1thu7jvHg@mail.gmail.com>
David Fernandez wrote, On 05/25/2012 06:10 PM:
> Hi Keith,
>
> On Fri, May 25, 2012 at 12:10 AM, Keith Seitz<keiths@redhat.com> wrote:
>> On 05/24/2012 03:45 PM, David Fernandez wrote:
>>
>>> I get the sources by doing:
>>> yumdownloader --source insight
>>> rpm -i insight-7.4.50-1.20120403cvs.fc16.src.rpm
>>> cd ~/rpmbuild/SPECS; rpmbuild -bp insight.spec
>>> cd ~/rpmbuild/BUILDROOT/arm-eabi/insight-7.4.50
Actually cd ~/rpmbuild/BUILDROOT
mkdir -p arm-eabi/insight-7.4.50
cd arm-eabi/insight-7.4.50
>>> ~/rpmbuild/BUILD/insight-7.4.50/configure --target=arm-eabi -v 2>&1 |
>>> tee configure.out
I see the same error. Doing this instead allows it to build as is:
~/rpmbuild/BUILD/insight-7.4.50/configure --with-system-readline
--target=arm-eabi -v 2>&1 | tee configure.out
The problem is that one of the patches to gdb/Makefile takes out the
path to readline.
If I put it back in it also works w/o the --with-system-readline:
Remove last patch from
rpmbuild/SOURCES/insight-7.4.50-readline-system.patch.
Are you trying to build an RPM for arm-eabi? I've never built an RPM (or
maybe once long ago)
so what is the next step? "make install" ?? I use insight with embedded
arm-eabi constantly but
have made my own custom version that works well from a CVS snapshot and
codesourery's gdb source.
-gene
next prev parent reply other threads:[~2012-05-27 6:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAA6dH30n=i40xuuAFxcwZzKHpLHcEP2J5GOr+03hb5B0qJ+vTw@mail.gmail.com>
2012-05-24 22:45 ` David Fernandez
2012-05-24 23:11 ` Keith Seitz
2012-05-25 22:11 ` David Fernandez
2012-05-27 6:19 ` Gene Smith [this message]
2012-05-27 18:49 ` David Fernandez
2012-05-28 3:25 ` Gene Smith
2012-05-29 12:48 ` Patrick Monnerat
2012-05-29 22:52 ` David Fernandez
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='jpsh1j$2ah$1@dough.gmane.org' \
--to=gds@chartertn.net \
--cc=insight@sources.redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).