1 |
"Jerry A!" wrote: |
2 |
|
3 |
> Hey Achim, I was looking at using pgcc instead of gcc proper. So, I've |
4 |
> hacked up the gcc-2.95.2.1.ebuild file. Right now, I have it checking |
5 |
> if "use pgcc" is set. If so, then it'll apply the patch cleanly. |
6 |
> |
7 |
> Here's a list of the changes I've made: |
8 |
> |
9 |
> . if/then blocks for "use pgcc" |
10 |
> . grap gcc-2.95.2.1.tar.gz instead of gcc-2.95.2 + diff file |
11 |
> . commented out A1 & A2--they appear to only be necessary for 2.95.2 |
12 |
> I will remove them from the final ebuild before committing if not |
13 |
> necessary. |
14 |
> . commented out A1..A2 patches sections in src_unpack(). Will also be |
15 |
> removed pending commit. |
16 |
|
17 |
Make these patches problems with pgcc? I removed a few other patches which |
18 |
made it in 2.95.2.1 but these |
19 |
where not in 2.95.2.1. Thats why they are still there. |
20 |
|
21 |
> |
22 |
> |
23 |
> Is there any reason we don't build the texinfo docs? |
24 |
|
25 |
? We build texinfo docs but we don't build texinfo because we have a separate |
26 |
package for that. |
27 |
|
28 |
I just commited my lates version of gcc 2.95.2.1-r1 which uses the "use |
29 |
build" if you compile for sys-build |
30 |
(in this case texinfo gets build). |
31 |
Should I merge it with your one or can you do it? |
32 |
|
33 |
achim~ |
34 |
|
35 |
> |
36 |
> |
37 |
> Could you please look over this and let me know what you think? |
38 |
> |
39 |
> --Jerry |
40 |
> |
41 |
> name: Jerry Alexandratos || Open-Source software isn't a |
42 |
> phone: 703.599.6023 || matter of life or death... |
43 |
> email: jerry@×××××××.org || ...It's much more important |
44 |
> || than that! |
45 |
> |
46 |
> ------------------------------------------------------------------------ |
47 |
> |
48 |
> gcc-2.95.2.1.ebuildName: gcc-2.95.2.1.ebuild |
49 |
> Type: Plain Text (text/plain) |