All of lore.kernel.org
 help / color / mirror / Atom feed
From: L A Walsh <lkml@tlinx.org>
To: Karel Zak <kzak@redhat.com>
Cc: util-linux@vger.kernel.org
Subject: static linking working w/gnu?  (was Re: [ANNOUNCE] util-linux v2.33-rc1)
Date: Mon, 08 Oct 2018 00:30:50 -0700	[thread overview]
Message-ID: <5BBB07AA.6010403@tlinx.org> (raw)
In-Reply-To: <20181002101454.qm5gzasb5naamnbg@ws.net.home>

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:
>   

On 10/7/2018 8:13 AM, Thorsten Kukuk wrote:

On Sun, Oct 07, Stefan Seyfried wrote:

> > /usr/lib64/gcc/x86_64-suse-linux/8/../../../../x86_64-suse-linux/bin/ld:
> > ./.libs/libmount.a(libmount_la-utils.o): in function `mnt_get_gid':
> > /dev/shm/util-linux-2.33-rc1/libmount/src/utils.c:614: warning: Using
> > 'getgrnam_r' in statically linked applications requires at runtime the
> > shared libraries from the glibc version used for linking
> ....
> > /usr/lib64/gcc/x86_64-suse-linux/8/../../../../x86_64-suse-linux/bin/ld:
> > ./.libs/libmount.a(libmount_la-utils.o): in function `mnt_get_username':
> > /dev/shm/util-linux-2.33-rc1/libmount/src/utils.c:566: warning: Using
> > 'getpwuid_r' in statically linked applications requires at runtime the
> > shared libraries from the glibc version used for linking
> > The bug is thus "RESOLVED WORKSFORME"
>   

No, the bug is, that the code is not designed for static linking,
as all the warnings show. And the upstream author should get the
same warnings as you abvoe.

-----
> On Sun, Oct 07, Stefan Seyfried wrote:
> > Am 07.10.18 um 00:17 schrieb L A Walsh:
> > > Because these utils 'should' be statically linkable and *are* on
> > > redhat> (which I thought opensuse was based on).
> 
> > Where do you get your alternative facts from?
-------------


So Karel, 

	Did you get warnings similar to the above?  The claim
is that you should be getting similar errors, but I got the impression
that you did not.

One person claimed it to be a bug in the Gnu tools & lib, while
others claim its designed that way, so not a bug...*sigh*.

But anyway -- did you get any such warnings?


I love the way Stefan labels my statement about some of the utils
being statically linkable and that it works on redhat an "alternative fact".

(sigh)...
Thanks!



  parent reply	other threads:[~2018-10-08  7:30 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-25 10:47 ` 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
2018-10-07 16:58         ` L A Walsh
2018-10-08  7:30     ` L A Walsh [this message]
2018-10-08  9:09       ` static linking working w/gnu? (was Re: [ANNOUNCE] util-linux v2.33-rc1) 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-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=5BBB07AA.6010403@tlinx.org \
    --to=lkml@tlinx.org \
    --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 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.