public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Florian Weimer <fweimer@redhat.com>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: libc-alpha@sourceware.org,  adhemerval.zanella@linaro.org
Subject: Re: [PATCH v4] Check global symbols in static library against shared library
Date: Thu, 23 May 2024 17:54:52 +0200	[thread overview]
Message-ID: <87zfsgo75f.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <CAMe9rOrRt-P6dP-75qAGdYihB7Bnka7_MofRX=d2DAGxvB54Rg@mail.gmail.com> (H. J. Lu's message of "Thu, 23 May 2024 06:58:42 -0700")

* H. J. Lu:

> On Thu, May 23, 2024 at 6:51 AM Florian Weimer <fweimer@redhat.com> wrote:
>>
>> * H. J. Lu:
>>
>> > diff --git a/sysdeps/alpha/Makefile b/sysdeps/alpha/Makefile
>> > index 11d5e65503..ed658c143e 100644
>> > --- a/sysdeps/alpha/Makefile
>> > +++ b/sysdeps/alpha/Makefile
>> > @@ -33,6 +33,11 @@ sysdep_routines += stxcpy stxncpy
>> >  endif
>> >
>> >  ifeq ($(subdir),elf)
>> > +# These global symbols are only in libc.so.
>> > +libc-shared-only-symbols += \
>> > +  __nldbl__IO_vfscanf \
>> > +# libc-shared-only-symbols
>> > +
>> >  # The ld.so startup code cannot use literals until it self-relocates.
>> >  CFLAGS-rtld.c = -mbuild-constants
>> >  endif
>>
>> Why doesn't this indicate a bug?  Shouldn't this part of libc.a, too?
>
> It is referenced from libnldbl_nonshared.a.
>
>> If it's not a bug, I think this belongs into
>> sysdeps/ieee754/ldbl-opt/Makefile.
>
> I will fix it.

What I meant is that you should probably be able to call scanf
from a program that is linked with -static -lnldbl, and the bug is the
missing __nldbl__IO_vfscanf function in libc.a.

Thanks,
Florian


  reply	other threads:[~2024-05-23 15:54 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-23 13:46 H.J. Lu
2024-05-23 13:51 ` Florian Weimer
2024-05-23 13:58   ` H.J. Lu
2024-05-23 15:54     ` Florian Weimer [this message]
2024-05-23 16:05       ` H.J. Lu
2024-05-23 18:29         ` Florian Weimer
2024-05-23 18:39           ` H.J. Lu
2024-05-23 19:42             ` Florian Weimer
2024-05-23 19:54               ` H.J. Lu
2024-05-23 20:00                 ` Florian Weimer
2024-05-23 20:10                   ` H.J. Lu

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=87zfsgo75f.fsf@oldenburg.str.redhat.com \
    --to=fweimer@redhat.com \
    --cc=adhemerval.zanella@linaro.org \
    --cc=hjl.tools@gmail.com \
    --cc=libc-alpha@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).