From: Manish Singh <manish.singh@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] Small fixes for ocfs2-tools 1.1.1
Date: Sat Aug 20 15:48:10 2005 [thread overview]
Message-ID: <20050820204812.GA4469@ca-server1.us.oracle.com> (raw)
In-Reply-To: <20050820141934.GM4436@marowsky-bree.de>
On Sat, Aug 20, 2005 at 04:19:34PM +0200, Lars Marowsky-Bree wrote:
> Hi,
>
> I'm just building ocfs2-tools 1.1.1 (bleeding edge ;-) for openSUSE.
>
> Attached you'll find two patches.
>
> One fixes obvious mistakes in configure.in as well as an uninitialized
> variable being dereferenced.
>
> The second one I'm not sure about whether you want to take it upstream.
> If linking against com_err, you need to also link against pthread now.
What changed to require this? That sounds kind of broken, and isn't
reflected in upstream e2fsprogs.
> In our specfile, I also had to move debugfs.ocfs2 and ocfs2cdsl from
> /sbin to /usr/sbin, because they link against glib, which is not on /,
> and thus our build system doesn't like binaries on / linked against
> that.
How about moving glib to / ? ;)
> The third attachment are the remaining signedness warnings the compiler
> generates. I've glanced at a few, and they seem harmless (except maybe
> the one in dump.c?), but you may want to clean them up...
Yeah, gcc4 spews like mad now...
> --- configure.in (revision 1063)
> +++ configure.in (working copy)
> @@ -84,7 +84,7 @@
>
> UUID_LIBS=
> AC_CHECK_LIB(uuid, uuid_unparse, UUID_LIBS=-luuid)
> -if test "x$COM_ERR_LIBS" = "x"; then
> +if test "x$UUID_LIBS" = "x"; then
> AC_MSG_ERROR([Unable to find uuid library])
> fi
> AC_CHECK_HEADER(uuid/uuid.h, :,
Cut'n'paste screw up. Thanks for noticing, this is applied to SVN.
-Manish
next prev parent reply other threads:[~2005-08-20 15:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-20 9:19 [Ocfs2-devel] Small fixes for ocfs2-tools 1.1.1 Lars Marowsky-Bree
2005-08-20 15:48 ` Manish Singh [this message]
2005-08-20 16:32 ` Lars Marowsky-Bree
2005-08-20 18:36 ` Manish Singh
2005-08-21 23:01 ` Joel Becker
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=20050820204812.GA4469@ca-server1.us.oracle.com \
--to=manish.singh@oracle.com \
--cc=ocfs2-devel@oss.oracle.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.