Return to BSD News archive
Newsgroups: comp.unix.bsd.freebsd.misc
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!simtel!swidir.switch.ch!scsing.switch.ch!news.belwue.de!news.uni-stuttgart.de!uni-regensburg.de!fauern!news.tu-chemnitz.de!irz401!theatre.pandora.sax.de!mw
From: mw@theatre.pandora.sax.de (Martin Welk)
Subject: Re: parse error before <somchar>
Organization: Private Site, Member of Individual Network e. V.
Message-ID: <DDC82J.9EE@theatre.pandora.sax.de>
References: <ortegaDDAnFr.FHt@netcom.com>
Date: Tue, 15 Aug 1995 05:47:07 GMT
Lines: 53
In article <ortegaDDAnFr.FHt@netcom.com>,
John Ortega <ortega@netcom.com> wrote:
>On three machince (8 to 12 MB memory) if have had this problem on many
>packages, including the kernel files:
>
>1. start make of some package
>2. make fails with a parse error from gcc
>3. start make, usually gcc will do a few more files
>4. go to 2
>
>Often, restarting make enough times will get you through, but on some
>things it just can't finish.
>
>This never happens on the machines with 16 or 32 megs of memory. Has
>anyone else had this problem? Also, the parse error often happens on some
>char that isn't in the file in question, like 0177.
I have an 8 MB machine (486DX2-66, Soyo motherboard, Adaptec 1542B SCSI host
adapter and more) and I have similar problems. I experienced them on my
old 386DX-40 board, too: some files seem to be defective sometimes.
It's hard for me to build a new kernel with the generic kernel on the
install disk: I had to create one on another machine (with 16 MByte,
running with no problems) and with that I can build a kernel here, too.
I have a Seagate ST41200N SCSI disk (about 1 GByte) and the problems
appear only with this drive: when I move /usr/src to /usr2 (which was
a Maxtor 245 MByte disk before and is now a Fujitsu 520 MByte disk) it
works without problems. But I don't have disk errors: everything works
fine, even swapping on that disk.
But every night my CNews active file (/usr/local/lib/news/active) gets
corrupted: one special line is defective every night. I moved active
to active.corrupt and copied it to active to move it to another place
on the disk. I correct it every day. But every night it happens again.
And I can't find out what it is :-( This behaviour is independent from
what else is running, for example X server, some clients and so on.
This happened under 2.0, some SNAPs after that and 2.0.5R.
If anyone has an idea what this is or could help me finding it out,
drop me a note. I can even make my machine accessible via The Net (tm)
when opening a SLIP connection. If anybody wants to come over here to
find it out, I can also offer bed & breakfast... :-)
Bye,
Martin
--
/| /| | /| / \ ,,You know, there's a lot of opportunities,
/ |/ | artin |/ |/ elk \ if you're knowing to take them,
\ you know, there's a lot of opportunities,
mw@pandora.sax.de \ if there aren't you can make them,
Meissen, Germany, Europe \ make or break them!'' (Tennant/Lowe)