From: Daniel Robbins <drobbins@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] glibc-2.2.4-r6 should be fixed
Date: Fri, 21 Dec 2001 10:51:46 -0600 [thread overview]
Message-ID: <20011221105146.D29599@chiba.3jane.net> (raw)
In-Reply-To: <200112211747.fBLHlZJ07676@mars.prosoft.com.tr>
On Fri, Dec 21, 2001 at 07:47:24PM +0200, Aycan Irican wrote:
> Sorry but,
> Applying it, I got no change. Same results.
>
> When it makes "make install", I got errors like...
The ebuild has been confirmed working by me and someone else. You will
not be able to merge the new ebuild until you have a functional system
again, but once you do the new ebuid should work fine. Sorry for the
inconvenience.
Best Regards,
--
Daniel Robbins <drobbins@gentoo.org>
Chief Architect/President http://www.gentoo.org
Gentoo Technologies, Inc.
next prev parent reply other threads:[~2001-12-21 16:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-21 16:22 [gentoo-dev] glibc-2.2.4-r6 should be fixed Daniel Robbins
2001-12-21 17:47 ` Aycan Irican
2001-12-21 16:51 ` Daniel Robbins [this message]
2001-12-21 19:07 ` Tod M. Neidt
2001-12-21 19:12 ` Daniel Robbins
2001-12-21 19:34 ` Martin Schlemmer
2001-12-21 19:38 ` Daniel Robbins
2001-12-21 17:35 ` Daniel Robbins
2001-12-21 18:43 ` Taras
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=20011221105146.D29599@chiba.3jane.net \
--to=drobbins@gentoo.org \
--cc=gentoo-dev@gentoo.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