public inbox for insight-prs@sourceware.org
help / color / mirror / Atom feed
From: Keith Seitz <keiths@redhat.com>
To: kseitz@sources.redhat.com
Cc: insight-prs@sources.redhat.com,
Subject: insight/179
Date: Thu, 29 Aug 2002 08:13:00 -0000 [thread overview]
Message-ID: <20020829151303.3136.qmail@sources.redhat.com> (raw)
The following reply was made to PR insight/179; it has been noted by GNATS.
From: Keith Seitz <keiths@redhat.com>
To: insight-gnats@sources.redhat.com
Cc: rnee@erols.com
Subject: insight/179
Date: Thu, 29 Aug 2002 08:06:35 -0700 (PDT)
From a SuSE developer on the gdb mailing list...
Keith
---------- Forwarded message ----------
Date: Thu, 29 Aug 2002 16:29:35 +0200
From: Andreas Jaeger <aj@suse.de>
To: Keith Seitz <keiths@redhat.com>
Cc: gdb@sources.redhat.com
Subject: Re: libiberty?
Keith Seitz <keiths@redhat.com> writes:
> On Thu, 29 Aug 2002, Andreas Jaeger wrote:
>
>> Keith Seitz <keiths@redhat.com> 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 seems like some header files are not installed, some extracts from
make.log:
checking for sys/wait.h... (cached) no
checking for vfork.h... (cached) no
checking for working vfork... (cached) no
checking for ANSI C header files... (cached) no
I really suspect a broken installation where some of the glibc header
files have been removed.
Andreas
--
Andreas Jaeger
SuSE Labs aj@suse.de
private aj@arthur.inka.de
http://www.suse.de/~aj
next reply other threads:[~2002-08-29 15:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-29 8:13 Keith Seitz [this message]
2002-08-29 8:23 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:
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=20020829151303.3136.qmail@sources.redhat.com \
--to=keiths@redhat.com \
--cc=insight-prs@sources.redhat.com \
--cc=kseitz@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).