From HassanR@avi.com  Wed Oct 15 15:27:00 2008
From: HassanR@avi.com (Hassan Radwan)
Date: Wed, 15 Oct 2008 15:27:00 -0000
Subject: LIBGLADE_PREFIX fail on build
Message-ID: <2131D39DDCC1CF4EBBDBA9994701D921A74566@hicksville.avi.com>

Hello,

I'm trying to build frysk on Ubuntu Hardy Heron and come across an error
while running the autogen.sh script:

checking for LIBGLADE_PREFIX... configure: error: package variable
prefix for libglade-2.0 empty, set environment variable LIBGLADE_PREFIX
configure: error: ../../frysk/frysk-gui/configure failed for frysk-gui

I've tried looking for help as to what LIBGLADE_PREFIX is supposed to be
set to, but haven't found anything nor did any of my guesses help. Can
someone please tell me what it's supposed to be?

Thanks!
Hassan


From mark@klomp.org  Thu Oct 30 08:38:00 2008
From: mark@klomp.org (Mark Wielaard)
Date: Thu, 30 Oct 2008 08:38:00 -0000
Subject: Nice usage of frysk
Message-ID: <1225355930.3289.2.camel@dijkstra.wildebeest.org>

Nice usage of frysk (fdebuginfo and fstack)
	
        Here's the result of a few minutes of hacking up something
        similar to Apport based on the awesome (and much underused)
        Frysk debugging tool kit. It doesn't post any backtraces on any
        Internet servers and has no fancy UI -- but it automatically
        dumps a stacktrace of every crashing process on the system to
        syslog and stores all kinds of data in /tmp/core.*/ for later
        inspection.

http://0pointer.de/blog/projects/automatic-backtrace.html


From tromey@redhat.com  Wed Dec 10 20:35:00 2008
From: tromey@redhat.com (Tom Tromey)
Date: Wed, 10 Dec 2008 20:35:00 -0000
Subject: upcoming bugzilla outage
Message-ID: <m3r64fixbd.fsf@fleche.redhat.com>

Hi all.  Please excuse the cross-post.  And, if you do respond, please
trim the CC list (but also please continue to CC me, since I am not on
all of these lists).

I've been wanting to move gdb from gnats to bugzilla for some time
now.  I think I've finally procrastinated enough.

I intend to do the switchover next Thursday, Dec 18.  If this poses a
problem for you, please let me know.

If you are seeing this on a list other than the gdb list, it is
because this outage will take down bugzilla for your project while I
do the transition.  An outage is necessary because we would like the
converted bug IDs to be sequential.

I will dump the database before starting, so if something awful
happens, I will have a backup.  I thought you'd want to know.

I have done this upgrade several times on a local bugzilla instance,
and I think it should go reasonably well.  Still, it may take a few
hours.  I'll start in the morning, US Mountain time.


GDB readers: I'm going to disable gnats before I start.  I'll send a
patch to update the web pages.  I have a patch to fix the scripts in
CVSROOT so that commits are logged in bugzilla, not gnats.  I will
check this in once everything is working.  If you could briefly
refrain from commits which update Gnats, that would be helpful.

Overseers: I'd like to keep the gnats database around for a while,
just in case we happen to need something.  But, I think that once this
conversion is complete, we can at the very least disable the service.

Tom