From: Eric Sandeen <sandeen@sandeen.net>
To: nscott@aconex.com
Cc: xfs-oss <xfs@oss.sgi.com>, Barry Naujok <bnaujok@sgi.com>
Subject: Re: xfs-cmds doesn't build... (cvs & 2.9.2...)
Date: Mon, 23 Jul 2007 08:52:42 -0500 [thread overview]
Message-ID: <46A4B2AA.7030304@sandeen.net> (raw)
In-Reply-To: <1185160946.10702.12.camel@edge.yarra.acx>
Nathan Scott wrote:
> On Sat, 2007-07-21 at 10:05 -0500, Eric Sandeen wrote:
>>
>> [sandeen@sandeen xfs-cmds]$ make
>> ....
>> == Building xfsprogs
>> == clean, log is Logs/clean
>> make: *** [cmds] Error 1
>> [sandeen@sandeen xfs-cmds]$ cat xfsprogs/Logs/clean
>> make[1]: Entering directory `/src/cvs/xfs-cmds/xfsprogs'
>> === include ===
>> gmake[2]: *** No rule to make target `mdrestore'. Stop.
>
> Did you use -d on your cvs update line? My cvs update found it ok.
Ugh... that's probably it. *grumble*
>> make[1]: *** [mdrestore] Error 2
>> make[1]: Leaving directory `/src/cvs/xfs-cmds/xfsprogs'
>> [sandeen@sandeen xfs-cmds]$ grep -B1 mdrestore xfsprogs/Makefile
>> SUBDIRS = include libxfs libxlog libxcmd libhandle libdisk \
>> copy db fsck growfs io logprint mkfs quota mdrestore repair
>> rtcp \
>> [sandeen@sandeen xfs-cmds]$ ls xfsprogs/mdrestore
>> ls: xfsprogs/mdrestore: No such file or directory
>>
>
> On Sat, 2007-07-21 at 10:05 -0500, Eric Sandeen wrote:
>>
>> 2.9.2 tarball:
>> [sandeen@sandeen xfsprogs-2.9.2]$ make
>> ....
>> metadump.c:28:26: xfs_metadump.h: No such file or directory
>>
>
> This should be fixed now (with Barrys last change).
Ok, cool.
Thanks!
-Eric
> cheers.
>
> --
> Nathan
>
prev parent reply other threads:[~2007-07-23 13:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-21 15:05 xfs-cmds doesn't build... (cvs & 2.9.2...) Eric Sandeen
2007-07-21 19:41 ` Martin Steigerwald
2007-07-21 20:53 ` Eric Sandeen
2007-07-23 3:22 ` Nathan Scott
2007-07-23 13:52 ` Eric Sandeen [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=46A4B2AA.7030304@sandeen.net \
--to=sandeen@sandeen.net \
--cc=bnaujok@sgi.com \
--cc=nscott@aconex.com \
--cc=xfs@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.