public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: Keith Seitz <keiths@redhat.com>
To: "Müller, Andreas, Prof. Dr." <andreas.mueller@h-da.de>,
	"insight@sourceware.org" <insight@sourceware.org>
Subject: Re: build on raspberry 3B+
Date: Sun, 02 Dec 2018 18:59:00 -0000	[thread overview]
Message-ID: <f4be64f1-36a4-5217-db82-aa770a013707@redhat.com> (raw)
In-Reply-To: <93D445DDAAD4584D8F631D16F40766AB979483C8@Vorlon.h-da.local>

On 12/2/18 10:30 AM, Müller, Andreas, Prof. Dr. wrote:

> I am trying to build the Insight software on a Raspberry Pi 3B+. I
> get the enclosed two errors when running "make" and "make install".
> Can you help me fixing them?

From make_messages:

if (/home/pi/src/insight-6.8/missing makeinfo --split-size=5000000 --split-size=
5000000 --version) >/dev/null 2>&1; then \
  for f in bfd.info bfd.info-[0-9] bfd.info-[0-9][0-9] bfd.i[0-9] bfd.i[0-9][0-9
]; do \
    if test -f $f; then mv $f $backupdir; restore=mv; else :; fi; \
  done; \
else :; fi && \
if /home/pi/src/insight-6.8/missing makeinfo --split-size=5000000 --split-size=5000000   -I ../../../src/insight-6.8/bfd/doc \
 -o bfd.info `test -f 'bfd.texinfo' || echo '../../../src/insight-6.8/bfd/doc/'`bfd.texinfo; \
then \
  rc=0; \
else \
  rc=$?; \
  $restore $backupdir/* `echo "./bfd.info" | sed 's|[^/]*$||'`; \
fi; \
rm -rf $backupdir; exit $rc
Makefile:390: recipe for target 'bfd.info' failed

There is no error message contained in here... Did you by chance redirect stdout
to a file when compiling and forget to redirect stderr?

Nonetheless, bfd.info failed, and I'm going to take a wild guess that your
system doesn't have makeinfo installed. This is in the texinfo package.

From make_install_messages:

/bin/bash ./libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I../../src/insight-6.8/bfd -I. -I. -I../../src/insight-6.8/bfd -I../../src/insight-6.8/bfd/../include     -W -Wall -Wstrict-prototypes -Wmissing-prototypes -Werror -g -O2 -c -o opncls.lo ../../src/insight-6.8/bfd/opncls.c
libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I../../src/insight-6.8/bfd -I. -I. -I../../src/insight-6.8/bfd -I../../src/insight-6.8/bfd/../include -W -Wall -Wstrict-prototypes -Wmissing-prototypes -Werror -g -O2 -c ../../src/insight-6.8/bfd/opncls.c -o opncls.o
Makefile:1071: recipe for target 'opncls.lo' failed

Again, no error messages here. [It looks like stderr is missing from the output.] However, for this one, I cannot guess off the top of my head what the problem might be.

Insight 6.8? That's *really* old. I would encourage you to clone the GIT repo
[git clone git://sourceware.org/git/insight.git] and build that. That's what I've
been using for several years now.

I don't believe we've done an "official" release in almost ten years. Maybe I should.

Keith

      reply	other threads:[~2018-12-02 18:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-02 18:31 Müller, Andreas, Prof. Dr.
2018-12-02 18:59 ` Keith Seitz [this message]

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=f4be64f1-36a4-5217-db82-aa770a013707@redhat.com \
    --to=keiths@redhat.com \
    --cc=andreas.mueller@h-da.de \
    --cc=insight@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).