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 (was Re: libiberty? (fwd)) Date: Thu, 29 Aug 2002 09:03:00 -0000 [thread overview] Message-ID: <20020829160300.26554.qmail@sources.redhat.com> (raw) [-- Warning: decoded text below may be mangled, UTF-8 assumed --] [-- Attachment #1: Type: text/plain, Size: 3525 bytes --] The following reply was made to PR insight/179; it has been noted by GNATS. From: Keith Seitz <keiths@redhat.com> To: aj@suse.de Cc: rnee@erols.com, <insight-gnats@sources.redhat.com> Subject: insight/179 (was Re: libiberty? (fwd)) Date: Thu, 29 Aug 2002 09:03:33 -0700 (PDT) Okay, I'm getting everyone on the list now! Robert, please see advice below wrt (re-)installing glibc-devel. Keith ---------- Forwarded message ---------- Date: Thu, 29 Aug 2002 17:58:06 +0200 From: Andreas Jaeger <aj@suse.de> To: Keith Seitz <keiths@redhat.com> Cc: Andreas Schwab <schwab@suse.de> Subject: Re: libiberty? (fwd) Hi keith, feel free to CC me on the PR instead of playing mediator. Keith Seitz <keiths@redhat.com> writes: > Hi, > > The user insists that he hasn't modified glibc in any way. Is it possible > that the appropriate headers weren't installed on his system? (Did he > forget to install some sort of package/RPM/.deb/whatever?) The headers are part of glibc-devel. And the error show that some files are missing. I propose to reinstall glibc-devel. > > Keith > ---------- Forwarded message ---------- > Date: Thu, 29 Aug 2002 11:43:14 -0400 > From: Robert Nee <rnee@erols.com> > To: Keith Seitz <keiths@redhat.com>, insight-gnats@sources.redhat.com > Cc: J D. Nee <rnee@erols.com> > Subject: Re: libiberty? (fwd) > > Sirs: > > I am not a software developer. I only recently installed SUSE 8.0 (i > registered my support key) on a new i686 computer as a NEW install. I > partioned the drive so Linux could be co-resident with Windows XP. I am not > using my "own" glibc headers and did not modify the existing glibc headers. > Are they under /usr/include/glib-1-2 ? There are only 2 files there. I don't > really know where the glibc headers are supposed to be. > Should I just reinstall everything over? I 'm afraid to try to uninstall > glibc from the "base" package as YAST may not work and I may not be able to > re-install it. Any suggestions? > Thanks, > Bob Nee > > > > ----- Original Message ----- > From: Keith Seitz <keiths@redhat.com> > To: <insight-gnats@sources.redhat.com> > Cc: <rnee@erols.com> > Sent: Thursday, August 29, 2002 11:07 AM > Subject: Re: libiberty? (fwd) > > >> Hmm... Are you using a modified glibc? >> >> Keith >> ---------- Forwarded message ---------- >> Date: Thu, 29 Aug 2002 16:51:41 +0200 >> From: Andreas Schwab <schwab@suse.de> >> To: Keith Seitz <keiths@redhat.com> >> Cc: Andreas Jaeger <aj@suse.de>, 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's a pilot error. The reporter is using his own, probably modified, >> glibc headers. There is nothing SuSE can do about. >> >> Andreas. >> >> -- >> Andreas Schwab, SuSE Labs, schwab@suse.de >> 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." >> > > -- Andreas Jaeger SuSE Labs aj@suse.de private aj@arthur.inka.de http://www.suse.de/~aj
next reply other threads:[~2002-08-29 16:03 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-08-29 9:03 Keith Seitz [this message] 2002-08-29 14:13 Robert Nee
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=20020829160300.26554.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: linkBe 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).