Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!elroy.jpl.nasa.gov!decwrl!usenet.coe.montana.edu!bsd.coe.montana.edu!nate From: nate@bsd.coe.montana.edu (Nate Williams) Newsgroups: comp.os.386bsd.questions Subject: Re: FreeBSD upgrade... Date: 13 Oct 1993 17:35:10 GMT Organization: Montana State University, Bozeman MT Lines: 88 Message-ID: <29he8e$7th@pdq.coe.montana.edu> References: <haley.750498537@husc8> NNTP-Posting-Host: bsd.coe.montana.edu Keywords: libgnumalloc, npx.c, 3btol, ??? In article <haley.750498537@husc8>, Elizabeth Haley <haley@husc8.harvard.edu> wrote: >O.K. So I attempt the installation via the update script... > >Problems: >1. update is the name of a utility on the PATH. > solution: run ./update to force the issue... Still, it's >namespace pollution. Made more clear in the README as of a few days ago. >2. Failure to complete make of gcc1 due to absence of libgnumalloc. >??? Was This SUPPOSED to be there??? I was never informed. I was >previously running 386bsd-0.1 + pk 0.2.4. > > solution: find and install same... Mayhap need to make sure >this is compiled and installed FIRST. Fixed in the most recent version as of 15 minutes ago. My fault. >3. O.K. So at this point I have hacked off the front part of the >update script to prevent it from doing things over again. >Everything runs vaguely O.K. Though I have to terminate it and "fg" to >get it to break a lockup at one point. I have no idea of the effects >of this. I suspect that the above 'lockup' is the cause of the rest of your troubles. Either that, or the gcc2 stuff failed. > It is during the (re) compilation of gcc, but I happen to >already have gcc compiled in /usr/local, so I forge ahead. Until we >hit making the kernel. The gcc is /usr/local will probably not work, due to the changes in the gcc2 we've done. As a matter of fact, I would suspect that most of your troubles are due to that gcc being in the path, since the FreeBSD gcc2 assumes that gcc2 is OUR port of gcc2, especially when making the support libraries. [ configure and compile kernel ] >The weird failure comes at npx.c. ... >It can't find a few symbols, one of which is _3btol, and it's apparent >nemesis _lto3b. ... >Note that the npx.c file failed under both the gcc2 produced by the >upgrade, and the gcc2 that I made in /usr/local, which has not shown >signs of problems before. They both fail the exact same way... ... The source tree we have relies on the gcc2 we've made, and I suspect highly that the gcc2 in FreeBSD has less bugs than your version in /usr/local. What to do now? 1) Install the gcc1_bin.tgz package from freefall to get a know working compiler back on your system. 2) Rename /usr/local/bin/gcc to something other than gcc, and for good measure rename /usr/bin/gcc to /usr/bin/gcc-bad 3) make a symbolic link from the now installed gcc1 cc driver to gcc # ln -s /usr/bin/cc /usr/bin/gcc 4) Compile and install the gcc2 that is distributed with FreeBSD # cd /usr/src/gnu/gcc2 # make # make install [ Before doing ANYTHING else, you must to the below. These commands are important to get a working compiler with the correct support routines. ] # cd /usr/src/gnu/gcc2/libgcc # make clean # make # make install >So then my question is, do I want to try again with FreeBSD, go to >NetBSD, or maybe try Linux? No need to re-install, just get a working compiler setup. Nate -- nate@bsd.coe.montana.edu | Freely available *nix clones benefit everyone, nate@cs.montana.edu | so let's not compete with each other, let's work #: (406) 994-4836 | compete with folks who try to tie us down to home #: (406) 586-0579 | proprietary O.S.'s (Microsloth) - Me