In article <19990403193632.a55...@titan.klemm.gtn.com>,
Andreas Klemm wrote:
> Got the latest egcs port
>
> # $Id: Makefile,v 1.53 1999/03/30 02:58:02 obrien Exp $
>
> Build X11R6 with the following CFLAGS:
>
> -pipe -mpentiumpro -O2
>
> I'm still running X11 and after ,make install' I'
According to David E . O'Brien:
> src/lib/csu/i386-elf will build and install crtbegin.o and crtend.o from
> the EGCS sources. Otherwise we have to use the poorer exception
> unwinding method.
Is there a runtime overhead of using these files even for C programs ?
--
Ollivier ROBERT -=- FreeBSD:
According to Alex Zepeda:
> Personally, I'd vote for using the new runtime objects, and forcing binary
> incompatibility. It's worth it IMO for the exception handling support if
> nothing else. However, if you're dead set against it, just back up your
> runtime objects, and edit the spec file (li
* From: "David O'Brien"
* So the fix we mentioned might not be needed with the base EGCS. Maybe
* you can just compile all the ports just to see where we stand. I don't
Well, as soon as the first snapshot with the system egcs is released,
I'm planning to grab it and run the build through it
Only thing I can see to note is that the cvs mailing lists are still
apparently down, so notification of this (and any other changes which take
place) won't go out to the interested listeners. If jmb is planning to re-send
all of the bounced email when he fixes the problem, that's okay.
Kris
cvsup around 17:30 PST
--
>>> elf make world started on Sat Apr 3 17:33:29 PST 1999
--
--
>>> elf make world complet
At 4:28 pm -0800 3/4/99, David O'Brien wrote:
>Can someone with a FAST machine do a CVSup from Freefall and `make world'
>to verify that it is not broken?
>>> elf make world completed on Sun Apr 4 03:07:53 BST 1999
cvsup'd (from the UK server) at Sun Apr 4 01:50:56 BST 1999
--
Bob Bishop
-Original Message-
From: David O'Brien
To: Jordan K. Hubbard ; Steve Price
Cc: curr...@freebsd.org
Date: Saturday, April 03, 1999 19:29
Subject: Re: X problems using egcs as compiler
>> Better yet, can we just run with this today instead of tomorrow?
>
>Can so
Once you say the word that egcs is the default and a make world will
actually use it, I'll be more than happy to do so immediately with
my dual PII-450 box here.
- Jordan
> > Better yet, can we just run with this today instead of tomorrow?
>
> Can someone with a FAST machine do a CVSup from Fre
Just finished doing a cvsup and currently doing a make world. Should be done
in less than 80 minutes .
Cheers,
Amancio
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
David O'Brien wrote:
>
> Can someone with a FAST machine do a CVSup from Freefall and `make world'
> to verify that it is not broken?
>
CVSupped from 01:25 BST, make -j12 -DCLOBBER world on an SMP box, both
ELF and aout libraries generated, compile options -02 -m486, all clear.
The word is go.
At 04:28 PM 4/3/99 -0800, David O'Brien wrote:
Better yet, can we just run with this today instead of tomorrow?
Can someone with a FAST machine do a CVSup from Freefall and `make world'
to verify that it is not broken?
My machines are either EGCS'ified, 3.1-CURRENT, or take 5 hours to `make
wo
On Sat, 3 Apr 1999, David O'Brien wrote:
# > Better yet, can we just run with this today instead of tomorrow?
#
# Can someone with a FAST machine do a CVSup from Freefall and `make world'
# to verify that it is not broken?
Doing it now. Going out to grab a bite to eat with the family
but I shou
David O'Brien wrote:
>
> > Better yet, can we just run with this today instead of tomorrow?
>
> Can someone with a FAST machine do a CVSup from Freefall and `make world'
> to verify that it is not broken?
>
> My machines are either EGCS'ified, 3.1-CURRENT, or take 5 hours to `make
> world'.
>
>
On Sat, 3 Apr 1999, Jordan K. Hubbard wrote:
# Better yet, can we just run with this today instead of tomorrow? I
# see no reason to wait any further, and some of us have more time this
# weekend to work on testing things which a Sunday schedule would
# collapse to less than half a day.
You're r
> Better yet, can we just run with this today instead of tomorrow?
Can someone with a FAST machine do a CVSup from Freefall and `make world'
to verify that it is not broken?
My machines are either EGCS'ified, 3.1-CURRENT, or take 5 hours to `make
world'.
--
-- David(obr...@nuxi.com -or- o
> See above. Can you send me a set of instructions for turning gcc
> off and egcs on in the base distribution?
Better yet, can we just run with this today instead of tomorrow? I
see no reason to wait any further, and some of us have more time this
weekend to work on testing things which a Sunday
On Sat, 3 Apr 1999, David O'Brien wrote:
# I'm not sure the best way to approach this. The specification file used
# in the port is different from the one that will be in the base system.
# (the on in the Port is more stock EGCS) The base system will have many
# more of our hacks.
I don't know
On Sat, 3 Apr 1999, Amancio Hasty wrote:
> Yes, it is most likely a DWARF2_UNWIND issue at least that is what I
> concluded in trying to support Electric Fire also someone should
> investigate whether egcs supports exception handling without thread
> support if memory does not fail me egcs require
Yes, it is most likely a DWARF2_UNWIND issue at least that is what I concluded
in
trying to support Electric Fire also someone should investigate whether egcs
supports
exception handling without thread support if memory does not fail me egcs
requires
thread support for exception handling. Perhap
> The problem is that egcs 1.1.2 has its own crt*.o files and use them in
> place of the FreeBSD one. By moving the files elsewhere, it works. I don't
> know the effect on exceptions though.
If that is the problem, then it sounds like a DWARF2_UNWIND issue.
> I don't know what David plan to do w
I have been compiling Netscape's Java VM Electric Fire which is written on
C++ with
no problems however I have been using the "-fexceptions" flag.
Amancio
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
> I got everything setup to build the entire ports collection and
> sometime during the night the big IDE disk that I keep all the
I'm not sure the best way to approach this. The specification file used
in the port is different from the one that will be in the base system.
(the on in the Port is
> gcc version egcs-2.91.66 19990314 (egcs-1.1.2 release)
> /usr/local/lib/gcc-lib/i386-portbld-freebsd3.1/egcs-2.91.66/collect2 -m
> elf_i38
> 6 -dynamic-linker /usr/libexec/ld-elf.so.1 -o resize /usr/lib/crt1.o
> /usr/lib/cr
> ti.o /usr/local/lib/gcc-lib/i386-portbld-freebsd3.1/egcs-2.91.66/crt
On Sat, 3 Apr 1999, Ollivier Robert wrote:
> According to Amancio Hasty:
> > Actually, it probably means that the program must be compiled with
> > "-fexecptions".
>
> The problem is that egcs 1.1.2 has its own crt*.o files and use them in
> place of the FreeBSD one. By moving the files elsewher
On Sat, Apr 03, 1999 at 11:51:54AM -0800, David O'Brien wrote:
> > andr...@titan{1001} $ xterm
> > /usr/libexec/ld-elf.so.1: /usr/X11R6/lib/libXaw.so.6: Undefined symbol
> > "__deregister_frame_info"
> > Exit 1
> >
> > Is this a problem with egcs ? Or did I overlook something ?
>
> Please recomp
According to Amancio Hasty:
> Actually, it probably means that the program must be compiled with
> "-fexecptions".
The problem is that egcs 1.1.2 has its own crt*.o files and use them in
place of the FreeBSD one. By moving the files elsewhere, it works. I don't
know the effect on exceptions thoug
On Sat, 3 Apr 1999, David O'Brien wrote:
# > Just tried to compile apache and apache's jserv and got hit by the
# > above bug so I hope that this gets resolved prior to using egcs as the
# > default.
#
# I doubt it will.
Me too. :/
# I expect there will be significant breakage of non-world afte
> Just tried to compile apache and apache's jserv and got hit by the
> above bug so I hope that this gets resolved prior to using egcs as the
> default.
I doubt it will.
I expect there will be significant breakage of non-world after the
commit. I've significantly tested kernel and world, but I h
> andr...@titan{1001} $ xterm
> /usr/libexec/ld-elf.so.1: /usr/X11R6/lib/libXaw.so.6: Undefined symbol
> "__deregister_frame_info"
> Exit 1
>
> Is this a problem with egcs ? Or did I overlook something ?
Please recompile everything you did with the "-v" option, and send the
output. You may easi
Actually, it probably means that the program must be compiled with
"-fexecptions".
Here is a little clue:
from egcs-1.1.2:
./gcc/frame.c:/* Called from crtbegin.o to deregister the unwind info for an
object. */
./gcc/frame.c:__deregister_frame_info (void *begin)
./gcc/frame.c:__deregister_fr
David O'Brien forwarded me a message a couple of days ago that
contains a fix that may help. You need to add the following
line at line 301 in target.make
-u __deregister_frame_info \
-steve
On Sat, 3 Apr 1999, Andreas Klemm wrote:
# Got the latest egcs port
#
# # $Id: Makefile,v 1.53
Got the latest egcs port
# $Id: Makefile,v 1.53 1999/03/30 02:58:02 obrien Exp $
Build X11R6 with the following CFLAGS:
-pipe -mpentiumpro -O2
I'm still running X11 and after ,make install' I'm unable
to launch x applications (xterm, ...)
andr...@titan{1001} $ xterm
/usr/libexec/ld-elf
33 matches
Mail list logo
