All of lore.kernel.org
 help / color / mirror / Atom feed
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 14:04:05 +0100	[thread overview]
Message-ID: <20030116140405.P7526@humilis> (raw)
In-Reply-To: <3E26A821.4060006@namesys.com>

Yury Umanets wrote (ao):
> First of all try to make bk pull in 5 minutes.the commited stuff
> should be available.

Yep, there is something to pull now.

> >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 $
> >
> It is apparently because of old version of autoconf, which is not
> supported by us. I'll disable version older then 2.50

Aha, oke. I edited prepare-conf to use the newer tools on my system.
I also made a tar of the bk clone+pull.

ookhoi $ tar xf reiser4progs.tar
ookhoi $ cd reiser4progs
ookhoi $ bk pull
Nothing to pull from bk://namesys.com/bk/reiser4progs
ookhoi $ cat /tmp/prepare-conf > prepare-conf
ookhoi $ cat prepare-conf
echo aclocal-1.4
aclocal-1.4
echo autoheader2.50
autoheader2.50
echo autoconf2.50
autoconf2.50
echo automake-1.4 --add-missing
automake-1.4 --add-missing
ookhoi $ ./prepare-conf
aclocal-1.4
autoheader2.50
WARNING: Using auxiliary files such as `acconfig.h', `config.h.bot'
WARNING: and `config.h.top', to define templates for `config.h.in'
WARNING: is deprecated and discouraged.

WARNING: Using the third argument of `AC_DEFINE' and
WARNING: `AC_DEFINE_UNQUOTED' allows to define a template without
WARNING: `acconfig.h':

WARNING:   AC_DEFINE([NEED_MAIN], 1,
WARNING:             [Define if a function `main' is needed.])

WARNING: More sophisticated templates can also be produced, see the
WARNING: documentation.
autoconf2.50
automake-1.4 --add-missing
ookhoi $ ./configure > /dev/null
configure: WARNING: libuuid could not be found which is required for the --with-uuid

./configure: line 2786: yes=no: command not found
configure: WARNING: The headers for libuuid could not be found which
are required for the --with-uuid option.

ookhoi $ make > /dev/null
ookhoi $

# find / -name '*reiser4*' | egrep -v '/usr/src|/tmp'
# make install > /dev/null
# find / -name '*reiser4*' | egrep -v '/usr/src|/tmp'
/usr/local/lib/reiser4
/usr/local/lib/libreiser4.a
/usr/local/lib/libreiser4.la
/usr/local/man/man8/mkfs.reiser4.8
/usr/local/man/man8/debugfs.reiser4.8
/usr/local/sbin/make_reiser4
/usr/local/sbin/debugfs.reiser4
/usr/local/sbin/fsck.reiser4
/usr/local/sbin/mkfs.reiser4
/usr/local/share/aclocal/libreiser4.m4
/usr/local/include/reiser4
/usr/local/include/reiser4/reiser4.h
#

ookhoi $ ldd `which mkfs.reiser4`
        libncurses.so.5 => /lib/libncurses.so.5 (0x40017000)
        libreadline.so.4 => /lib/libreadline.so.4 (0x40057000)
        libc.so.6 => /lib/libc.so.6 (0x40080000)
        /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)
ookhoi $

# mkfs.reiser4 /dev/sda1
mkfs.reiser4 0.2.0
Copyright (C) 2001, 2002 by Hans Reiser, licensing governed by
reiser4progs/COPYING.

Error: There are no any built-in plugins found.
Fatal: Can't initialize plugin factory.
Error: Can't initialize libreiser4.
#


> >Can I provide more info? Is there something you would like me to do?
> >
> No, thanks a lot :) It was very nice of you :)

You're vere welcome!

  reply	other threads:[~2003-01-16 13:04 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
2003-01-16 12:40                 ` Yury Umanets
2003-01-16 13:04                   ` Ookhoi [this message]
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=20030116140405.P7526@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.