All of lore.kernel.org
 help / color / mirror / Atom feed
From: Laurent Riffard <laurent.riffard@free.fr>
To: reiserfs-list@namesys.com
Subject: compilation issue with reiser4progs-0.4.20
Date: Thu, 25 Dec 2003 23:08:32 +0100	[thread overview]
Message-ID: <3FEB5FE0.7020805@free.fr> (raw)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


Hi

I just want to inform you with the following issue : if you try to
~ compile reiser4progs-0.4.20 and type "./prepare" before
"./configure" (without any option), it won't compile.

I tried it because it was noticed in
http://thebsh.namesys.com/snapshots/LATEST/READ.ME. I had the
following output :

reiser4progs-0.4.20$ ./prepare
Running aclocal...
Running autoheader...
Running autoconf...
Running automake --add-missing...
automake: libreiser4/Makefile.am: warning: automake does not
support libreiser4_alone_la_LDFLAGS being defined conditionally

As a consequence, the macro libnode40_static_la_CFLAGS is defined
in the Makefiles with "-DENABLE_LARGE_KEY -DENABLE_SHORT_KEY" but
it is not used in the compilation command line. And compilation of
plugin/node/node40/node40.c will fail.

Just untar the tarball, apply the patch from
http://marc.theaimsgroup.com/?l=reiserfs&m=107237319006797&w=2 ,
and "./configure" works for me.

- --
laurent
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQE/61/gUqUFrirTu6IRAhj3AJ9dsCOecaFPIy6Ox6eWDUdRgbqhGwCfS4bP
HJBqBJijQMDgJ/YgC11yer4=
=T7F/
-----END PGP SIGNATURE-----


             reply	other threads:[~2003-12-25 22:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-25 22:08 Laurent Riffard [this message]
2003-12-26  0:46 ` compilation issue with reiser4progs-0.4.20 Domenico Andreoli
2003-12-26 21:53   ` Laurent Riffard

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=3FEB5FE0.7020805@free.fr \
    --to=laurent.riffard@free.fr \
    --cc=reiserfs-list@namesys.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.