Re: -print-* command-line switches misbehave or are misdocumented
Why not just fix it, if not document the way it works, cutsie, "its a
developer feature" fools no one and just hands ammunition to the
anti Linux and GNU camp, they read these lists too!
--
Greetings Brian
> On Sat, 20 Jun 2009, H.J. Lu wrote:
>> I think it is a bad idea to include it in -Wall. You fixed 3 warnings in
>> gcc and I fixed 1 in binutils. If you have thousands of packages in C,
>> -Wall may generate hundreds of warnings. It will make gcc 4.5.0 unusable
>> to those people.
>
> A warning i
Dave makes a very important point, who to believe:
Certainly System header prototypes, but then the
file, line-number, and prototype which the implementation contradicts,
whenever.
mfg, Brian
Two quick questions:
(1) Is the feature roadmap for 4.5, 4.6 ... published anywhere
(2) What is the recommended way to force 32 bit build on 64 eg 86_64 and will
it work with libtool and all. I have a solution but its very ugly!
--
Greetings, Brian
OK, there are a few more things to say about gcc, and the kernel, and
distributions (also the way patches to both work, to both).
Stipulations: (a) I always try to run the current stable kernel, released by
the 'stable-team' led by GKH. But he is getting too good, stable is
2.6.27.10 but I am run
