From: Felix Zielcke <fzielcke@z-51.de>
To: Edward Shishkin <edward.shishkin@gmail.com>,
ReiserFS development mailing list
<reiserfs-devel@vger.kernel.org>
Subject: Re: Reiser4 for Linux-4.14, Reiser4progs-1.2.0, Libaal-1.0.7, Format 4.0.2
Date: Mon, 27 Nov 2017 16:27:01 +0100 [thread overview]
Message-ID: <1511796421.5344.6.camel@z-51.de> (raw)
In-Reply-To: <8db85297-34f8-980c-dab9-c98b95fb592c@gmail.com>
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
next prev parent reply other threads:[~2017-11-27 15:27 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 [this message]
2017-11-27 20:05 ` Edward Shishkin
2017-11-28 11:50 ` Edward Shishkin
-- 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=1511796421.5344.6.camel@z-51.de \
--to=fzielcke@z-51.de \
--cc=edward.shishkin@gmail.com \
--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).