unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: ng0 <ng0@pragmatique.xyz>
To: 26874@debbugs.gnu.org
Subject: bug#26874: lvm2 build error
Date: Thu, 11 May 2017 14:55:15 +0000	[thread overview]
Message-ID: <20170511145515.u45dknfjcfn74htv@abyayala> (raw)
In-Reply-To: <20170511073109.olno56qranqdrj2x@abyayala>

ng0 transcribed 2.3K bytes:
> lvm2 from bc0e6c9312f5f755e1ccd7d8c43b58974e6f7d38 fails with this:
> 
> ../lib/liblvm-internal.a(sharedlib.o): In function `load_shared_library':
> sharedlib.c:(.text+0x130): warning: Using 'dlopen' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking
> /gnu/store/874zyvmg1ykihbx2j38m58srgblj7al9-eudev-3.2.1/lib/libudev.a(util.o): In function `get_group_creds':
> (.text+0x1e89): warning: Using 'getgrgid' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking
> /gnu/store/874zyvmg1ykihbx2j38m58srgblj7al9-eudev-3.2.1/lib/libudev.a(util.o): In function `get_group_creds':
> (.text+0x1ef2): warning: Using 'getgrnam' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking
> /gnu/store/874zyvmg1ykihbx2j38m58srgblj7al9-eudev-3.2.1/lib/libudev.a(util.o): In function `get_user_creds':
> (.text+0x1ddb): warning: Using 'getpwnam' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking
> /gnu/store/874zyvmg1ykihbx2j38m58srgblj7al9-eudev-3.2.1/lib/libudev.a(util.o): In function `get_user_creds':
> (.text+0x1d13): warning: Using 'getpwuid' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking
> ../libdm/ioctl/libdevmapper.a(libdm-string.o): In function `dm_size_to_string':
> libdm-string.c:(.text+0x11b6): undefined reference to `nearbyint'
> libdm-string.c:(.text+0x11cb): undefined reference to `floor'
> collect2: error: ld returned 1 exit status
> make[1]: *** [Makefile:163: lvm.static] Error 1
> make[1]: *** Waiting for unfinished jobs....
> make[1]: Leaving directory '/tmp/guix-build-lvm2-static-2.02.171.drv-0/LVM2.2.02.171/tools'
> make: *** [make.tmpl:327: tools] Error 2
> phase `build' failed after 22.0 seconds
> builder for `/gnu/store/jhmy3pfy0mda6svfjg82zz67j2qw6nxi-lvm2-static-2.02.171.drv' failed with exit code 1
> cannot build derivation `/gnu/store/nrk426gr7p9j8lfy9mi52yxfq6fylc76-cryptsetup-static-1.7.4.drv': 1 dependencies couldn't be built
> guix system: error: build failed: build of `/gnu/store/nrk426gr7p9j8lfy9mi52yxfq6fylc76-cryptsetup-static-1.7.4.drv' failed
> -- 
> https://pragmatique.xyz
> PGP: https://people.pragmatique.xyz/ng0/
> 
> 
> 

#lvm on freenode.net says we are on our own and that the method (in general)
to statically build lvm2 is considered fragile.
The comment was that we need to make libm available, statically, as well for
lvm2.
The only person shown by git blame gnu/packages/linux.scm for lvm2-static is
Ludovic.
-- 
https://pragmatique.xyz
PGP: https://people.pragmatique.xyz/ng0/

  reply	other threads:[~2017-05-11 14:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-11  7:31 bug#26874: lvm2 build error ng0
2017-05-11 14:55 ` ng0 [this message]
2017-05-11 18:10   ` Marius Bakke
2017-05-11 19:45 ` Marius Bakke
2017-05-11 20:12   ` ng0

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170511145515.u45dknfjcfn74htv@abyayala \
    --to=ng0@pragmatique.xyz \
    --cc=26874@debbugs.gnu.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).