RE: building xfsdump...

["LA Walsh" <law@tlinx.org>]

Nep...seems to show less detail, last bit of lines:
define HAVE_STDLIB_H 1
#define HAVE_STRING_H 1
#define HAVE_MEMORY_H 1
#define HAVE_STRINGS_H 1
#define HAVE_INTTYPES_H 1
#define HAVE_STDINT_H 1
#define HAVE_UNISTD_H 1
#define HAVE_LIBUUID 1

configure: exit 1
---
	exit 1: ... I think the error message I'm getting seems to be
pointing the to the problem though the problem isn't verifiable via other
methods,
though I had problems with the curses lib back in SuSE 8.0 -- same symptom
when doing a make menuconfig (in kernel) -- curses couldn't be found.  
But with 8.1 it went away. (Checking...well kernel make menuconfig works with
curses linkage).  Hmmm...but menuconfig has a define 'CURSES_LOC="<ncurses.h>"

	Perhaps xfsdump needs to know to use ncurses rather than curses?
Maybe I shouldn't be using suse...:-)...nah...must be a redhat bug that it works
:-).


> -----Original Message-----
> From: Andi Kleen [mailto:ak@suse.de] 
> Sent: January 01, 2003 09:42p
> To: LA Walsh; linux-xfs@oss.sgi.com
> Subject: Re: building xfsdump...
> 
> 
> On Wed, Jan 01, 2003 at 09:36:55PM -0800, LA Walsh wrote:
> > 
> > minor problem with likely a real dumb error on my part in system 
> > configuration, but in trying to rebuild the rpm for xfsdump 
> on my SuSE 
> > system, I got an error I don't understand (w/o, perhaps an extended 
> > period of examination) and was hoping someone might 
> short-circuit my 
> > debugging of this issue:
> 
> Take a look at config.log in the build directory where it 
> failed. It usually shows you what went wrong in more detail 
> (compiled source + 
> error messages from the toolkit) 
> 
> -Andi
>