public inbox for sid@sourceware.org
 help / color / mirror / Atom feed
From: "Frank Ch. Eigler" <fche@redhat.com>
To: Jim Blandy <jimb@redhat.com>
Cc: sid@sources.redhat.com, cgen@sources.redhat.com
Subject: Re: sid cgen cpus broken by absence of pic libiberty
Date: Wed, 02 Feb 2005 11:18:00 -0000	[thread overview]
Message-ID: <20050202111833.GA30374@redhat.com> (raw)
In-Reply-To: <vt28y67phl6.fsf@zenia.home>

[-- Attachment #1: Type: text/plain, Size: 446 bytes --]

Hi -


> I think the SID build is broken for CGEN-based processors.
> [...]
> Since worthies much worthier than I have struggled with making
> libiberty produce PIC object files and failed, I'm inclined to work on
> making the opcodes stuff and sid no longer depend on libiberty.  [...]

Thanks.  I'd like to "ditto" dje and suggest in this case going to
direct ctype.h.  Let's lose library/macro indirection unless it is
known to help.


- FChE

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

      parent reply	other threads:[~2005-02-02 11:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-02  7:13 Jim Blandy
2005-02-02  8:41 ` Doug Evans
2005-02-02 11:18 ` Frank Ch. Eigler [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=20050202111833.GA30374@redhat.com \
    --to=fche@redhat.com \
    --cc=cgen@sources.redhat.com \
    --cc=jimb@redhat.com \
    --cc=sid@sources.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).