All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yury Umanets <umka@namesys.com>
To: ookhoi@humilis.net
Cc: 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 22:17:47 +0300	[thread overview]
Message-ID: <3E27055B.4090706@namesys.com> (raw)
In-Reply-To: <20030116200305.T7526@humilis>

Ookhoi wrote:

>Yury Umanets wrote (ao):
>  
>
>>Looks like the problem is in line
>>
>>gcc -g -O2 -D_REENTRANT -D_FILE_OFFSET_BITS=64 -g -W -Wall -Wno-unused
>>-Werror -DPLUGIN_DIR=\"/usr/l
>>ocal/lib/reiser4\" -o debugfs.reiser4 debugfs.o
>>../../libreiser4/.libs/libreiser4.a ../../progs/lib
>>misc/.libs/libmisc.a /usr/src/reiser4progs/libaal/.libs/libaal.a
>>-lncurses -lreadline
>>
>>Your libtool has decided to link all binaries against static library
>>../../libreiser4/.libs/libreiser4.a. This library contains plugins
>>code too. But, lnker was unable to find direct links to plugin
>>symbols. That is because they do not exist, we're working with plugins
>>by means of using interface structs for example, item_ops, which
>>contains all methods of corresponding item plugin. So, linker did not
>>include plugin symbols into result binary.
>>
>>The cure ptobably is to install more recent libtool.
>>    
>>
>
>Oke, I'll search for a more recent one. I do run an up to date debian
>sid (unstable) though. Hm :-)
>
>ookhoi $ libtool --version
>ltmain.sh (GNU libtool) 1.4.3 (1.922.2.111 2002/10/23 02:54:36)
>
libtool --version
ltmain.sh (GNU libtool) 1.4.2 (1.922.2.53 2001/09/11 03:18:52)

>
>I'll report success or failure. Thanks!
>
>  
>
Thanks to you :) I'll find the cure :)

>  
>


-- 
Yury Umanets



  reply	other threads:[~2003-01-16 19:17 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
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 [this message]
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=3E27055B.4090706@namesys.com \
    --to=umka@namesys.com \
    --cc=ookhoi@humilis.net \
    --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.