public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
* Building problem
@ 2013-03-27  0:47 Jan Murawski
  2013-03-27  4:24 ` Keith Seitz
  0 siblings, 1 reply; 3+ messages in thread
From: Jan Murawski @ 2013-03-27  0:47 UTC (permalink / raw)
  To: insight

[-- Attachment #1: Type: text/plain, Size: 2453 bytes --]

Hi all,

I am trying to build insight and end up receiving the following message.
What am I missing?

Cheers,
Jan


jan@xyn:/tmp/insight-6.8/insigth$ make
make[1]: Entering directory `/tmp/insight-6.8/insigth'
make[2]: Entering directory `/tmp/insight-6.8/insigth/libiberty'
make[3]: Entering directory `/tmp/insight-6.8/insigth/libiberty/testsuite'
make[3]: Für das Ziel »all« ist nichts zu tun.
make[3]: Leaving directory `/tmp/insight-6.8/insigth/libiberty/testsuite'
make[2]: Leaving directory `/tmp/insight-6.8/insigth/libiberty'
make[2]: Entering directory `/tmp/insight-6.8/insigth/intl'
make[2]: Für das Ziel »all« ist nichts zu tun.
make[2]: Leaving directory `/tmp/insight-6.8/insigth/intl'
make[2]: Entering directory `/tmp/insight-6.8/insigth/bfd'
Making info in doc
make[3]: Entering directory `/tmp/insight-6.8/insigth/bfd/doc'
restore=: && backupdir=".am$$" && \
rm -rf $backupdir && mkdir $backupdir && \
if (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 makeinfo --split-size=5000000 --split-size=5000000   -I
../../../bfd/doc \
 -o bfd.info `test -f 'bfd.texinfo' || echo
'../../../bfd/doc/'`bfd.texinfo; \
then \
  rc=0; \
else \
  rc=$?; \
  $restore $backupdir/* `echo "./bfd.info" | sed 's|[^/]*$||'`; \
fi; \
rm -rf $backupdir; exit $rc
../../../bfd/doc/bfd.texinfo:326: unknown command `colophon'
../../../bfd/doc/bfd.texinfo:337: unknown command `cygnus'
../../../bfd/doc/elf.texi:11: raising the section level of
@subsubsection which is too low
make[3]: *** [bfd.info] Fehler 1
make[3]: Leaving directory `/tmp/insight-6.8/insigth/bfd/doc'
Making info in po
make[3]: Entering directory `/tmp/insight-6.8/insigth/bfd/po'
make[3]: Für das Ziel »info« ist nichts zu tun.
make[3]: Leaving directory `/tmp/insight-6.8/insigth/bfd/po'
make[3]: Entering directory `/tmp/insight-6.8/insigth/bfd'
make[3]: Für das Ziel »info-am« ist nichts zu tun.
make[3]: Leaving directory `/tmp/insight-6.8/insigth/bfd'
make[2]: *** [info-recursive] Fehler 1
make[2]: Leaving directory `/tmp/insight-6.8/insigth/bfd'
make[1]: *** [all-bfd] Fehler 2
make[1]: Leaving directory `/tmp/insight-6.8/insigth'
make: *** [all] Fehler 2
jan@xyn:/tmp/insight-6.8/insigth$


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: Building problem
  2013-03-27  0:47 Building problem Jan Murawski
@ 2013-03-27  4:24 ` Keith Seitz
       [not found]   ` <BAY002-W10523A8D01D4489A80368B4A8D10@phx.gbl>
  0 siblings, 1 reply; 3+ messages in thread
From: Keith Seitz @ 2013-03-27  4:24 UTC (permalink / raw)
  To: Jan Murawski; +Cc: insight

On 03/26/2013 05:46 PM, Jan Murawski wrote:

> I am trying to build insight and end up receiving the following message.
> What am I missing?

6.8 is several years old. You are appear to be running into autotools 
problems with the (now) outdated configurey in that source tarball.

Normally, I would recommend grabbing CVS HEAD or a gdb release and the 
same vintage src/gdb/gdbtk directory from CVS to go with it. However, 
I've been sitting on quite a few patches to make it work (or at least 
make it work better) on many platforms. So this may or may not work for 
you. Or it may be more trouble than it is worth.

However, I believe insight is tagged on the gdb_7_5-branch. It is not 
yet tagged on the (recently made) 7.6 branch.

I can try to make a 7.6 release candidate in the next few days and post 
it to sourceware. I've just been swamped lately.

Keith

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: Building problem
       [not found]   ` <BAY002-W10523A8D01D4489A80368B4A8D10@phx.gbl>
@ 2013-03-27  5:26     ` Keith Seitz
  0 siblings, 0 replies; 3+ messages in thread
From: Keith Seitz @ 2013-03-27  5:26 UTC (permalink / raw)
  To: Sefer Tov; +Cc: Jan Murawski, insight

On 03/26/2013 10:15 PM, Sefer Tov wrote:

> Thanks for the reply. I was actually trying to build the CVS HEAD version.

I built that this afternoon for x86_64-linux without incident.

> Seems like parts of the GDB code just won't compile with GCC 4.6
> complaining about C++ adherence problems (parts of the simulator) and
> after repeatedly patching them I eventually had to give up. I assume
> that an older compiler (maybe GCC 3.4 or 4.3) would accept that code
> however it's harder to get them built for a dual-arch (x86/x64) environment.

Over the past few days, there has been quite a bit of brokenness in the 
simulators. Developers are working to sort it out. See, for example:

http://sourceware.org/ml/gdb-patches/2013-03/msg00871.html

[This is not the only thread on it; just the one I remember reading 
about the most over the past week.]

Does your problem sound anything like that? [It doesn't really, but 
without actual log of the build, it is unwise to commit. :-)]

> Have you tried building the CVS HEAD with newer GCC? I wonder if you'd
> be encountering the same issues.

I'm using gcc version 4.6.3 20120306 (Red Hat 4.6.3-2) (GCC). This is 
the Fedora 15 system compiler.

Keith

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2013-03-27  5:26 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2013-03-27  0:47 Building problem Jan Murawski
2013-03-27  4:24 ` Keith Seitz
     [not found]   ` <BAY002-W10523A8D01D4489A80368B4A8D10@phx.gbl>
2013-03-27  5:26     ` Keith Seitz

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).