Bug 17747 – guile not suitable for some development

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 17747 - guile not suitable for some development

Summary:	guile not suitable for some development

Status:	CLOSED WONTFIX

Aliases:	None

Product:	Red Hat Linux
Classification:	Retired
Component:	guile (Show other bugs)
Sub Component:
Version:	6.2
Hardware:	i386 Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Phil Knirsch
QA Contact:
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2000-09-20 12:14 EDT by Frank Ch. Eigler
Modified:	2015-03-04 20:08 EST (History)
CC List:	1 user (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2001-02-21 09:14:14 EST
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Frank Ch. Eigler 2000-09-20 12:14:28 EDT

Guile 1.3.* has built-in support for limited debugging, but this
functionality is conditional on the package being configured & built
with the "--enable-guile-debug" option.  While perhaps the presence
of this code slows down non-debugging sessions a bit, its absence
causes grief when debugging Scheme code.  The unavailability of
stack tracebacks are a real killer.  Please build the guile RPM with
this additional configure-time flag.

Comment 1 Phil Knirsch 2001-02-21 09:14:10 EST

We have considered your request here but unfortunately have to inform you that
we will not enabled the debuging option for the builds.

If you need assistance in how you can rebuild the guile RPM with the debugging
enabled feel free to drop me an email.

Read ya, Phil <phil@redhat.de>

Note You need to log in before you can comment on or make changes to this bug.