public inbox for insight-prs@sourceware.org
help / color / mirror / Atom feed
From: kontakt@michaelstather.com
To: insight-gnats@sources.redhat.com
Subject: insight/281: Can´t compile insight
Date: Sat, 19 Nov 2005 00:53:00 -0000	[thread overview]
Message-ID: <20051119004315.8073.qmail@sourceware.org> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 2352 bytes --]


>Number:         281
>Category:       insight
>Synopsis:       Can´t compile insight
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sat Nov 19 00:53:01 GMT 2005
>Closed-Date:
>Last-Modified:
>Originator:     kontakt@michaelstather.com
>Release:        unknown-1.0
>Organization:
>Environment:

>Description:
I downloaded the newest version of insight on my SuSE 10.0 (gcc 4) system. When executing "make" I got:

gcc -DHAVE_CONFIG_H -I. -I. -I.. -fwritable-strings -I/home/michael/Desktop/insight-6.1/tcl/generic -I/home/michael/Desktop/insight-6.1/tk/generic -I/usr/X11R6/include -DHAVE_UNISTD_H=1 -DHAVE_LIMITS_H=1 -D_LARGEFILE64_SOURCE=1 -DTCL_WIDE_INT_TYPE=long\ long -DHAVE_STRUCT_STAT64=1 -DHAVE_TYPE_OFF64_T=1 -DHAVE_GETCWD=1 -DHAVE_OPENDIR=1 -DHAVE_STRSTR=1 -DHAVE_STRTOL=1 -DHAVE_STRTOLL=1 -DHAVE_STRTOULL=1 -DHAVE_TMPNAM=1 -DHAVE_WAITPID=1 -DHAVE_UNISTD_H=1 -DHAVE_SYS_PARAM_H=1 -DUSE_TERMIOS=1 -DHAVE_SYS_TIME_H=1 -DTIME_WITH_SYS_TIME=1 -DHAVE_TM_ZONE=1 -DHAVE_GMTIME_R=1 -DHAVE_LOCALTIME_R=1 -DHAVE_TM_GMTOFF=1 -DHAVE_TIMEZONE_VAR=1 -DHAVE_ST_BLKSIZE=1 -DSTDC_HEADERS=1 -DHAVE_SIGNED_CHAR=1 -DHAVE_LANGINFO=1 -DSTATIC_BUILD=1 -DPEEK_XCLOSEIM=1 -DHAVE_SYS_IOCTL_H=1  -DHAVE_UNISTD_H=1 -DHAVE_LIMITS_H=1 -D_LARGEFILE64_SOURCE=1 -DTCL_WIDE_INT_TYPE=long\ long -DHAVE_STRUCT_STAT64=1 -DHAVE_TYPE_OFF64_T=1 -DSTATIC_BUILD=1 -DPEEK_XCLOSEIM=1 -DSTDC_HEADERS=1 -DHAVE_SYS_TIME_H=1 -DTIME_WITH_SYS_TIME=1 -DHAVE_PW_GECOS=1  -I/home/michael/Desktop/insight-6.1/tk/generic/../unix -I/home/michael/Desktop/insight-6.1/tk/generic/../win -DTBL_VERSION=\"2.7\" -DTBL_COMMAND=\"table\" -DTBL_RUNTIME=\"tkTable.tcl\" -DTBL_RUNTIME_DIR=\"/usr/local/share/redhat/gui\" -DSTATIC_BUILD    -g -O2 -c subcommand.c
cc1: error: unrecognized command line option "-fwritable-strings"
make[3]: *** [subcommand.o] Fehler 1
make[3]: Leaving directory `/home/michael/Desktop/insight-6.1/libgui/src'
make[2]: *** [all-recursive] Fehler 1
make[2]: Leaving directory `/home/michael/Desktop/insight-6.1/libgui'
make[1]: *** [all-recursive-am] Fehler 2
make[1]: Leaving directory `/home/michael/Desktop/insight-6.1/libgui'
make: *** [all-libgui] Fehler 2

What can I do?
>How-To-Repeat:

>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:


             reply	other threads:[~2005-11-19  0:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-19  0:53 kontakt [this message]
2005-11-19  1:17 insight/281: Can´t " kseitz
2005-11-19 17:13 insight/281: Can't " Keith Seitz

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=20051119004315.8073.qmail@sourceware.org \
    --to=kontakt@michaelstather.com \
    --cc=insight-gnats@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).