From: Eric Sandeen <sandeen@sandeen.net>
To: "Raz Ben-Jehuda(caro)" <raziebe@gmail.com>
Cc: linux-xfs@oss.sgi.com
Subject: Re: building xfstests
Date: Tue, 05 Jun 2007 10:07:03 -0500 [thread overview]
Message-ID: <46657C17.1090105@sandeen.net> (raw)
In-Reply-To: <5d96567b0706050749o74bc7701g154e836c43a511be@mail.gmail.com>
Raz Ben-Jehuda(caro) wrote:
> Hello
> I have downloaded from the web the cvs repository of the
> module xfs-cmds.
>
> I failing to build it. the bellow is the "make" output.
...
> Wrote:
> /d1/rt/raz/downloads/xfs-cmds/xfsdump/build/xfsdump-2.2.45.src.tar.gz
> Wrote:
> /d1/rt/raz/downloads/xfs-cmds/xfsdump/build/tar/xfsdump-2.2.45.tar.gz
So, everything built - but it just did not build rpms - which is maybe
fine with you?
> for d in attr acl xfsprogs dmapi xfsdump; do \
> ( cd /d1/rt/raz/downloads/xfs-cmds && /bin/cp
> $d/build/rpm/*.src.rpm /d1/rt/raz/downloads/xfs-cmds/SRPMS ) \
> done
> /bin/cp: cannot stat `attr/build/rpm/*.src.rpm': No such file or directory
> /bin/cp: cannot stat `acl/build/rpm/*.src.rpm': No such file or directory
> /bin/cp: cannot stat `xfsprogs/build/rpm/*.src.rpm': No such file or
> directory
> /bin/cp: cannot stat `dmapi/build/rpm/*.src.rpm': No such file or directory
> /bin/cp: cannot stat `xfsdump/build/rpm/*.src.rpm': No such file or
> directory
It's just trying to copy rpms to a central location, and they didn't
build for you (maybe you're on debian or similar?)
So kind of a dumb top-level makefile (hmm who wrote that stuff... ;-)
but it looks like all of your packages built as tarballs.
-Eric
> make: *** [cmds] Error 1
>
> anyone ?
>
>
prev parent reply other threads:[~2007-06-05 15:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-05 14:49 building xfstests Raz Ben-Jehuda(caro)
2007-06-05 15:07 ` 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=46657C17.1090105@sandeen.net \
--to=sandeen@sandeen.net \
--cc=linux-xfs@oss.sgi.com \
--cc=raziebe@gmail.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