xfs
[Top] [All Lists]

Re: make on xfs commands..

To: Trevor Hurst <trev@xxxxxxx>
Subject: Re: make on xfs commands..
From: "Nathan Scott" <nathans@xxxxxxxxxxxxxxxxxxxxxxxx>
Date: Fri, 7 Jul 2000 08:20:37 -0500
Cc: linux-xfs@xxxxxxxxxxx
In-reply-to: Trevor Hurst <trev@xxxxxxx> "Re: make on xfs commands.." (Jul 7, 8:01am)
References: <3963A20A.7DAD6487@xxxxxxx> <3964F00B.C71393FE@xxxxxxxxxxx> <10007070745.ZM21335@xxxxxxxxxxxxxxxxxxxxxxxx> <396500EB.C4D9A6FE@xxxxxxx>
Sender: owner-linux-xfs@xxxxxxxxxxx
hi,

On Jul 7,  8:01am, Trevor Hurst wrote:
> Subject: Re: make on xfs commands..
> > 
> > these #defines come from maxtrres.h which should exist in
> > your cmd/xfs/mkfs directory at the time you're building xfs_mkfs.c
> > - maxtrres.h is generated using cmd/xfs/maxtrres/xfs_maxtrres,
> > so I guess you'd see these errors if that header hadn't been
> > generated or if you didn't have the #include "maxtrres.h" line at
> > the top of xfs_mkfs.c ... does the header exist?
> > 
> 
>  Ah... Yes, it does, however, I think the problem is
> that it is of 0 byte length.. uggh.. Looks like I will wipe

yes, that would be a big problem.

> out the tree and pull down a fresh one and try again. Not sure
> how the header file got to be empty, does this seem strange?

I could see how it might have happened if the maxtrres subdir
hadn't been descended & built before the mkfs directory (the
shell redirect in the mkfs Makefile would have created the empty
file) - though I would also have expected a "command not found"
error in the mkfs build when attempting to run "xfs_maxtrres" (?)


cheers.

-- 
Nathan

<Prev in Thread] Current Thread [Next in Thread>