Re: tlug: ccp

[Scott Stone <sstone@example.com>]

On Wed, 16 Dec 1998, Stephen J. Turnbull wrote:

> >>>>> "Chris" == Chris Sekiya <chris@example.com> writes:
> 
>     Chris> It can.  Up until 1.1.1 there were gcse problems in targets
>     Chris> that didn't have a plethora of registers (i.e., Intel).
>     Chris> I've had pretty good experiences with egcs.
> 
> Good for you.
> 
> I note that no distribution in their right mind builds the kernel with
> egcs yet, at least they all seem to say "gcc 2.7.2.3".  Also, egcs

Slackware builds their kernels with egcs.  At least, they told me this at
Comdex...

> _definitely_ fucks up XEmacs's `unexec' functionality on some
> platforms (Linux Alpha and HPUX, although apparently not Linux Intel).
> 

'unexec' -- how exactly does that work?  I want to try that and make sure
I didn't barney anything with xemacs...

> It's sufficiently widespread and poorly understood that simply puking
> and dying when configure finds egcs 1.1.1 has been seriously suggested
> by Kyle Jones, who puts _you_ to shame when it comes to standards
> conformance and trusting own builds anal-retentiveness.

The 2.0.36 kernel headers include a #error directive if it finds egcs or
gcc 2.8.x, so compiling anything that includes /usr/include/linux/types.h
will puke and die with egcs.

This seems to be a new 'feature' for 2.0.36.

--------------------------------------------------
Scott M. Stone <sstone@example.com, sstone@example.com>
Head of TurboLinux Development/Systems Administrator
Pacific HiTech, Inc (USA) / Pacific HiTech, KK (Japan)


------------------------------------------------------------------
Next Nomikai: 15 January 1999, 19:30 Tengu TokyoEkiMae 03-3275-3691
Next Technical Meeting: 13 February, 12:30               Place: TBD
------------------------------------------------------------------
more info: http://tlug.linux.or.jp                     Sponsor: PHT