test to curr...@freebsd.org
(Just testing after hub was upgraded) To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
DES from source?
[posted to -current after no response from -questions] Hi! I am looking for the correct way of installing DES (crypt) from sources.
Error during compile EGCS
I made two steps in /usr/src/contrib/egsc # ./configure # make I have: gcc -DIN_GCC -g -O2 -DHAVE_CONFIG_H -I. -I. -I./config -DGCC_INCLUDE_DIR=\/usr/local/lib/gcc-lib/i386-unknown-freebsdelf4.0/egcs-2.91.66/include\ -DGPLUSPLUS_INCLUDE_DIR=\/usr/local/include/g++\ -DOLD_GPLUSPLUS_INCLUDE_DIR=\/usr/local/lib/g++-include\ -DLOCAL_INCLUDE_DIR=\/usr/local/include\ -DCROSS_INCLUDE_DIR=\/usr/local/i386-unknown-freebsdelf4.0/sys-include\ -DTOOL_INCLUDE_DIR=\/usr/local/i386-unknown-freebsdelf4.0/include\ -c `echo ./cccp.c | sed 's,^\./,,'` In file included from config/i386/xm-i386.h:43, from config.h:2, from cccp.c:21: tm.h:3: linux.h: No such file or directory tm.h:4: i386/freebsd-elf.h: No such file or directory *** Error code 1 Stop. *** Error code 1 Stop. What does it mean? REM To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: SMP users (important)
Alan Cox said: I've committed the basic infrastructure to improve TLB management on SMPs. Translation: this will lead to the elimination of a LOT of interprocessor interrupts to invalidate TLB entries. I'll be turning on the new mechanisms slowly so we can carefully debug each step and (hopefully) avoid any problems. (To the rest of the team, Alan and Luoqi already know my opinion.) I just wanted to chime in and say that the new patches are based on a really good concept, and is much cleaner than the previous method. Also, many RISC architectures can utilize this method due to the availability of lots of general registers. (One could go so far as to have the compiler reserve the register.) Non-threaded user mode apps could optionally use the reserved register, but for threaded user mode apps, that reserved register could also be used as a per-thread base pointer. I believe that NT does the above (%fs for X86, and general register for Alpha.) On PPC, there are several local, per-processor registers that one could use (but loading a general register with that per processor register would be needed for access.) Also, since the PPC has lots of registers, one could? permanently reserve one of the general registers (r13?). All in all, this change has the potential for better context switching time (and less memory/better performance for multi-threaded processes.) This is a serious, non-trivial movement in the *right* direction!!! :-). SMP users should be pleased with this movement (I certainly am!!!) -- John | Never try to teach a pig to sing, dy...@iquest.net | it makes one look stupid jdy...@nc.com | and it irritates the pig. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: UPDATE4: ATA/ATAPI driver new version available.
Ladavac Marino mlada...@metropolitan.at writes: [ML] Also, is there any swapping area on that slice? Because if there is and kernel has been told to use it (AFAIR swapon happens even in single user mode) Not unless you run it manually. you have just obliterated the kernel pages (kernel is pageable these days IIRC, at least the data if not the code). It's not, as far as I know. DES -- Dag-Erling Smorgrav - d...@flood.ping.uio.no To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: DES from source?
Anders Andersson wrote: I am looking for the correct way of installing DES (crypt) from sources. Nothing to do, except for... From the beginning I install most of my boxes from ftp and with the minimal option. After that I cvsup and do make world to fit my needs. On this test box I run 4.0-CURRENT and have cvsupped the: # The international secure collections. src-crypto src-eBones src-secure ...this. I plan to do 'make world' and from what I can tell I need to: ln -fs libdescrypt.so libcrypt.so ln -fs libdescrypt.so.2 libcrypt.so.2 ln -fs libdescrypt.a libcrypt.a after make world to use DES (crypt). This should happen automagically. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Headers changed?
Well, it goes like this: I cvsupped to CURRENT from 3.1 some time ago (like a month or something) and everything was going great. Friday night I cvsupped and tried to make world, but without success -- yacc complained during something in cc1. Anyhoo, I then successfully did a make world -DNOTOOLS, and the result is somewhat suboptimal, in that Hello world does not compile, and I can't make world at the moment. Are these changes related to the introduction of egcs? Any help gratefully received! (Including telling me if this is the wrong place to ask) gcc output follows. In file included from /usr/include/stdio.h:44, from hw.c:1: /usr/include/machine/ansi.h:103: syntax error before `__attribute__' /usr/include/machine/ansi.h:104: syntax error before `__attribute__' In file included from hw.c:1: /usr/include/stdio.h:55: syntax error before `fpos_t' gcc: Internal compiler error: program cc1 got fatal signal 11 -- [gjvc] To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: SMP users (important)
On Sat, 3 Apr 1999, John S. Dyson wrote: Alan Cox said: I've committed the basic infrastructure to improve TLB management on SMPs. Translation: this will lead to the elimination of a LOT of interprocessor interrupts to invalidate TLB entries. I'll be turning on the new mechanisms slowly so we can carefully debug each step and (hopefully) avoid any problems. (To the rest of the team, Alan and Luoqi already know my opinion.) I just wanted to chime in and say that the new patches are based on a really good concept, and is much cleaner than the previous method. Also, many RISC architectures can utilize this method due to the availability of lots of general registers. (One could go so far as to have the compiler reserve the register.) Non-threaded user mode apps could optionally use the reserved register, but for threaded user mode apps, that reserved register could also be used as a per-thread base pointer. I believe that NT does the above (%fs for X86, and general register for Alpha.) On PPC, there are several local, per-processor registers that one could use (but loading a general register with that per processor register would be needed for access.) Also, since the PPC has lots of registers, one could? permanently reserve one of the general registers (r13?). All in all, this change has the potential for better context switching time (and less memory/better performance for multi-threaded processes.) This is a serious, non-trivial movement in the *right* direction!!! :-). SMP users should be pleased with this movement (I certainly am!!!) The alpha palcode supports a per-thread unique value which can be used by any threading system (user or kernel). -- Doug Rabson Mail: d...@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: DES from source?
Hi Synker!
Anders Andersson and...@sanyusan.se writes:
I am looking for the correct way of installing DES (crypt) from sources.
*grumble* why do people keep wanting to install me? ;)
I plan to do 'make world' and from what I can tell I need to:
ln -fs libdescrypt.so libcrypt.so
ln -fs libdescrypt.so.2 libcrypt.so.2
ln -fs libdescrypt.a libcrypt.a
# cd /usr/src
# for f in libdescrypt* ; do ln -fs $f $(echo $f | sed s/des//) ; done
Do I need to change all passwd with 'passwd {user}' to use DES passwd crypt?
Existing MD5 passwords will still work. New users will get DES
passwords.
DES
--
Dag-Erling Smorgrav - d...@flood.ping.uio.no
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message
GNU regex (Was: egcs knob and objective C)
At 03:32 PM 4/2/99 -0600, Jacques Vidrine wrote: On 2 April 1999 at 22:25, Doug Rabson d...@nlsystems.com wrote: We should also consider installing libbfd. If and when we bring in a newer version of gdb, it would be a good idea to avoid importing yet another version of libiberty and libbfd. ... and GNU regex. If you mean a version of regex included in the LGPL'ed libc, yes, then this point might be mute. However, if you mean the regex/rx distributions, please, no. GNU regex and GNU rx distributions are both under the GPL. Henry Spencer's regex has a promiscious license. Even if a LGPL'ed distribution was available, I wouldn't recommend switching without a significant and demonstrated technical advantage. I've found that each implementation is even with the others. I would suggest GNU regex be made ports unless some base application required the -lgnuregex. Kurt To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
-Werrors in CFLAGS ?
Why is make world showing these just now ? cc -fpic -DPIC -g -pipe -DPERMIT_CONSOLE -D_SKEY_INTERNAL -I/src/src/lib/libskey -W -Wall -Werror -I/usr/obj/src/src/tmp/usr/include -c /src/src/lib/libskey/skey_getpass.c -o skey_getpass.So cc1: warnings being treated as errors /usr/obj/src/src/tmp/usr/include/stdio.h:354: warning: `__sputc' defined but not used cc1: warnings being treated as errors /usr/obj/src/src/tmp/usr/include/stdio.h:354: warning: `__sputc' defined but not used *** Error code 1 *** Error code 1 cc1: warnings being treated as errors /usr/obj/src/src/tmp/usr/include/stdio.h:354: warning: `__sputc' defined but not used *** Error code 1 I'm at cvs-cur #5203 made on 1999/04/02 16:24:18. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- robe...@keltia.freenix.fr FreeBSD keltia.freenix.fr 4.0-CURRENT #70: Sat Feb 27 09:43:08 CET 1999 To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
AWE broken by recent commits to i386/isa/sound files?
After a 'make world' last night, everytime I use any of the AWE utilities (as ported by Randall Hopper) I get this: AWE32: unsupported ioctl -1064546046 AWE32: unsupported ioctl -1064546046 I remember seeing a couple of commits to some of the files in sys/i386/isa/sound, but I don't remember exactly which files were changed... Is it possible that these changes broke AWE support? To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: GNU regex (Was: egcs knob and objective C)
On 3 April 1999 at 7:49, Kurt D. Zeilenga k...@openldap.org wrote: [snip] If you mean a version of regex included in the LGPL'ed libc, yes, then this point might be mute. However, if you mean the regex/rx distributions, please, no. We're talking about gdb, so I mean the GNU regex implementation that is distributed as part of gdb. [snip] I would suggest GNU regex be made ports unless some base application required the -lgnuregex. As much as I would like to see us shipping only one regex implementation, and a BSD-style licensed one at that, some base applications require GNU regex, notably those found under src/gnu. However, as we import new things (a new GDB, a new CVS) perhaps we can try to drop the regex implementations that come with those, and use one that is already in the system. Then again, perhaps not. No telling what subtle bugs could be created by changing the regex implementation used in complex applications such as CVS. Jacques Vidrine / n...@nectar.com / nec...@freebsd.org To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
X problems using egcs as compiler
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.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 ?
My freebsd 3.1-STABLE kernel, compiled with -pipe -O2 -mpentiumpro,
runs fine since half a day.
--
Andreas Klemm http://www.FreeBSD.ORG/~andreas
http://www.freebsd.org/~fsmp/SMP/SMP.html
powered by Symmetric MultiProcessor FreeBSD
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message
make world is broken ...
The make world (4.0-current) broke yesterday and after a day of cvsupping is still broke ... I can't send the output but it stopped in the libc I presume ... Please check... Happy Easter to everybody (also to whom broke world :-)) Thanks for attention Best Regards, Gianmarco Giovannelli , Unix expert since yesterday http://www.giovannelli.it/~gmarco http://www2.masternet.it To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: X problems using egcs as compiler
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 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.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 ?
#
# My freebsd 3.1-STABLE kernel, compiled with -pipe -O2 -mpentiumpro,
# runs fine since half a day.
#
# --
# Andreas Klemm http://www.FreeBSD.ORG/~andreas
# http://www.freebsd.org/~fsmp/SMP/SMP.html
# powered by Symmetric MultiProcessor FreeBSD
#
#
# To Unsubscribe: send mail to majord...@freebsd.org
# with unsubscribe freebsd-current in the body of the message
#
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message
CVS-all mailing list problems?
I know this is the -current list, but... I haven't received a single message on the cvs-all list since 11:57 GMT this morning, whilst a cvsup just gave me a loads of commits today... this does not seem to be a local issue, since I receive -current normally (or so it seems, at least). Any clues? PYD To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: X problems using egcs as compiler
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_frame (void *begin)
./gcc/frame.c: free (__deregister_frame_info (begin));
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.
Amancio
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 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.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 ?
#
# My freebsd 3.1-STABLE kernel, compiled with -pipe -O2 -mpentiumpro,
# runs fine since half a day.
#
# --
# Andreas Klemm http://www.FreeBSD.ORG/~andreas
# http://www.freebsd.org/~fsmp/SMP/SMP.html
# powered by Symmetric MultiProcessor FreeBSD
#
#
# To Unsubscribe: send mail to majord...@freebsd.org
# with unsubscribe freebsd-current in the body of the message
#
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message
Re: CVS-all mailing list problems?
On Sat, 3 Apr 1999, Pierre Y. Dampure wrote: I know this is the -current list, but... I haven't received a single message on the cvs-all list since 11:57 GMT this morning, whilst a cvsup just gave me a loads of commits today... this does not seem to be a local issue, since I receive -current normally (or so it seems, at least). Any clues? Yeah, heavy maint on hub last night, moving it to 3.1. Much breakage, not all made up for yet. They didn't go to sleep until it was in useable shape (nice guys) so let 'em sleep a little more before raising a ruckus. It'll come back. I'm waiting some repairs myself. PYD To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message +--- Chuck Robey | Interests include any kind of voice or data chu...@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run picnic (FreeBSD-current) (301) 220-2114 | and jaunt (Solaris7). +--- To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Error during compile EGCS
I made two steps in /usr/src/contrib/egsc # ./configure Don't do that - that isn't how egcs or anything else in /usr/src/contrib is supposed to be used and you appear to be fundamentally confused about the sources, so much so that I wouldn't suggest attempting to build anything from them until you've taken more time to study the build mechanism. - Jordan To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: X problems using egcs as compiler
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 haven't tried ports at all. People may be well advised to CVSup and `make world' (or don't CVSup again for a while) sometime before Sunday California PDT time (-7hrs Zulu). The rockiness of -CURRENT is about to be upon us. -- -- David(obr...@nuxi.com -or- obr...@freebsd.org) To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Headers changed?
Hello world does not compile, and I can't make world at the moment. Are these changes related to the introduction of egcs? No. No EGCS-only changes have been made to the base system yet. The somewhat EGCS-related change I've made so far fixed breakage in `make world' in that the wrong compiler was building libgcc.a. We were using the base compiler, rather than the one built in `make world'. -- -- David(obr...@nuxi.com -or- obr...@freebsd.org) To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: X problems using egcs as compiler
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 after the # commit. I've significantly tested kernel and world, but I haven't tried # ports at all. I got everything setup to build the entire ports collection and sometime during the night the big IDE disk that I keep all the distfiles and packages on went south. :( It had been acting funny lately. I think it finally decided it had seen enough. I'm off to the store to pick up another and then by work where I have a T1 to grab all the distfiles that are not on the 3.1 CDs. I sure hope Satoshi is following this because it doesn't look like I'm going to be able to get very far before the switch is thrown. In fact now is probably a good time to post something to the ports mailing list. I'll send out something brief before I head off to the store. # People may be well advised to CVSup and `make world' (or don't CVSup # again for a while) sometime before Sunday California PDT time (-7hrs # Zulu). # # The rockiness of -CURRENT is about to be upon us. Committers brush up on your edit-pr skills, we're in for a load of fun in the following weeks. -steve # -- # -- David(obr...@nuxi.com -or- obr...@freebsd.org) # To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: X problems using egcs as compiler
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 though. I tumbled in this problem when compiling Perl 5.005_03 with egcs and moving the files away solved the problem. I don't know what David plan to do with these crt*.o files. David ? -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- robe...@keltia.freenix.fr FreeBSD keltia.freenix.fr 4.0-CURRENT #70: Sat Feb 27 09:43:08 CET 1999 To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: X problems using egcs as compiler
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 elsewhere, it works. I don't know the effect on exceptions though. I tumbled in this problem when compiling Perl 5.005_03 with egcs and moving the files away solved the problem. I don't know what David plan to do with these crt*.o files. David ? 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 (like the egcs port forced you to do at one time, and probably still does). - alex To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: X problems using egcs as compiler
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/crtbegin.o -L.. /../exports/lib -L/usr/X11R6/lib -L/usr/local/lib/gcc-lib/i386-portbld-freebsd3. 1/egcs-2.91.66 -L/usr/local/i386-portbld-freebsd3.1/lib -L/usr/local/lib resize. o -lxpg4 -lrpcsvc -lkrb -ldes -lcrypt -ltermcap -rpath /usr/X11R6/lib -lgcc -lc -lgcc /usr/local/lib/gcc-lib/i386-portbld-freebsd3.1/egcs-2.91.66/crtend.o /usr/ lib/crtn.o Looking at the link line, I don't see anything wrong on 1st glance. -- -- David(obr...@nuxi.com -or- obr...@freebsd.org) To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: X problems using egcs as compiler
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 more stock EGCS) The base system will have many more of our hacks. 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 expect *any* problems with ports that use the C compiler. All the problems I think we might have are C++ compiler issues. -- -- David(obr...@nuxi.com -or- obr...@freebsd.org) To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: X problems using egcs as compiler
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
Re: X problems using egcs as compiler
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. Perhaps it is a good time to review the egcs docs with respect to frame handling and exception handling. Amancio 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 with these crt*.o files. David ? 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. -- -- David(obr...@nuxi.com -or- obr...@freebsd.org) To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: make world is hosed
- - Last section: Building elf libraries - - Last arrow: === libstdc++ - - Last 20 lines before first error: - - install -c -o root -g wheel -m 444 libreadline_p.a /usr/obj/usr/src/tmp/usr/lib install -c -o root -g wheel -m 444 libreadline.so.3 /usr/obj/usr/src/tmp/usr/lib ln -sf libreadline.so.3 /usr/obj/usr/src/tmp/usr/lib/libreadline.so === libreadline/doc === libreadline/doc/history === libreadline/doc/readline === libstdc++ ..snip.. cd /usr/src/gnu/usr.bin/cc/libgcc; /usr/obj/usr/src/tmp/usr/bin/make all; /usr/obj/usr/src/tmp/usr/bin/make -B install install -c -o root -g wheel -m 444 bsd.README bsd.dep.mk bsd.doc.mk bsd.docb.mk bsd.info.mk bsd.kern.mk bsd.kmod.mk bsd.lib.mk bsd.libnames.mk bsd.man.mk bsd.obj.mk bsd.own.mk bsd.port.mk bsd.port.post.mk bsd.port.pre.mk bsd.port.subdir.mk bsd.prog.mk bsd.sgml.mk bsd.subdir.mk sys.mk /usr/obj/usr/src/tmp/mk usage: install [-CcDps] [-f flags] [-g group] [-m mode] [-o owner] file1 file2 install [-CcDps] [-f flags] [-g group] [-m mode] [-o owner] file1 ... fileN directory install -d [-g group] [-m mode] [-o owner] directory ... *** Error code 64 Is anyone else experiencing this? -- -- David(obr...@nuxi.com -or- obr...@freebsd.org) To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: X problems using egcs as compiler
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 requires thread support for exception handling. Perhaps it is a good time to review the egcs docs with respect to frame handling and exception handling. How can I tell if I've got thread support enabled? I've used ksirc before which uses exceptions to parse irc output, and it's obviously not threaded (cause Qt isn't). Sure, I don't like ksirc, and I got some odd perl related errors, but it worked. - alex To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: make world is hosed
I did a cvsup and a make world around 8:00 PM last nite and went without a hitch . Amancio To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: make world is hosed
David O'Brien wrote: Is anyone else experiencing this? -- I did earlier on today; I removed /usr/src/gnu/usr.bin/cc/libgcc, and all went fine. It might in fact have been a consequence of one of your earlier commits (when you moved the Makefile to the Attic)? Best Regards, PYD To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: X problems using egcs as compiler
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 what we'd prove if the ports tree was built with an un-FreeBSD'd egcs. It might get us close, then again it might get us chasing (mis)features that aren't going to be present when it is the system compiler. I certainly would feel better about using the real thing. # 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 # expect *any* problems with ports that use the C compiler. All the # problems I think we might have are C++ compiler issues. See above. Can you send me a set of instructions for turning gcc off and egcs on in the base distribution? -steve # -- # -- David(obr...@nuxi.com -or- obr...@freebsd.org) # To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: X problems using egcs as compiler
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 schedule would collapse to less than half a day. - Jordan To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Switching to EGCS on Saturday (PST)
Better yet, can we just run with this today instead of tomorrow? I guess we could do it today. But there might be some that were planning on doing a final CVSup tonight, since the announcement was for Sunday. Opinions? -- -- David(obr...@nuxi.com -or- obr...@freebsd.org) To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: X problems using egcs as compiler
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- obr...@freebsd.org) To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: X problems using egcs as compiler
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 right, even better yet. Throw the switch already! :) -steve To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: X problems using egcs as compiler
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'. -- -- David(obr...@nuxi.com -or- obr...@freebsd.org) To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message Just did that... results in roughly 1 hour 1/2, ok? (unless it breaks, of course). PYD To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Switching to EGCS on Saturday (PST)
On Sat, 3 Apr 1999, David O'Brien wrote: # I guess we could do it today. # # But there might be some that were planning on doing a final CVSup # tonight, since the announcement was for Sunday. They can always CVSup the latest bits and 'cvs co -D...' if they are getting the repository. They can also do this with a 'date=...' line in their cvsup-supfile. Just note the date/time just before the switch is thrown and let's get this show on the road. # Opinions? Do it. # -- # -- David(obr...@nuxi.com -or- obr...@freebsd.org) To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Switching to EGCS on Saturday (PST)
No. Don't. Please stick to reported change times. 'cvs co -D' is a desperate last measure. On Sat, 3 Apr 1999, Steve Price wrote: On Sat, 3 Apr 1999, David O'Brien wrote: # I guess we could do it today. # # But there might be some that were planning on doing a final CVSup # tonight, since the announcement was for Sunday. They can always CVSup the latest bits and 'cvs co -D...' if they are getting the repository. They can also do this with a 'date=...' line in their cvsup-supfile. Just note the date/time just before the switch is thrown and let's get this show on the road. # Opinions? Do it. # -- # -- David(obr...@nuxi.com -or- obr...@freebsd.org) To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Switching to EGCS on Saturday (PST)
On Sat, 3 Apr 1999, David O'Brien wrote:
Better yet, can we just run with this today instead of tomorrow?
I guess we could do it today.
But there might be some that were planning on doing a final CVSup
tonight, since the announcement was for Sunday.
Opinions?
Its -CURRENT ... go for it. As soon as I see the announcement go out,
I'll be one of those upgrading to it, I've been looking forward to seeing
EGCS integrated for a long time now :)
Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: scra...@hub.org secondary: scra...@{freebsd|postgresql}.org
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message
Re: X problems using egcs as compiler
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 should be back before it finishes. It usually only takes a little over an hour to do a 'make world' from scratch on my box at work. I'll let you know when it gets done. # My machines are either EGCS'ified, 3.1-CURRENT, or take 5 hours to `make # world'. # # -- # -- David(obr...@nuxi.com -or- obr...@freebsd.org) # To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: X problems using egcs as compiler
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 world'. -- -- David(obr...@nuxi.com -or- obr...@freebsd.org) To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message I started a Make world about 1 hour ago with current as of then sources. It should be done in about 30min's. The only thing is I don't build xntpd but every thing else is built. I'll post when completed Manfred = ||man...@pacbell.net || ||Ph. (415) 681-6235|| = To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Switching to EGCS on Saturday (PST)
On Sat, 3 Apr 1999, Matthew Jacob wrote: # # # No. Don't. Please stick to reported change times. 'cvs co -D' is a # desperate last measure. Something that someone playing with bleeding edge bits should be willing to do, IMHO. # # On Sat, 3 Apr 1999, Steve Price wrote: # # On Sat, 3 Apr 1999, David O'Brien wrote: # # # I guess we could do it today. # # # # But there might be some that were planning on doing a final CVSup # # tonight, since the announcement was for Sunday. # # They can always CVSup the latest bits and 'cvs co -D...' if they # are getting the repository. They can also do this with a 'date=...' # line in their cvsup-supfile. Just note the date/time just before # the switch is thrown and let's get this show on the road. # # # Opinions? # # Do it. # # # -- # # -- David(obr...@nuxi.com -or- obr...@freebsd.org) To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Switching to EGCS on Saturday (PST)
We could also tag the repository... would that be better? No. Don't. Please stick to reported change times. 'cvs co -D' is a desperate last measure. They can always CVSup the latest bits and 'cvs co -D...' if they are getting the repository. They can also do this with a 'date=...' line in their cvsup-supfile. Just note the date/time just before the switch is thrown and let's get this show on the road. -- -- David(obr...@nuxi.com -or- obr...@freebsd.org) To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Switching to EGCS on Saturday (PST)
On Sat, 3 Apr 1999, Matthew Jacob wrote: # # # No. Don't. Please stick to reported change times. 'cvs co -D' is a # desperate last measure. Something that someone playing with bleeding edge bits should be willing to do, IMHO. That's ridiculous. There's substantial work ongoing in 4.0 with enough people involved that changing things around for the hell of it and not sticking to broadcast times is just plain stupid. It's called 'dufus engineering', or 'freshman humour' or some such. Just because it's so-called 'bleeding edge' doesn't mean you can just integrate any old crap and just say well- it's bleeding edge. Harumph. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Switching to EGCS on Saturday (PST)
For a major change like using a different compiler- seems like A Good Idea(tm). On Sat, 3 Apr 1999, David O'Brien wrote: We could also tag the repository... would that be better? No. Don't. Please stick to reported change times. 'cvs co -D' is a desperate last measure. They can always CVSup the latest bits and 'cvs co -D...' if they are getting the repository. They can also do this with a 'date=...' line in their cvsup-supfile. Just note the date/time just before the switch is thrown and let's get this show on the road. -- -- David(obr...@nuxi.com -or- obr...@freebsd.org) To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: netscape: no recognized font
They went away after I nuked all prior traces of Navigator, including my .netscape directory (you should rename it :-) that was it. i cleaned out much of .netscrape and it worked fine. thanks. randy To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Switching to EGCS on Saturday (PST)
On Sat, 3 Apr 1999, Matthew Jacob wrote: # Something that someone playing with bleeding edge bits should # be willing to do, IMHO. # # That's ridiculous. There's substantial work ongoing in 4.0 with enough # people involved that changing things around for the hell of it and not # sticking to broadcast times is just plain stupid. It's called 'dufus # engineering', or 'freshman humour' or some such. Just because it's # so-called 'bleeding edge' doesn't mean you can just integrate any old crap # and just say well- it's bleeding edge. Harumph. We are not changing it for the hell of it. From what I gather David already has things ready and is just waiting for Sunday to come to commit the changes. Committing them now gives much of the people who will work to fix things that get broken a whole day more this weekend to work on them. This isn't 'dufus engineering' it is called advancing the state-of-the-art. It has been a long time coming and needs to be done, sooner than later. Just because the compiler changes doesn't mean development on the 4.0 branch have to stop. We need to get this change in the hands of as many people as we can so that we can work out any remaining hitches. Waiting another 24 hours == wasting another 24 hours, IMHO. -steve To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
crypt algorithms (was Re: DES from source?)
On Sat, Apr 03, 1999 at 05:34:06PM +0200, a little birdie told me
that Dag-Erling Smorgrav remarked
Do I need to change all passwd with 'passwd {user}' to use DES passwd crypt?
Existing MD5 passwords will still work. New users will get DES
passwords.
Did we ever hash out a mechanism to do this the other way (or integrate
new algorithms) and set 'try' vs. 'use' algorithms? I'm unclear as to
whether PAM is supposed to/capable of addressing this.
---
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
| Matthew Fuller http://www.over-yonder.net/ |
* fulle...@futuresouth.com fulle...@over-yonder.net *
| UNIX Systems Administrator Specializing in FreeBSD |
* FutureSouth Communications ISPHelp ISP Consulting *
| The only reason I'm burning my candle at both ends, |
*is because I haven't figured out how to light the*
| middle yet |
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message
Re: Fatal trap 1: privileged instruction fault while in kernel mode
On Sunday, 4 April 1999 at 1:57:50 +1000, Stephen McKay wrote: I've just got what seems an unlikely panic. How could I get a privileged instruction fault while in kernel mode? Sounds like a hardware (processor) problem to me. What was the instruction it was trying to execute? Greg -- See complete headers for address, home page and phone numbers finger g...@lemis.com for PGP public key To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Switching to EGCS on Saturday (PST)
On Sat, 3 Apr 1999, Matthew Jacob wrote: # Something that someone playing with bleeding edge bits should # be willing to do, IMHO. # # That's ridiculous. There's substantial work ongoing in 4.0 with enough # people involved that changing things around for the hell of it and not # sticking to broadcast times is just plain stupid. It's called 'dufus # engineering', or 'freshman humour' or some such. Just because it's # so-called 'bleeding edge' doesn't mean you can just integrate any old crap # and just say well- it's bleeding edge. Harumph. Sorry- let me apologize for bad tone. Bad day for me. We are not changing it for the hell of it. From what I gather David already has things ready and is just waiting for Sunday to come to commit the changes. Committing them now gives much of the people who will work to fix things that get broken a whole day more this weekend to work on them. This isn't 'dufus engineering' it is called advancing the state-of-the-art. It has been a long time coming and needs to be done, sooner than later. Just because the compiler changes doesn't mean development on the 4.0 branch have to stop. We need to get this change in the hands of as many people as we can so that we can work out any remaining hitches. Waiting another 24 hours == wasting another 24 hours, IMHO. I suppose. It's also fair to state that sticking to stated plans is good too. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Switching to EGCS on Saturday (PST)
On Sat, 3 Apr 1999, Steve Price wrote: On Sat, 3 Apr 1999, Matthew Jacob wrote: # Something that someone playing with bleeding edge bits should # be willing to do, IMHO. # # That's ridiculous. There's substantial work ongoing in 4.0 with enough # people involved that changing things around for the hell of it and not # sticking to broadcast times is just plain stupid. It's called 'dufus # engineering', or 'freshman humour' or some such. Just because it's # so-called 'bleeding edge' doesn't mean you can just integrate any old crap # and just say well- it's bleeding edge. Harumph. We are not changing it for the hell of it. From what I gather David already has things ready and is just waiting for Sunday to come to commit the changes. Committing them now gives much of the people who will work to fix things that get broken a whole day more this weekend to work on them. This isn't 'dufus engineering' it is called advancing the state-of-the-art. It has been a long time coming and needs to be done, sooner than later. Just because the compiler changes doesn't mean development on the 4.0 branch have to stop. We need to get this change in the hands of as many people as we can so that we can work out any remaining hitches. Waiting another 24 hours == wasting another 24 hours, IMHO. I don't like to disagree with you, Matthew, but the cvsup line to get what you need is pretty simple. This thing needs to get tested, asap, and the weekend is a better time for it. Your argument is basically do what you said ... the rest, likening it to freshman antics, is emotionalism. We have a good reason to push ahead here, and an easy recovery path. Some folks might get surprised, but that seems like a small thing, actually, because nearly all of them are reading this. +--- Chuck Robey | Interests include any kind of voice or data chu...@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run picnic (FreeBSD-current) (301) 220-2114 | and jaunt (Solaris7). +--- To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Switching to EGCS on Saturday (PST)
Just because the compiler changes doesn't mean development on the 4.0 branch have to stop. We need to get this change in the hands of as many people as we can so that we can work out any remaining hitches. Waiting another 24 hours == wasting another 24 hours, IMHO. I don't like to disagree with you, Matthew, but the cvsup line to get what you need is pretty simple. This thing needs to get tested, asap, and the weekend is a better time for it. Your argument is basically do what you said ... the rest, likening it to freshman antics, is emotionalism. We have a good reason to push ahead here, and an easy recovery path. Some folks might get surprised, but that seems like a small thing, actually, because nearly all of them are reading this. Yeah, yeah, yeah, yeah I'm a grumpy idiot...sorry... To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: X problems using egcs as compiler
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. PYD To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: X problems using egcs as compiler
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
Re: X problems using egcs as compiler
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 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- obr...@freebsd.org) To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Switching to EGCS on Saturday (PST)
-current comes without any warranties whatsoever. I say just pull the switch! :) Better yet, can we just run with this today instead of tomorrow? I guess we could do it today. But there might be some that were planning on doing a final CVSup tonight, since the announcement was for Sunday. Opinions? -- -- David(obr...@nuxi.com -or- obr...@freebsd.org) To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Switching to EGCS on Saturday (PST)
It's really not necessary given that -D gives us the same functionality. It's also hardly a desperation measure to use a commonly available feature of CVS, especially not when one is already crazed enough to track -current in the first place. - Jordan We could also tag the repository... would that be better? No. Don't. Please stick to reported change times. 'cvs co -D' is a desperate last measure. They can always CVSup the latest bits and 'cvs co -D...' if they are getting the repository. They can also do this with a 'date=...' line in their cvsup-supfile. Just note the date/time just before the switch is thrown and let's get this show on the road. -- -- David(obr...@nuxi.com -or- obr...@freebsd.org) To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Switching to EGCS on Saturday (PST)
Dude, we're talking about advancing by a day an event which is already seriously late anyway. The end of the world isn't going to come out of this and, even if it were, 24 more hours to live wouldn't make the slightest bit of difference to you anyway. I think you just need to chill out and let -current do what it needs to do. It's more important for us to get testing started than it is for us to safeguard your box and if zero risk is what you seek, don't run -current at all. Enough said - this isn't even worth arguing about. - Jordan To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Switching to EGCS on Saturday (PST)
It's already Sunday GMT. That it is. Well then that is good enough for me. (although Zulu time sounds more cool to me). I just upgraded my main EGCS development machine to the March 31st CURRENT snapshot and am doing a `make buildworld' to ensure things are ready go to. I will be gone from 7pm-10pm Saturday PST. Destroying^H^H^H^Hupgrading the compiler will commence after that time. -- -- David(obr...@nuxi.com -or- obr...@freebsd.org) To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Switching to EGCS on Saturday (PST)
alright alright! On Sat, 3 Apr 1999, Jordan K. Hubbard wrote: Dude, we're talking about advancing by a day an event which is already seriously late anyway. The end of the world isn't going to come out of this and, even if it were, 24 more hours to live wouldn't make the slightest bit of difference to you anyway. I think you just need to chill out and let -current do what it needs to do. It's more important for us to get testing started than it is for us to safeguard your box and if zero risk is what you seek, don't run -current at all. Enough said - this isn't even worth arguing about. - Jordan To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: X problems using egcs as compiler
-Original Message- From: David O'Brien obr...@nuxi.com To: Jordan K. Hubbard j...@zippy.cdrom.com; Steve Price spr...@hiwaay.net Cc: curr...@freebsd.org 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 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'. Done. cvsupped at 19:48 EST from cvsup2.freebsd.org buildworld with stock make.conf just finished without any problems. I'd say go for it :) Steph --- Stephane E. Potvin Galea Network Security To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: X problems using egcs as compiler
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 (0118) 977 4017 international code +44 118 r...@gid.co.ukfax (0118) 989 4254 between 0800 and 1800 UK To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: X problems using egcs as compiler
cvsup around 17:30 PST -- elf make world started on Sat Apr 3 17:33:29 PST 1999 -- -- elf make world completed on Sat Apr 3 18:33:39 PST 1999 -- Amancio To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: X problems using egcs as compiler
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 - The Feynman problem-solving algorithm: 1. Write down the problem 2. Think real hard 3. Write down the solution To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
show stopper for EGCS import
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 with libgcc. 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. I'm working on fixing this problem now. Sorry to have the import delayed. -- -- David(obr...@nuxi.com -or- obr...@freebsd.org) To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Fatal trap 1: privileged instruction fault while in kernel mode
On Sunday, 4 April 1999 at 15:09:48 +1000, Stephen McKay wrote: On Sunday, 4th April 1999, Greg Lehey wrote: On Sunday, 4 April 1999 at 1:57:50 +1000, Stephen McKay wrote: I've just got what seems an unlikely panic. How could I get a privileged instruction fault while in kernel mode? Sounds like a hardware (processor) problem to me. What was the instruction it was trying to execute? You were distracted by the large amount of extraneous fluff. ;-) Oops. I wrote: The fatal instruction is: 0xc016abc9 vclean+269:movl $0xc023355c,0xffdc(%ebp) which looks pretty ordinary. Certainly not a privileged instruction. If the processor gets a privileged instruction fault on this one, I would say it's wrong. What sort of hardware error happens once in 3 months? This one. I often hammer it. It has done long tape operations before too. I don't want to believe it is hardware yet. I'd say the truth is staring you in the face. Don't come too close, it might grab you. I was hoping somebody knew the precise conditions that could produce this trap. I'd guess that you'll never see exactly this trap again. But I do recall seeing some other similar ones. I think I'll have to cruise the Intel web site and download some big pdfs. Well, at least you'll learn something, but I don't expect you to find the solution to your problem there. Could it be heat? If it's hot, yes. Greg -- When replying to this message, please copy the original recipients. For more information, see http://www.lemis.com/questions.html See complete headers for address, home page and phone numbers finger g...@lemis.com for PGP public key To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
contrib/egcs
Hi! I have noticed that egcs-1.1.2 made it into /usr/src/contrib. But 'make buildworld' does not touch it. What is the intended use of egcs? Thanks -Bernd To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
