public inbox for
help / color / mirror / Atom feed
From: Keith Seitz <>
Subject: insight/179
Date: Thu, 29 Aug 2002 08:23:00 -0000	[thread overview]
Message-ID: <> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1286 bytes --]

The following reply was made to PR insight/179; it has been noted by GNATS.

From: Keith Seitz <>
Subject: insight/179
Date: Thu, 29 Aug 2002 08:22:51 -0700 (PDT)

 Hmm... Are you using a modified glibc?
 ---------- Forwarded message ----------
 Date: Thu, 29 Aug 2002 16:51:41 +0200
 From: Andreas Schwab <>
 To: Keith Seitz <>
 Cc: Andreas Jaeger <>,
 Subject: Re: libiberty?
 Keith Seitz <> writes:
 |> On Thu, 29 Aug 2002, Andreas Jaeger wrote:
 |> > Keith Seitz <> writes:
 |> > 
 |> > > I just got a PR concerning a libiberty build failure on SuSE8.0...
 |> > 
 |> > Which PR?  Can I access the database somewhere?  I'll have a look.
 |> insight/179
 |> I appreciate any help you might be able to offer this user.
 It's a pilot error.  The reporter is using his own, probably modified,
 glibc headers.  There is nothing SuSE can do about.
 Andreas Schwab, SuSE Labs,
 SuSE Linux AG, Deutschherrnstr. 15-19, D-90429 Nürnberg
 Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
 "And now for something completely different."

             reply	other threads:[~2002-08-29 15:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-29  8:23 Keith Seitz [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-08-29  8:13 insight/179 Keith Seitz

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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).