From: Maxime Devos <maximedevos@telenet.be>
To: zamfofex <zamfofex@twdb.moe>, 54832@debbugs.gnu.org
Subject: [bug#54832] [patch] update glibc to 2.35
Date: Sun, 10 Apr 2022 12:16:30 +0200 [thread overview]
Message-ID: <9cef0f8b9f2e3a847bb8faa5e6b48f688f74841a.camel@telenet.be> (raw)
In-Reply-To: <935236349.13698.1649553391613@privateemail.com>
[-- Attachment #1: Type: text/plain, Size: 1344 bytes --]
zamfofex schreef op za 09-04-2022 om 22:16 [-0300]:
+ (define empty-static-libraries '("libpthread.a"
"libdl.a" "libutil.a" "libanl.a"))
+ (define (empty-static-library? file)
+ (any (lambda (s) (string=? file s)) empty-
static-libraries))
+
(define (static-library? file)
;; Return true if FILE is a static library.
The
;; "_nonshared.a" files are referred to by
libc.so,
;; libpthread.so, etc., which are in fact
linker
;; scripts.
(and (string-suffix? ".a" file)
- (not (string-contains file
"_nonshared"))))
+ (not (string-contains file
"_nonshared"))
+ (not (empty-static-library? file))))
Why are empty static libraries skipped? Would "gcc -static -lpthread main.c" (*)
(in an environment that includes glibc:static) still work, or does it now fail?
Greetings,
Maxime.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
next prev parent reply other threads:[~2022-04-10 10:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-10 1:16 [bug#54832] [patch] update glibc to 2.35 zamfofex
2022-04-10 10:16 ` Maxime Devos [this message]
[not found] ` <1497835452.18920.1649591936889@privateemail.com>
2022-04-24 14:19 ` [bug#54832] Fwd: " zamfofex
2022-04-10 10:17 ` Maxime Devos
2022-04-10 10:18 ` Maxime Devos
2022-05-15 21:31 ` Ludovic Courtès
2022-06-06 12:06 ` zamfofex
2022-07-17 10:06 ` Ludovic Courtès
2022-07-19 14:12 ` zamfofex
2022-07-19 19:16 ` Greg Hogan
2022-09-01 22:32 ` bug#54832: " Marius Bakke
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=9cef0f8b9f2e3a847bb8faa5e6b48f688f74841a.camel@telenet.be \
--to=maximedevos@telenet.be \
--cc=54832@debbugs.gnu.org \
--cc=zamfofex@twdb.moe \
/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).