gt; Everything is well. I haven't tried out C++ yet though.
>
> Tom Veldhouse
> ve...@visi.com
>
> -Original Message-
> From: The Hermit Hacker
> To: Wilko Bulte
> Cc: obr...@nuxi.com ; curr...@freebsd.org
>
> Date: Monday, April 05, 1999 6:52 AM
>
Date: Monday, April 05, 1999 6:52 AM
Subject: Re: show stopper for EGCS import
>
>What does 'cc -v' show on your system? I just finished a 'make world' on
>mine, and it still says 2.7.2.1 ... am I missing something here? :(
>
>
To Unsubscribe: send mail to
What does 'cc -v' show on your system? I just finished a 'make world' on
mine, and it still says 2.7.2.1 ... am I missing something here? :(
On Sun, 4 Apr 1999, Wilko Bulte wrote:
> As David O'Brien wrote ...
> > > Yesterday I changed csu/i386-elf/ to build crtbegin.o and crtend.o from
> > > t
As David O'Brien wrote ...
> > Yesterday I changed csu/i386-elf/ to build crtbegin.o and crtend.o from
> > the EGCS source rather than our home-grown ones.
> ..snip..
> > I've made the same fix to lib/csu as I did libgcc, but now am getting
> > the same weird "install" problem Poul-Henning was ge
YAY!!
David, consider yourself signed up for a six pack of anything you like
to drink come the next USENIX. First 6 beers are on me (assuming you
don't mind if I pound a 7-up for each beer you drink, that is). :-)
- Jordan
> > Yesterday I changed csu/i386-elf/ to build crtbegin.o and crtend.o f
> > "sjlj-exceptions" type exception machanism for a while.
>
> Is there any way to tell gcc not to do this by default,
Yes, "-fno-sjlj-exceptions", but you will proably get core dumps when you
throw an exception.
--
-- David(obr...@nuxi.com -or- obr...@freebsd.org)
To Unsubscribe: sen
Why are exceptions handling on by default better yet do we know why exception
handling
is not needed by default with gcc-2.8? and has anyone spent time reading
the egcs requirements for exception handling?
Amancio
> On Sun, Apr 04, 1999 at 10:39:15AM -0700, Amancio Hasty wrote:
> >
>
On Sun, 4 Apr 1999, David O'Brien wrote:
> > Yesterday I changed csu/i386-elf/ to build crtbegin.o and crtend.o from
> > the EGCS source rather than our home-grown ones.
> ..snip..
> > I've made the same fix to lib/csu as I did libgcc, but now am getting
> > the same weird "install" problem Poul
On Sun, Apr 04, 1999 at 10:39:15AM -0700, Amancio Hasty wrote:
>
> What do you mean by: we are going to have to use ""sjlj-exceptions" type
> exception machanism for a while?
-fsjlj-exceptions is on by default.
--
-- David(obr...@nuxi.com -or- obr...@freebsd.org)
To Unsubscribe: send m
Cool,
What do you mean by: we are going to have to use ""sjlj-exceptions" type
exception machanism for a while?
Tnks,
Amancio
> > Yesterday I changed csu/i386-elf/ to build crtbegin.o and crtend.o from
> > the EGCS source rather than our home-grown ones.
> ..snip..
> > I've m
In article <19990403222515.a75...@nuxi.com>, David O'Brien
wrote:
> Yesterday I changed csu/i386-elf/ to build crtbegin.o and crtend.o
> from the EGCS source rather than our home-grown ones. This
> afternoon I switch my EGCS development machine back to a purely
> stock 4.0 SNAPSHOT and found tha
> Yesterday I changed csu/i386-elf/ to build crtbegin.o and crtend.o from
> the EGCS source rather than our home-grown ones.
..snip..
> I've made the same fix to lib/csu as I did libgcc, but now am getting
> the same weird "install" problem Poul-Henning was getting.
Well FMH! I found a typo I m
Yesterday I changed csu/i386-elf/ to build crtbegin.o and crtend.o from
the EGCS source rather than our home-grown ones. This afternoon I switch
my EGCS development machine back to a purely stock 4.0 SNAPSHOT and found
that GCC 2.7.2 cannot compile the new sources. This is the same problem
I had
13 matches
Mail list logo
