From: Eric Sandeen <sandeen@sandeen.net>
To: aelder@sgi.com
Cc: Christoph Hellwig <hch@infradead.org>, xfs@oss.sgi.com
Subject: Re: [PATCH 3/3] xfsqa: build dbtest on debian platforms
Date: Thu, 29 Apr 2010 22:20:11 -0500 [thread overview]
Message-ID: <4BDA4C6B.3080503@sandeen.net> (raw)
In-Reply-To: <1272594520.3221.154.camel@doink>
Alex Elder wrote:
> On Fri, 2010-04-30 at 11:26 +1000, Dave Chinner wrote:
>> On Thu, Apr 29, 2010 at 06:46:11AM -0400, Christoph Hellwig wrote:
>>> Spoken too soon. While this second patch at least compiles on my Debian
>>> testing system it doesn't link:
>>>
>>> /tmp/ccWcHXtY.o: In function `CleanupDbmLookup': /root/xfstests-dev/src/dbtest.c:304: undefined reference to `dbm_close'
>>> /tmp/ccWcHXtY.o: In function `DoDbmLookup':
>>> /root/xfstests-dev/src/dbtest.c:220: undefined reference to `dbm_fetch'
>>> /root/xfstests-dev/src/dbtest.c:264: undefined reference to `dbm_fetch' /tmp/ccWcHXtY.o: In function `InitDbmLookup':
>>> /root/xfstests-dev/src/dbtest.c:144: undefined reference to `dbm_open'
>>> /root/xfstests-dev/src/dbtest.c:178: undefined reference to `dbm_store'
>>> /root/xfstests-dev/src/dbtest.c:191: undefined reference to `dbm_close'
>>> /root/xfstests-dev/src/dbtest.c:196: undefined reference to `dbm_open'
>>> collect2: ld returned 1 exit status
>>> make[2]: *** [dbtest] Error 1
>>> make[1]: *** [src] Error 2
>>> make: *** [default] Error 2
>> Where is libgdbm-compat on your system?
>
> I think we need to do a better job of defining what's required
> for this stuff--building and running. I know I had trouble
> the first time I set things up, and now that it works I
> have no recollection of the stuff that I did. It would be
> good to make it easier for people to get testing going,
> we might get more people actually running them in a wider
> variety of environments.
Making missing stuff gracefully handled runtime helps...
I also have a hacked up rpm for this, that way package dependencies
take care of it all seamlessly:
BuildRequires: autoconf, libtool, xfsprogs-devel, e2fsprogs-devel
BuildRequires: libacl-devel, libattr-devel, libaio-devel
Requires: bash, xfsprogs, xfsdump, perl, acl, attr, bind-utils
Requires: bc, indent, quota
If I just knew a decent place to drop the stuff that was compliant
with fs hierarchy rules, I'd toss it into fedora, and debian might
not be far behind ...
-Eric
> -Alex
>
> _______________________________________________
> xfs mailing list
> xfs@oss.sgi.com
> http://oss.sgi.com/mailman/listinfo/xfs
>
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-04-30 3:18 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-29 0:16 [PATCH 0/3] xfstests: miscellaneous patches Dave Chinner
2010-04-29 0:16 ` [PATCH 1/3] xfsqa: clean up 030 repair output Dave Chinner
2010-04-29 10:18 ` Christoph Hellwig
2010-04-29 0:16 ` [PATCH 2/3] xfsqa: keep xfs_fsr output around in test 222 Dave Chinner
2010-04-29 10:19 ` Christoph Hellwig
2010-04-29 0:16 ` [PATCH 3/3] xfsqa: build dbtest on debian platforms Dave Chinner
2010-04-29 6:49 ` Dave Chinner
2010-04-29 10:20 ` Christoph Hellwig
2010-04-29 10:46 ` Christoph Hellwig
2010-04-30 1:26 ` Dave Chinner
2010-04-30 2:28 ` Alex Elder
2010-04-30 3:20 ` Eric Sandeen [this message]
2010-04-30 8:55 ` Dave Chinner
2010-04-30 16:39 ` Christoph Hellwig
2010-04-30 17:24 ` Alex Elder
2010-04-29 10:20 ` Christoph Hellwig
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=4BDA4C6B.3080503@sandeen.net \
--to=sandeen@sandeen.net \
--cc=aelder@sgi.com \
--cc=hch@infradead.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox