Re: Various build fixes Anthony Mulcahy (anthony@kcn.ne.jp)
Sun, 14 May 2000 02:54:32 +0900

Hello,

On Sat, May 13, 2000 at 11:45:11AM -0400, Jonathan S. Shapiro wrote:
> In regard to the various problems with "fixregs.h", I suspect that what is
> happening here is a bad file generation that is ending up in the tarball. I

The tarballs which I downloaded on May 4th will compile without doing any "make update" so they seem to be OK.

> Hmm. I would have done this differently. I'ld have untarred directly into
> /mo so as to avoid the redundant layer of "eros/eros", but this is fine. By
> the way, setting XENV to $EROS_ROOT/xenv is not necessary. It defaults to
> $EROS_ROOT/xenv

OK, I'll try to compile without setting XENV.

> > 4. I changed the following lines in
> > $EROS_ROOT/src/build/lib/make/makevars.mk,
> > because the cross compilation tools were not being called.
> If linux-xenv was properly included, this should be done automatically. If
> not, we need to figure out why it didn't work. Where were the cross tools
> not getting called?

I retried everything from scratch today and there was no need to modify makevars.mk so it must have been due to some mistake that I made the first time.

> I think that the floppy defaults to /dev/fd0H1440. You can change this by
> setting EROS_FD to /dev/fd0. Look at the common build rules in the test
> directory that is the parent of the directory where you were building.

Yes I discovered this. If I set EROS_FD to /dev/fd0, I can "make ztstflop" without any problems and I can then boot another machine with the disk, however the boot up process stops after the following lines:

Your cpu type is 5 (GenuineIntel)
Could not reserve log space for node
current thread 0x01092ee0 (Running) ctxt 0x01061590 (user)
rsrv=0x00105a300

uobj 0x00000018 cnt=0 0x0000000000001605 Stopped at 0x00105b14 0x105b14: movl %ebp,%esp kdb>_

If I type continue at the debugger prompt, it will run until it stops at a checkpoint and typing continue a second time appears to put it into an infinite loop. Is this behaviour correct? What does the message about not being able to reserve log space mean?

> If someone can answer the following stupid "make" question, I could make a
> lot of this simpler:

I'm afraid that I can't answer it :(

Best regards,

Anthony Mulcahy

-- 
Anthony Mulcahy     <anthony@kcn.ne.jp>     GPG KeyID 61CA8871
              http://seahorse.sourceforge.net