public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Sam James <sam@gentoo.org>
To: Adhemerval Zanella Netto <adhemerval.zanella@linaro.org>
Cc: Joan Bruguera <joanbrugueram@gmail.com>, libc-alpha@sourceware.org
Subject: Re: [PATCH] elf: Restore lconfig libc6 implicit soname logic [BZ #30125]
Date: Thu, 16 Feb 2023 01:40:27 +0000	[thread overview]
Message-ID: <FD442A61-81E4-43DD-B1A5-F56C19571123@gentoo.org> (raw)
In-Reply-To: <29e67aba-b51a-be4c-0408-de87d0aae4ad@linaro.org>

[-- Attachment #1: Type: text/plain, Size: 1886 bytes --]



> On 15 Feb 2023, at 13:19, Adhemerval Zanella Netto via Libc-alpha <libc-alpha@sourceware.org> wrote:
> 
> 
> 
> On 14/02/23 22:41, Joan Bruguera wrote:
>> While cleaning up old libc version support, the deprecated libc4 code was
>> accidentally kept in `implicit_soname`, instead of the libc6 code.
>> 
>> This causes additional symlinks to be created by `ldconfig` for libraries
>> without a soname, e.g. a library `libsomething.123.456.789` without a soname
>> will create a `libsomething.123` -> `libsomething.123.456.789` symlink.
>> 
>> As the libc6 version of the `implicit_soname` code is just a trivial xstrdup,
>> just inline it and remove `implicit_soname` altogether.
>> 
>> Some further simplification looks possible (e.g. the call to `create_links`
>> looks like a no-op if `soname == NULL`, other than the verbose printfs), but
>> logic is kept as-is for now.
>> 
>> Fixes: BZ #30125
>> Fixes: 8ee878592c4a ("Assume only FLAG_ELF_LIBC6 suport")
> 
> Patch looks ok in general, some comments on the test.  You used an old revision
> and then patch does not apply cleanly[1], could you rebase the patch and send
> a v2?
> 
> [1] https://patchwork.sourceware.org/project/glibc/patch/20230215014124.4144451-1-joanbrugueram@gmail.com/
> 
>> Signed-off-by: Joan Bruguera <joanbrugueram@gmail.com>
> 
> We do not signed-off-by on glibc, so no need for it.
> 

https://sourceware.org/glibc/wiki/Contribution%20checklist#Developer_Certificate_of_Origin says we do?

>> [snip]

>> +gcc /dev/null -o $testroot/lib/libsomething.so.1.2.3 -shared
> 
> We can not assume gcc will be presented in PATH, you need to use the CC used
> on build.  So pass the $(CC) on tst-ldconfig-no-soname.out rule and use it on
> the script.

(Indeed, GCC may not be the used compiler either, or specifically 'gcc' but some
prefixed or versioned gcc).


[-- Attachment #2: Message signed with OpenPGP --]
[-- Type: application/pgp-signature, Size: 358 bytes --]

  parent reply	other threads:[~2023-02-16  1:40 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-15  1:41 Joan Bruguera
2023-02-15  1:47 ` Joan Bruguera
2023-02-15 13:19 ` Adhemerval Zanella Netto
2023-02-16  1:29   ` Joan Bruguera
2023-02-16  1:40   ` Sam James [this message]
2023-02-16  2:23     ` [PATCH v3] elf: Restore ldconfig " Joan Bruguera
2023-02-16  6:08       ` Florian Weimer
2023-02-16  2:23     ` [PATCH] elf: Restore lconfig " Joan Bruguera
2023-02-16  6:01       ` Florian Weimer
2023-02-16  1:24 ` [PATCH v2] elf: Restore ldconfig " Joan Bruguera
2023-02-16  2:08   ` [PATCH v3] " Joan Bruguera
2023-02-18 21:52     ` [PATCH v4] " Joan Bruguera
2023-02-20 12:32       ` Adhemerval Zanella Netto
2023-02-20 13:21         ` Florian Weimer
2023-02-20 13:55           ` Adhemerval Zanella Netto
2023-02-20 14:04             ` Florian Weimer
2023-02-20 14:26               ` Adhemerval Zanella Netto

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=FD442A61-81E4-43DD-B1A5-F56C19571123@gentoo.org \
    --to=sam@gentoo.org \
    --cc=adhemerval.zanella@linaro.org \
    --cc=joanbrugueram@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).