public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: Russel Winder <russel.winder@concertant.com>
To: Insight <insight@sourceware.org>
Subject: Re: Compiling Insight
Date: Sat, 15 Aug 2009 15:46:00 -0000	[thread overview]
Message-ID: <1250351148.20123.314.camel@balin> (raw)
In-Reply-To: <1250338272.20123.292.camel@balin>

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

I take the plunge and checkout out the development repository.

Initially the build failed as texinfo wasn't installed.  The core
problem is marked as a warning but it causes the build to fail.  I think
there is an issue to sort out there.

The build then failed because flex wasn't installed.  I guess the config
phase should check for the presence of flex so as to avoid this failure.
I installed bison at the same time as flex so I don't know if that would
cause a problem as well.

With texinfo and flex (and bison) in place the build completed and
installed as required.

PS  It seems that 6,7,1 remains the version of insight in Debian and
hence Ubuntu.


On Sat, 2009-08-15 at 13:11 +0100, Russel Winder wrote:
> I have just downloaded 6.8.1 from the website, but when I try to compile
> it I get an error as shown below.  I am on Ubuntu 9.04 with the standard
> GCC installed.  Is this supposed to compile "out of the box"?
> 
> Thanks.
> 
>         gcc -c -g -O2   -I. -I.././gdb -I.././gdb/config -DLOCALEDIR="\"/opt/insight-6.8.1/share/locale\"" -DHAVE_CONFIG_H -I.././gdb/../include/opcode -I.././gdb/../readline/.. -I../bfd -I.././gdb/../bfd -I.././gdb/../include -I../libdecnumber -I.././gdb/../libdecnumber   -DMI_OUT=1 -DGDBTK -DTUI=1  -Wall -Wdeclaration-after-statement -Wpointer-arith -Wformat-nonliteral -Wno-pointer-sign -Wno-unused -Wno-switch -Wno-char-subscripts -Werror .././gdb/cli/cli-cmds.c
>         cc1: warnings being treated as errors
>         .././gdb/cli/cli-cmds.c: In function ‘pwd_command’:
>         .././gdb/cli/cli-cmds.c:323: error: ignoring return value of ‘getcwd’, declared with attribute warn_unused_result
>         make[2]: *** [cli-cmds.o] Error 1
>         make[2]: Leaving directory `/home/share/tmp/insight-6.8-1/gdb'
>         make[1]: *** [all-gdb] Error 2
>         make[1]: Leaving directory `/home/share/tmp/insight-6.8-1'
>         make: *** [all] Error 2

-- 
Russel.
=============================================================================
Dr Russel Winder      Partner
                                            xmpp: russel@russel.org.uk
Concertant LLP        t: +44 20 7585 2200, +44 20 7193 9203
41 Buckmaster Road,   f: +44 8700 516 084   voip: sip:russel.winder@ekiga.net
London SW11 1EN, UK   m: +44 7770 465 077   skype: russel_winder

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

  reply	other threads:[~2009-08-15 15:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-15 12:11 Russel Winder
2009-08-15 15:46 ` Russel Winder [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-06-30  0:40 Leslie Newell
2000-06-29  3:26 Leslie Newell
2000-06-29 15:47 ` Kai Ruottu

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=1250351148.20123.314.camel@balin \
    --to=russel.winder@concertant.com \
    --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).