From: Eric Sandeen <sandeen@redhat.com>
To: "Ted Ts'o" <tytso@mit.edu>
Cc: ext4 development <linux-ext4@vger.kernel.org>
Subject: Re: e2fsprogs: use ALL_CFLAGS to build gen_crc32ctable
Date: Mon, 10 Oct 2011 12:52:58 -0500 [thread overview]
Message-ID: <4E9330FA.4070307@redhat.com> (raw)
In-Reply-To: <4E932DBE.7080203@redhat.com>
On 10/10/11 12:39 PM, Eric Sandeen wrote:
> On 10/3/11 10:02 PM, Ted Ts'o wrote:
...
>> diff --git a/lib/ext2fs/crc32c.c b/lib/ext2fs/crc32c.c
>> index 65bca5c..6be4336 100644
>> --- a/lib/ext2fs/crc32c.c
>> +++ b/lib/ext2fs/crc32c.c
>> @@ -40,6 +40,23 @@
>> #define PTR_ALIGN(p, a) ((typeof(p))ALIGN((unsigned long)(p), (a)))
>> #include "crc32c_defs.h"
>>
>> +#include "ext2fs.h"
>> +#ifdef WORDS_BIGENDIAN
>
> well, this has the exact same problem as originally reported, because
> we still don't have the include paths to find ext2fs.h in the tree,
> and it is still included via crc32c_defs.h
Sorry, ignore that; PEBKAC here. :(
(tarball naming convention change means I had to fix up the source
tarball name in 2 places in the spec, and I missed one. Apologies...)
Now I am getting translation table problems, but I'll see what's up
there.
mv: cannot stat `t-es.gmo': No such file or directory
mv: cannot stat `t-ca.gmo': No such file or directorymake[2]: *** [es.gmo] Error 1
-Eric
next prev parent reply other threads:[~2011-10-10 17:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-03 16:14 [PATCH] e2fsprogs: use ALL_CFLAGS to build gen_crc32ctable Eric Sandeen
2011-10-04 3:02 ` Ted Ts'o
2011-10-10 17:39 ` Eric Sandeen
2011-10-10 17:52 ` Eric Sandeen [this message]
2011-10-10 18:42 ` 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=4E9330FA.4070307@redhat.com \
--to=sandeen@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
/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.