From: 320095285153-0001@t-online.de (Achim Gottinger)
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] PGCC
Date: Mon Feb 19 11:08:02 2001 [thread overview]
Message-ID: <3A915AB7.62757B5F@gottinger.de> (raw)
In-Reply-To: 20010219124314.A21137@kabbu.akopia.com
"Jerry A!" wrote:
> Hey Achim, I was looking at using pgcc instead of gcc proper. So, I've
> hacked up the gcc-2.95.2.1.ebuild file. Right now, I have it checking
> if "use pgcc" is set. If so, then it'll apply the patch cleanly.
>
> Here's a list of the changes I've made:
>
> . if/then blocks for "use pgcc"
> . grap gcc-2.95.2.1.tar.gz instead of gcc-2.95.2 + diff file
> . commented out A1 & A2--they appear to only be necessary for 2.95.2
> I will remove them from the final ebuild before committing if not
> necessary.
> . 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.
>
>
> 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.
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?
achim~
>
>
> Could you please look over this and let me know what you think?
>
> --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!
>
> ------------------------------------------------------------------------
>
> gcc-2.95.2.1.ebuildName: gcc-2.95.2.1.ebuild
> Type: Plain Text (text/plain)
next prev parent reply other threads:[~2001-02-19 18:07 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 [this message]
2001-02-19 12:01 ` Jerry A!
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=3A915AB7.62757B5F@gottinger.de \
--to=320095285153-0001@t-online.de \
--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