From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Karel Zak <kzak@redhat.com>
Cc: util-linux@vger.kernel.org
Subject: Re: [PATCH 2/2] Add uuid to the linker flags if using built LIBBLKID
Date: Wed, 29 Feb 2012 22:38:08 +0100 [thread overview]
Message-ID: <20120229213808.GB11628@linutronix.de> (raw)
In-Reply-To: <20120228143537.GD22034@x2.net.home>
* Karel Zak | 2012-02-28 15:35:37 [+0100]:
>> --- a/config/include-Makefile.am
>> +++ b/config/include-Makefile.am
>> @@ -31,6 +31,9 @@ ul_libuuid_la = $(top_builddir)/libuuid/src/libuuid.la
>> $(ul_libuuid_la):
>> $(MAKE) -C $(ul_libuuid_builddir)
>>
>> +if BUILD_LIBBLKID
>
> I guess you mean "if BUILD_LIBUUID".
I don't think so. Because if I build LIBBLKID it requires syms from
LIBUUID.
>> + ul_libblkid_la += $(ul_libuuid_la)
>> +endif
>
> Hmm... I don't like this, it creates explicit dependence, libtool
> should be smart enough to maintain dependencies dynamically.
>
> We have libuuid.la in libblkid_la_LIBADD (see in libblkid/src/Makefile.am) and
> on my system it generates the final libblkid.la with
>
> # Libraries that this one depends upon.
> dependency_libs='/home/projects/util-linux/util-linux/libuuid/src/libuuid.la'
>
>
> It would be nice to know more details about your environment to
> reproduce this problem. If I will be able to reproduce the problem
> then I can also add regression test (for cross compiling).
configured by
| $ ./configure --host=powerpc-linux-gnu --without-ncurses host_alias=powerpc-linux-gnu --no-create --no-recursion
according to config.log (everything starting with host_alias was not
added me). It is a cross compiler environment with no headers/libs. So
both libs (uuid and libblkid should be built by util-linux). After a
make I end up with:
|make[4]: Nothing to be done for `all-am'.
|make[4]: Leaving directory `/home/bigeasy/work/git/util-linux/libblkid/src'
|make[3]: Leaving directory `/home/bigeasy/work/git/util-linux/libblkid/src'
|Making all in samples
|make[3]: Entering directory `/home/bigeasy/work/git/util-linux/libblkid/samples'
| CCLD mkfs
|/usr/lib/gcc/powerpc-linux-gnu/4.4.5/../../../../powerpc-linux-gnu/bin/ld: warning: libuuid.so.1, needed by ../../libblkid/src/.libs/libblkid.so, not found (try using -rpath or -rpath-link)
|../../libblkid/src/.libs/libblkid.so: undefined reference to `uuid_unparse@UUID_1.0'
|collect2: ld returned 1 exit status
|make[3]: *** [mkfs] Error 1
>
> Karel
Sebastian
next prev parent reply other threads:[~2012-02-29 21:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-24 17:16 [PATCH 1/2] conifigure: add a crosscompile path for scanf_cv_alloc_modifier Sebastian Andrzej Siewior
2012-02-24 17:16 ` [PATCH 2/2] Add uuid to the linker flags if using built LIBBLKID Sebastian Andrzej Siewior
2012-02-28 14:35 ` Karel Zak
2012-02-29 21:38 ` Sebastian Andrzej Siewior [this message]
2012-02-28 14:12 ` [PATCH 1/2] conifigure: add a crosscompile path for scanf_cv_alloc_modifier Karel Zak
2012-02-29 21:31 ` Sebastian Andrzej Siewior
2012-03-20 8:18 ` Karel Zak
2012-03-30 19:49 ` Mike Frysinger
2012-03-30 20:52 ` Mike Frysinger
2012-04-02 7:14 ` Sebastian Andrzej Siewior
2012-04-02 19:00 ` Mike Frysinger
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=20120229213808.GB11628@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=kzak@redhat.com \
--cc=util-linux@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