From: Alex Elder <aelder@sgi.com>
To: Christian Kujau <lists@nerdbynature.de>
Cc: Christoph Hellwig <hch@infradead.org>, xfs@oss.sgi.com
Subject: Re: xfsprogs: only absolute run-paths are allowed
Date: Wed, 21 Jul 2010 14:10:04 -0500 [thread overview]
Message-ID: <1279739404.1816.20.camel@doink> (raw)
In-Reply-To: <alpine.DEB.2.01.1007211149320.3964@bogon.housecafe.de>
On Wed, 2010-07-21 at 11:55 -0700, Christian Kujau wrote:
> On Wed, 21 Jul 2010 at 13:33, Alex Elder wrote:
> > > The patch below should fix this issue. Note that you need to do a
> > >
> > > make realclean
> > > make configure
> > >
> > > to regenerate the configure script first.
> >
> > This looks OK to me. Once you get confirmation
> > it works for Christian you can re-format your
> > description and commit it. (I didn't see the
> > problem in my environment for some reason.)
>
> Yes, the patch works for me, thanks Christoph!
>
> Tested-by: Christian Kujau <lists@nerdbynature.de>
>
> Btw, I noticed quite a few warnings[0] during compilation:
>
> warning: pointer targets in assignment differ in signedness
> warning: pointer targets in passing argument 1 of '...' differ in signedness
>
> I hope they're nothing to worry about?
Nothing to worry about. We need to update some
code but it some cases it needs to match the
kernel code as well. Eventually we'll get there.
-Alex
> Thanks again,
> Christian.
>
> [0] http://nerdbynature.de/bits/xfsprogs/prefix/make_v3.1.2.log.gz
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-07-21 19:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-21 11:31 xfsprogs: only absolute run-paths are allowed Christian Kujau
2010-07-21 17:13 ` Christoph Hellwig
2010-07-21 18:33 ` Alex Elder
2010-07-21 18:55 ` Christian Kujau
2010-07-21 19:10 ` Alex Elder [this message]
2010-07-22 5:22 ` 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=1279739404.1816.20.camel@doink \
--to=aelder@sgi.com \
--cc=hch@infradead.org \
--cc=lists@nerdbynature.de \
--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