Gentoo Archives: gentoo-dev

From: Doug Goldstein <cardoe@g.o>
To: gentoo-dev@g.o
Subject: Re: [gentoo-dev] GCC 3.1/3.2
Date: Sun, 28 Jul 2002 17:21:36
Message-Id: 3D446D30.4000408@gentoo.org
In Reply to: RE: [gentoo-dev] GCC 3.1/3.2 by Michael Mattsson
1 Michael Mattsson wrote:
2
3 >Just curious. Who are you sending patches to? Gentoo scripters, or
4 >independent QT/GTK developers?
5 >What kind of patches are you refering to? Gcc3.2 or kernel patches?
6 >Why arent any patches in the cvs tree? How many questions can I fit
7 >onto one paragraph?
8 >
9 >I'm kind of confused as I thought that pretty much all gentoo related
10 >code were script based. If this is not the case, then is it possible to
11 >get a list of gentoo specific modules that may be affected by future GCC
12 >upgrades? I ask this because I tend to use the latest GCC CVS
13 >snapshots for my development (currently gcc 3.1.3).
14 >
15 >
16 >
17 >Michael Mattsson
18 >Kyrana Inc.
19 >michel@××××××.com
20 >
21 >
22 >
23 >
24 >
25 >>-----Original Message-----
26 >>
27 >>
28 >
29 >
30 >
31 >>3.2 is labeled by GNU to be 100% multi-vender compliant with
32 >>the C++ ABI
33 >>now. Which is the core prob with the new gcc releases. By skipping
34 >>straight to 3.2 we'll avoid 2 problem transitions.. 1 from
35 >>2.95 to 3.1
36 >>and then from 3.1/3.1.1 to 3.2 instead we'll have 2.95 to
37 >>3.2. As one of
38 >>the gcc-3.1/gcc-3.2 Gentoo guys I support this plan (was one
39 >>of the ones
40 >>calling for it among the devs) and I'm working hard with all
41 >>the other
42 >>guys to send upstream patches to developers to make sure their
43 >>applications are ready for the new gcc-3.2 platform. (this
44 >>will benefit
45 >>all distros).
46 >>
47 >>--
48 >>Doug Goldstein
49 >>Developer (Laptops, WiFi, GCC-3.1)
50 >>Gentoo Linux
51 >>http://www.gentoo.org/~cardoe/
52 >>
53 >>
54 >>
55 >
56 >
57 >_______________________________________________
58 >gentoo-dev mailing list
59 >gentoo-dev@g.o
60 >http://lists.gentoo.org/mailman/listinfo/gentoo-dev
61 >
62 >
63 >
64 >
65 Most of my patches are actually in the Gentoo source tree. When you
66 emerge a package and you see a line that it's patching the source code
67 right after unpacking the source... that's possibly one of the gcc-3.1
68 patches. As far as where I send the patches to... I go to the
69 maintainer's website and e-mail it to him/her and also explain all my
70 changes. My patches aren't to specific Qt/GTK code because 99% of that
71 code is fine. It's all C++ syntaxing and what not really. And if you
72 wanna see lots of kernel hacks at patches by us Gentoo people... try
73 mjc-sources. Make sure to pick your architecture with (3.1) at the end
74 if you're using gcc-3.1.
75
76 --
77 Doug Goldstein
78 Developer (Laptops, WiFi, GCC-3.1)
79 Gentoo Linux http://www.gentoo.org/~cardoe/