From: Ookhoi <ookhoi@humilis.net>
To: Yury Umanets <umka@namesys.com>
Cc: ookhoi@humilis.net, Reiserfs-List <reiserfs-list@namesys.com>
Subject: Re: build problem BK reiser4progs: /usr/include/features.h:218:52: operator '==' has no left operand
Date: Thu, 16 Jan 2003 13:31:00 +0100 [thread overview]
Message-ID: <20030116133100.O7526@humilis> (raw)
In-Reply-To: <3E26A2A6.702@namesys.com>
Yury Umanets wrote (ao):
> >>Strange :) There must be changes in configure.in
still "Nothing to pull from"
> Please remove all previous versions of reiser4progs. Everything,
> libaal, libreiser4, etc.
Did that everywhere.
> >When I try to mkfs.reiser4 /dev/sda1 it says:
> >
> >ookhoi $ mkfs.reiser4 /dev/sda1
> >mkfs.reiser4 0.2.0
> >Copyright (C) 2001, 2002 by Hans Reiser, licensing governed by
> >reiser4progs/COPYING.
> >Fatal: Can't initialize plugin factory.
> >Error: Can't initialize libreiser4.
> >ookhoi $ echo $?
> >8
>
> It is because libreiser4 was unable to found any plugins (built-in and
> separate *.so). I will make error messages more detailed.
Oki, tnx :-)
I see this btw:
ookhoi $ ./prepare-conf
aclocal
autoheader
configure.in:181: warning: AC_TRY_RUN called without default to allow cross compiling
autoconf
configure.in:181: warning: AC_TRY_RUN called without default to allow cross compiling
autoconf: Undefined macros:
configure.in:148:AC_SYS_LARGEFILE
configure.in:198:AC_FUNC_MALLOC
automake --add-missing
ookhoi $ ./configure > /dev/null
configure: warning: libuuid could not be found which is required for the --with-uuid
./configure: line 1098: yes=no: command not found
./configure: line 1681: AC_SYS_LARGEFILE: command not found
configure: warning: The headers for libuuid could not be found which
are required for the --with-uuid option.
./configure: line 6649: AC_FUNC_MALLOC: command not found
ookhoi $ make > /dev/null
In file included from /usr/include/stdint.h:26,
from ../include/aal/aal.h:46,
from device.c:8:
/usr/include/features.h:218:52: operator '==' has no left operand
make[2]: *** [device.lo] Error 1
make[1]: *** [all-recursive] Error 1
make: *** [all-recursive-am] Error 2
ookhoi $
ookhoi $ autoconf --version
Autoconf version 2.13
ookhoi $ gcc --version
gcc (GCC) 3.2.2 20030109 (Debian prerelease)
Can I provide more info? Is there something you would like me to do?
next prev parent reply other threads:[~2003-01-16 12:31 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-16 9:27 build problem BK reiser4progs: /usr/include/features.h:218:52: operator '==' has no left operand Ookhoi
2003-01-16 10:44 ` Yury Umanets
2003-01-16 11:02 ` Ookhoi
2003-01-16 11:08 ` Yury Umanets
2003-01-16 11:10 ` Ookhoi
[not found] ` <3E269499.2090909@namesys.com>
[not found] ` <20030116123949.N7526@humilis>
2003-01-16 12:16 ` Yury Umanets
2003-01-16 12:31 ` Ookhoi [this message]
2003-01-16 12:40 ` Yury Umanets
2003-01-16 13:04 ` Ookhoi
2003-01-16 13:23 ` Yury Umanets
2003-01-16 13:55 ` Ookhoi
2003-01-16 14:04 ` Yury Umanets
2003-01-16 18:00 ` Ookhoi
2003-01-16 18:07 ` Yury Umanets
2003-01-16 18:28 ` Ookhoi
2003-01-16 18:29 ` Yury Umanets
2003-01-16 18:44 ` Yury Umanets
2003-01-16 19:03 ` Ookhoi
2003-01-16 19:17 ` Yury Umanets
2003-01-16 19:41 ` Ookhoi
2003-01-16 19:51 ` Yury Umanets
2003-01-16 20:27 ` Ookhoi
2003-01-17 10:08 ` Yury Umanets
2003-01-16 11:09 ` Ookhoi
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=20030116133100.O7526@humilis \
--to=ookhoi@humilis.net \
--cc=reiserfs-list@namesys.com \
--cc=umka@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.