public inbox for
 help / color / mirror / Atom feed
From: Keith Seitz <>
To: Jorge Calderon <>
Subject: Re: Bug
Date: Sat, 26 Oct 2013 18:47:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On 10/25/2013 10:40 PM, Jorge Calderon wrote:

> I'm unable to reach the bug reporting database (500 error):

I'll look into it, thanks.

> I getting the following error while running make on version 6.8a using Fedora:
> clang -c -DHAVE_CONFIG_H -ggdb3 -O0 -std=c99 -Wall -Werror -I.
> -I../../insight-6.8/libiberty/../include  -W -Wall -Wwrite-strings
> -Wc++-compat -Wstrict-prototypes -pedantic
> ../../insight-6.8/libiberty/regex.c -o regex.o
> ../../insight-6.8/libiberty/regex.c:130:7: error: incompatible redeclaration of
>        library function 'malloc' [-Werror,-Wincompatible-library-redeclaration]
> char *malloc ();

6.8? That's like eight years old... I *really* recommend trying 
something newer, like 7.5 or 7.6. You will, however, have to build it 
yourself, and that just got complicated. Actually, *really* complicated.

GDB has moved to GIT and is no longer maintaining the CVS repository. I 
am in the process of moving Insight to GIT, too, but I am not ready with it.

In the meantime, you can still grab GDB from either CVS or GIT and 
insight from CVS (src/gdb/gdbtk and src/libgui are all that is needed). 
I've given detailed instructions on how to patch and build insight here:

If you run into any problems, send a note to the mailing list, and I 
will help you get through it. Heck, if you want a working tarball or 
something, I can probably post a snapshot to the FTP site. Just let me know.


      reply	other threads:[~2013-10-26 18:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-26  5:40 Bug Jorge Calderon
2013-10-26 18:47 ` 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

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