[Bug 194011] Review Request: curry - Münster Curry compiler

[bugzilla at redhat.com]

Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug report.

Summary: Review Request: curry -  Münster Curry compiler


https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=194011





------- Additional Comments From gemi at bluewin.ch  2006-06-07 04:26 EST -------
(In reply to comment #3)
> "debug" is a different issue: Such libaries are rarely needed by anybody and
> often are of doubtful benefits. One would have to check for for what they are
> really needed and if shipping a "non-debug variant" isn't sufficient. In most
> cases a "-O2 -g" compiled "non-debug" variant + debug-info-rpms render "debug
> variants" superfluous. But with exotic compilers, one never knows.
I looked into this a little deeper: libcurry.a is the normal runtime library,
that is linked into every standalone program. libcurry_g.a is NOT
the same library compiled using gcc -g, but contains the code for the
declarative debugger of curry (this is similar to the standard
debugger in Prolog). If you compile using "cyc --debug" this library is
linked in addition to libcurry.a. I could imagine putting this library into
a separate package curry-debugger or curry-debug. However, then
cyc --debug fails.

-- 
Configure bugmail: https://bugzilla.redhat.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.