From: Yury Umanets <umka@namesys.com>
To: ookhoi@humilis.net
Cc: 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:44:13 +0300 [thread overview]
Message-ID: <3E268CFD.5080604@namesys.com> (raw)
In-Reply-To: <20030116102742.I7526@humilis>
Ookhoi wrote:
>Hi all,
>
>A fresh BK reiser4progs gives me the following error. It is not obvious
>to me what is wrong :-/
>
>Please only deal with this if you have time. I can use the snapshot
>progs just fine.
>
>Tnx!
>
>
>$ make
>make all-recursive
>make[1]: Entering directory `/usr/src/reiser4progs'
>Making all in libaal
>make[2]: Entering directory `/usr/src/reiser4progs/libaal'
>/bin/sh ../libtool --mode=compile gcc -DHAVE_CONFIG_H -I. -I. -I.. -I../include -D_REENTRANT -D_FILE_OFFSET_BITS= -g -W -Wall -Wno-unused -Werror -DPLUGIN_DIR=\"/usr/local/lib/reiser4\" -c device.c
>gcc -DHAVE_CONFIG_H -I. -I. -I.. -I../include -D_REENTRANT -D_FILE_OFFSET_BITS= -g -W -Wall -Wno-unused -Werror -DPLUGIN_DIR=\"/usr/local/lib/reiser4\" -Wp,-MD,.deps/device.pp -c device.c -o device.o
>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[2]: Leaving directory `/usr/src/reiser4progs/libaal'
>make[1]: *** [all-recursive] Error 1
>make[1]: Leaving directory `/usr/src/reiser4progs'
>make: *** [all-recursive-am] Error 2
>
>
>
>
Looks like the problem with your autoconf. What version do you use?
--
Yury Umanets
next prev parent reply other threads:[~2003-01-16 10:44 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 [this message]
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
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=3E268CFD.5080604@namesys.com \
--to=umka@namesys.com \
--cc=Reiserfs-List@namesys.com \
--cc=ookhoi@humilis.net \
/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.