From: Keith Seitz <keiths@redhat.com>
To: John Cooper <jwhackwizard@yahoo.com>
Cc: insight@sourceware.org
Subject: Re: Cannot make insight-6.8-1 on openSuSE 11.4
Date: Tue, 31 May 2011 15:03:00 -0000 [thread overview]
Message-ID: <4DE50340.9090909@redhat.com> (raw)
In-Reply-To: <947424.37542.qm@web114216.mail.gq1.yahoo.com>
On 05/30/2011 05:00 PM, John Cooper wrote:
> Even though do not seem to have all the required dependencies, and the configure script seems to run without incident, I simply cannot make insight-6.8-1 on my openSuSE 11.4 [with KDE] install. Using the following commands from a terminal ...
A couple of preliminary questions/observations. First, are you really
using the "official" 6.8.1 release? I would highly recommend grabbing
something a bit newer. CVS is typically always stable -- I have used CVS
HEAD for the better part of ten years.
On linux one should not need to build the tcl packages (tcl, tk, itcl).
The build should pick up the installed system components, provided they
(and their -devel counterparts) are installed. I don't know about SuSE,
but on Fedora, the -devel packages contain all the necessary bits for
this to work.
> jwesleycooper@linux-twom:~/compile/insight-build> ../insight-6.8-1/configure> configout.txt 2> configerr.txt
> jwesleycooper@linux-twom:~/compile/insight-build> make> makelog.txt 2> makeerr.txt
>
> ... I have redirected both stdout and stderr from these commands to the files indicated, which I have included along with the generated config.log file in the config-make_out-err/tar.gz file attached to this message. Please let me know what the issue might be, and how I might resolve it.
This is the key: "cc1: warnings being treated as errors"
You're seeing a bunch of warnings which the build is treating as errors.
Use the configure flag --disable-werror to get around this.
Keith
prev parent reply other threads:[~2011-05-31 15:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-31 0:01 John Cooper
2011-05-31 15:03 ` 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=4DE50340.9090909@redhat.com \
--to=keiths@redhat.com \
--cc=insight@sourceware.org \
--cc=jwhackwizard@yahoo.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).