public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen.net>
To: Martin Steigerwald <Martin@lichtvoll.de>
Cc: linux-xfs@oss.sgi.com
Subject: Re: xfs-cmds doesn't build... (cvs & 2.9.2...)
Date: Sat, 21 Jul 2007 15:53:04 -0500	[thread overview]
Message-ID: <46A27230.2060908@sandeen.net> (raw)
In-Reply-To: <200707212141.10101.Martin@lichtvoll.de>

Martin Steigerwald wrote:
> Am Samstag 21 Juli 2007 schrieb Eric Sandeen:
>> cvs:
>>
>> [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.
>> 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
> 
> Hi Eric,
> 
> did work here a bit before Sa 21. Jul 21:40:50 CEST 2007.
> 
> Regards,

Yep, if I cd into xfs-cmds it's ok.  Looks like just "make" from the top
dir is busted.  (the tarball *is* busted too, missing a header file)

thanks,

-eric

  reply	other threads:[~2007-07-21 20:53 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 [this message]
2007-07-23  3:22 ` Nathan Scott
2007-07-23 13:52   ` Eric Sandeen

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=46A27230.2060908@sandeen.net \
    --to=sandeen@sandeen.net \
    --cc=Martin@lichtvoll.de \
    --cc=linux-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox