Subject: continue after error code.
To: None <netbsd-help@netbsd.org>
From: Reinoud Koornstra <Reinoud.Koornstra@ibbnet.org>
List: netbsd-help
Date: 02/08/2000 04:00:32
Hi,

I have some corrupt hardware, i suspect my memory, therefore make build
stops always with error codes at several places.
Always with internal compiler error.
That's not a real problem. We can continue with make UPDATE= build after
that. However, i wonder over the following: When the process stopped with
an internal compiler error at a specific file, then that file isnt
compiled at all, of being compiled corrupted, what can i do to make sure
that everything including the file from there on i being compiled again?
Should i remove the .o file or .so or .po file of the .c file where make
build stopped or what should i do?
Or does make UPDATE= build takes care of this? I cant imagine it takes
care of it, if the file is corruptly compiled. So what is best to do in
that case? And even if you do the above procedure makeing sure the file
where make build stopped is being compiled again, i saw in the makefile
that make UPDATE= is not the same as a normal make build.
What would the difference exacly be?
Btw, are there any memory checking programs to test it in netbsd?
Bye,

Reinoud.