From: Jerry A! <jerry@thehutt.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] PGCC
Date: Mon Feb 19 12:01:02 2001 [thread overview]
Message-ID: <20010219140058.A21535@kabbu.akopia.com> (raw)
In-Reply-To: <3A915AB7.62757B5F@gottinger.de>; from 320095285153-0001@t-online.de on Mon, Feb 19, 2001 at 06:41:11PM +0100
On Mon, Feb 19, 2001 at 06:41:11PM +0100, Achim Gottinger wrote:
: "Jerry A!" wrote:
:
: > . commented out A1..A2 patches sections in src_unpack(). Will also be
: > removed pending commit.
:
: Make these patches problems with pgcc? I removed a few other patches which
: made it in 2.95.2.1 but these
: where not in 2.95.2.1. Thats why they are still there.
I don't think that these patches will present a problem with pgcc. The
reason I commented them out was b/c they didn't even get downloaded when
I did an "ebuild ... fetch"
: > Is there any reason we don't build the texinfo docs?
:
: ? We build texinfo docs but we don't build texinfo because we have a separate
: package for that.
Okay, that's all I needed to know.
: I just commited my lates version of gcc 2.95.2.1-r1 which uses the "use
: build" if you compile for sys-build
: (in this case texinfo gets build).
: Should I merge it with your one or can you do it?
I'll be happy to take care of the merge. I want to do some more testing
and I wanted to make sure that the way I was going about this is okay
with you.
--Jerry
name: Jerry Alexandratos || Open-Source software isn't a
phone: 703.599.6023 || matter of life or death...
email: jerry@thehutt.org || ...It's much more important
|| than that!
next prev parent reply other threads:[~2001-02-19 19:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-19 10:43 [gentoo-dev] PGCC Jerry A!
2001-02-19 11:08 ` Achim Gottinger
2001-02-19 12:01 ` Jerry A! [this message]
2001-02-19 12:44 ` Achim Gottinger
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=20010219140058.A21535@kabbu.akopia.com \
--to=jerry@thehutt.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