From: Bernhard Voelker <mail@bernhard-voelker.de>
To: L A Walsh <lkml@tlinx.org>, Karel Zak <kzak@redhat.com>
Cc: util-linux@vger.kernel.org
Subject: Re: [ANNOUNCE] util-linux v2.33-rc1
Date: Sun, 7 Oct 2018 16:57:45 +0200 [thread overview]
Message-ID: <a8f5fac6-b7a3-ee92-3f5b-b6459cdc3b5f@bernhard-voelker.de> (raw)
In-Reply-To: <5BB90C30.1080005@tlinx.org>
On 10/6/18 9:25 PM, L A Walsh wrote:
> On 10/2/2018 3:14 AM, Karel Zak wrote:
>> On Sun, Sep 30, 2018 at 04:33:14PM -0700, L A Walsh wrote:
>>
>>> On 9/25/2018 3:47 AM, Karel Zak wrote:
>>>
>>>> The commands mount and umount
>>>>
>>> ---
>>> I note that umount has a static option umount.static, but I don't see
>>> the same for mount (i.e. mount.static).
>>>
>>
>> $ ./configure --enable-static-programs=mount,umount
>> $ make mount.static umount.static
>>
>> works for me:
>>
> so I see... Except I got:
> CC sys-utils/mount_static-mount.o
> CCLD mount.static
> libtool: warning: complete static linking is impossible in this
> configuration
> /usr/bin/ld: total time in link: 0.038189
> CC sys-utils/umount_static-umount.o
> CCLD umount.static
> libtool: warning: complete static linking is impossible in this
> configuration
> /usr/bin/ld: total time in link: 0.039017
>
> with ldd:
> Ishtar:tools/util-linux/util-linux-2.33-rc1> ldd mount.static
> linux-vdso.so.1 (0x00007ffc38d78000)
> librt.so.1 => /lib64/librt.so.1 (0x0000003001c00000)
> libc.so.6 => /lib64/libc.so.6 (0x0000003000800000)
> libpthread.so.0 => /lib64/libpthread.so.0 (0x0000003000c00000)
> /lib64/ld-linux-x86-64.so.2 (0x00007f81b9262000)
>
> It seems something about my config (or Suse's config) is creating a problem
> for static linking. I should probably ask on the Suse list
> to see if anyone as run into this or solved it, though if you
> have any ideas or known probs, great!
$ zypper install glibc-devel-static
next prev parent reply other threads:[~2018-10-07 14:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-25 10:47 [ANNOUNCE] util-linux v2.33-rc1 Karel Zak
2018-09-30 23:33 ` L A Walsh
2018-10-02 10:14 ` Karel Zak
2018-10-06 19:25 ` L A Walsh
2018-10-07 14:57 ` Bernhard Voelker [this message]
2018-10-07 16:58 ` L A Walsh
2018-10-08 7:30 ` static linking working w/gnu? (was Re: [ANNOUNCE] util-linux v2.33-rc1) L A Walsh
2018-10-08 9:09 ` Karel Zak
2018-10-08 12:43 ` L A Walsh
2018-10-16 0:48 ` L A Walsh
2018-10-04 22:11 ` [ANNOUNCE] util-linux v2.33-rc1 Ruediger Meier
2018-10-04 22:11 ` Ruediger Meier
2018-10-05 9:37 ` Karel Zak
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=a8f5fac6-b7a3-ee92-3f5b-b6459cdc3b5f@bernhard-voelker.de \
--to=mail@bernhard-voelker.de \
--cc=kzak@redhat.com \
--cc=lkml@tlinx.org \
--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;
as well as URLs for NNTP newsgroup(s).