reiserfs-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Edward Shishkin <edward.shishkin@gmail.com>
To: Felix Zielcke <fzielcke@z-51.de>,
	ReiserFS development mailing list
	<reiserfs-devel@vger.kernel.org>
Cc: Christian Kujau <lists@nerdbynature.de>
Subject: Re: Reiser4 for Linux-4.14, Reiser4progs-1.2.0, Libaal-1.0.7, Format 4.0.2
Date: Tue, 28 Nov 2017 12:50:09 +0100	[thread overview]
Message-ID: <f1bfffae-0355-c4a3-cbb4-ca8f4ee970ec@gmail.com> (raw)
In-Reply-To: <8a29e976-de48-dabe-2b2f-a7149002251e@gmail.com>

Hello everyone.

Please, find version 1.2.1 of reiser4progs with the fixup:
https://sourceforge.net/projects/reiser4/files/reiser4-utils/reiser4progs

TBH, I am not sure that Reiser4 works for architectures different from
amd64 and i386. However, correct builds is a good start to fix things :)

Thanks,
Edward.

On 11/27/2017 09:05 PM, Edward Shishkin wrote:
> Hi Felix,
>
> Thank you for the hint!
> It seems that the following patch is incomplete (missing rename of 
> align_loop_flag):
> https://github.com/edward6/reiser4progs/commit/2b74e05bdde4f84a224bc235814d1fc51793a2c8 
>
> I'll prepare a new release basing on your fixup.
>
> Edward.
>
> On 11/27/2017 04:27 PM, Felix Zielcke wrote:
>> Am Montag, den 27.11.2017, 14:46 +0100 schrieb Edward Shishkin:
>>> Hi Felix,
>>>
>>> Thank you for the report, I'll try to find out, what is wrong.
>>>
>>> Edward.
>>>
>> Hi Edward,
>>
>> I got now a hint on the Debian bugtracker
>> The problem seems to be the variable used in the configure.ac check for
>> falign-loops
>> This patch seems to fix it:
>>
>> --- a/configure.ac
>> +++ b/configure.ac
>> @@ -408,7 +408,7 @@
>>   fi
>>      # Force no alignment to save space.
>> -if test "x$falign_loop_flag" = xyes; then
>> +if test "x$falign_loop_flag_cv_" = xyes; then
>>          ALIGN_FLAGS="-falign-jumps=1 -falign-loops=1 
>> -falign-functions=1 \
>>   -falign-labels=1 -fno-inline -fstrength-reduce"
>>   else
>>
>> Regards
>> Felix
>


  reply	other threads:[~2017-11-28 11:50 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-26 23:01 Reiser4 for Linux-4.14, Reiser4progs-1.2.0, Libaal-1.0.7, Format 4.0.2 Edward Shishkin
2017-11-27 13:10 ` Felix Zielcke
2017-11-27 13:46   ` Edward Shishkin
2017-11-27 15:27     ` Felix Zielcke
2017-11-27 20:05       ` Edward Shishkin
2017-11-28 11:50         ` Edward Shishkin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-11-27 14:37 Metztli Information Technology
2017-11-27 23:08 ` Edward Shishkin
2017-11-28 15:21 Metztli Information Technology
2017-11-28 17:08 ` Edward Shishkin
2017-11-29  3:05 Metztli Information Technology
2017-12-01 16:49 Metztli Information Technology

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=f1bfffae-0355-c4a3-cbb4-ca8f4ee970ec@gmail.com \
    --to=edward.shishkin@gmail.com \
    --cc=fzielcke@z-51.de \
    --cc=lists@nerdbynature.de \
    --cc=reiserfs-devel@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).