Date: Thu, 17 Jul 1997 16:41:26 -0700 (PDT) From: Simon Shapiro <Shimon@i-Connect.Net> To: Michael Smith <msmith@atrad.adelaide.edu.au> Cc: freebsd-current@FreeBSD.ORG Subject: Re: Errors (?) in building -current Message-ID: <XFMail.970717212105.Shimon@i-Connect.Net> In-Reply-To: <199707170239.MAA26911@genesis.atrad.adelaide.edu.au>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi Michael Smith; On 17-Jul-97 you wrote: > Simon Shapiro stands accused of saying: > [Charset iso-8859-8 unsupported, filtering to ASCII...] > > Hi Y'all! > > > > I encounter these when building current as of lastnight: > > Um, are you building on an SMP machine, or with some degree of > parallelism enabled? One of the machines is SMP, both are running UP kernel (one is 2.2 one is -current. > > ===> lkm/syscons/fade > > install -c -o bin -g bin -m 555 fade_saver_mod.o /lkm > > fcns.c:49: initializer element for `el_func[88]' is not constant > > fcns.c:49: `vi_zero' undeclared here (not in a function) > > fcns.c:49: initializer element for `el_func[89]' is not constant > > In file included from editline.c:21: > > /usr/src/3.0/src/lib/libedit/vi.c:674: warning: type mismatch with > previous > > impl > > icit declaration > > /usr/src/3.0/src/lib/libedit/common.c:114: warning: previous implicit > > declaratio > > n of `vi_command_mode' > > /usr/src/3.0/src/lib/libedit/vi.c:674: warning: `vi_command_mode' was > > previously > > implicitly declared to return `int' > > /usr/src/3.0/src/lib/libedit/vi.c:674: warning: `vi_command_mode' was > > declared i > > mplicitly `extern' and later `static' > > *** Error code 1 (continuing) > > Care to tell me what is actually trying to compile fcns.c immediately > after > _installing_ the syscons fader LKM? I am really dumb when it cones to gigantic makes. I cd;make world;email failure :-) > > From _my_ -current build last night, fresh CVSup, cvs co -Pd : I always do (was told to) do cvs update, not cvs checkout. Does that make a difference? I went as far as removing the entire CVS tree (helped some), removing all of /usr/obj (helped some others) and removing all of /usr/src (helped none). This is what I am left with. Looks to me that I am not intelligent enough for this process. I seem to have endless problems with it. It works well for several weeks than it stops. Somehow it is always something I supposedly have done that is really stupid. One day I will figure it out. ... > You appear to have disk or memory corruption problems. common.h is > automatically generated during the build (eep, this is Bad), and > should look like : > > /* Automatically generated file, do not edit */ > #ifndef _h_common_c > #define _h_common_c > protected el_action_t ed_end_of_file __P((EditLine *, int)); > protected el_action_t ed_insert __P((EditLine *, int)); > protected el_action_t ed_delete_prev_word __P((EditLine *, int)); Two separate machines? Both having the same corrupted memory? Four different kernels? I have limited experience in this but find it hard to accept. I did witness through the years, CVS cause more heartburn than its worth. Typically the answer is the M$ standard: re-install. One day you may agree to help me develop an RDBMS based revision and release control system. First we have to have an RDBMS that actually works for less than 50,000 dollars and available in source. Simon
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?XFMail.970717212105.Shimon>