public inbox for cgen@sourceware.org
 help / color / mirror / Atom feed
From: Doug Evans <dje@sebabeach.org>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: cgen@sourceware.org
Subject: Re: stop assuming cgen is scripted?
Date: Tue, 09 Jun 2009 21:29:00 -0000	[thread overview]
Message-ID: <4A2ED431.2000104@sebabeach.org> (raw)
In-Reply-To: <y0mfxeapyhx.fsf@fche.csb>

Frank Ch. Eigler wrote:
> Doug Evans <dje@sebabeach.org> writes:
>
>   
>> One thing I would like to change in cgen is the assumption that it's
>> scripted.  It originally didn't assume it was scripted.  How much
>> resistance is there to removing this assumption?
>>     
>
> Can you elaborate what this would entail in terms of code?  We're
> unlikely to have strong opinions in this regard; hobbit support was
> only reluctantly removed because of interoperability problems with
> guile, IIRC.
>
> But I think we're all just happy to see you back actively on the
> project.
>
> - FChE
>   

This isn't the entire issue, but IWBN if when I have a combined app+cgen 
tree, (e.g. binutils+cgen) I can configure binutils and I get a Makefile 
in cgen so I can do, for example, "make info".   [To be honest, to me 
it's more than WBN.  I'd really like the top level configury support for 
cgen put back.  Please pretty please?]

btw, one thing that depresses me is that the hobbit code is lost.
The sourceware repository was set up afterwards.
Any chance you can do me a favor and dig it up from some internal archive?

      reply	other threads:[~2009-06-09 21:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-08  4:46 Doug Evans
2009-06-08 14:54 ` Frank Ch. Eigler
2009-06-09 21:29   ` Doug Evans [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:
  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=4A2ED431.2000104@sebabeach.org \
    --to=dje@sebabeach.org \
    --cc=cgen@sourceware.org \
    --cc=fche@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).