From: Edward Shishkin <edward.shishkin@gmail.com>
To: Matthew White <mehw.is.me@inventati.org>
Cc: ReiserFS development mailing list <reiserfs-devel@vger.kernel.org>
Subject: Re: reiser4progs - linking to libreiser4 gives "undefined reference to misc_str2long"
Date: Tue, 17 Nov 2020 22:11:10 +0100 [thread overview]
Message-ID: <66031259-74b7-74a7-9ec9-c57651942214@gmail.com> (raw)
In-Reply-To: <20201116161230.7be6dcf0@pineapple>
On 11/16/2020 04:15 PM, Matthew White wrote:
> Hello,
Hi Matthew,
>
> I was having problems linking to libreiser4 once it is installed into my
> system, even compiling a dumb program fails (see test-libreiser4.c).
Ummm, indeed, it doesn't work. The next surprise for me is that it
also doesn't work if we build/install reiser4progs rolled back to the
old commits. Whereas reiser4 support in grub also includes libreiser4.h
header:
https://github.com/edward6/reiser4progs/blob/master/grub-0.97-reiser4-20060227.diff
It could happen that I missed something though..
>
> Compiler: gcc (Gentoo 9.3.0-r1 p3) 9.3.0
> OS: Gentoo GNU/Linux
> reiser4progs versions tested: v1.2.1, v2.0.2, v2.0.3, v2.0.4 (github)
>
> $ /usr/bin/ld: /lib64/libreiser4-1.2.so.1: undefined reference to `misc_str2long'
> $ collect2: error: ld returned 1 exit status
>
> I attach the dumb program used for testing 'test-libreiser4.c' and also
> patches to https://github.com/edward6/reiser4progs [master (v1.2.1) and
> format41 (v2.0.4) branches].
>
> Details are in the patches and also here: https://bugs.gentoo.org/754924
>
> The solution I adopted is to compile libreiser4 (libreiser4/Makefile.am)
> linking it also to the libmisc convenience library (static libtool).
>
> Is there a specific reason to not making libmisc an installable library?
I don't know such reasons. I'll merge your patches.
Double thanks for the "format41" branch :)
Edward.
> Or, instead, why not linking libreiser4 to a static libmisc, and then to
> use just libreiser4 when lining demo/* and progs/* (Makefile.am files)?
>
> Thanks.
> - Matthew
>
> --
>
> Matthew White <mehw.is.me@inventati.org>
>
parent reply other threads:[~2020-11-17 21:11 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20201116161230.7be6dcf0@pineapple>]
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=66031259-74b7-74a7-9ec9-c57651942214@gmail.com \
--to=edward.shishkin@gmail.com \
--cc=mehw.is.me@inventati.org \
--cc=reiserfs-devel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).