From: Peter Allin <pallists@peca.dk>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: sid@sourceware.org
Subject: Re: Build problems - no libiberty/pic
Date: Thu, 30 Mar 2006 04:59:00 -0000 [thread overview]
Message-ID: <442B65A0.6040703@peca.dk> (raw)
In-Reply-To: <y0macbbed4s.fsf@ton.toronto.redhat.com>
>This was a consequence of an earlier partially accepted contribution.
>I checked in some code that works/hacks around the situation. Please
>try it out.
>
>
>
Yes - that did it. It compiles fine now. I'm looking forward to
experimenting with it.
Thanks a lot,
Peter Allin
prev parent reply other threads:[~2006-03-30 4:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-26 21:16 Peter Allin
2006-03-27 22:28 ` Frank Ch. Eigler
2006-03-30 4:59 ` Peter Allin [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=442B65A0.6040703@peca.dk \
--to=pallists@peca.dk \
--cc=fche@redhat.com \
--cc=sid@sourceware.org \
/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).