GNU bug report logs -
#77103
[PATCH v1] gnu: glibc/hurd: Hide to prevent warning
Previous Next
To reply to this bug, email your comments to 77103 AT debbugs.gnu.org.
There is no need to reopen the bug first.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
guix-patches <at> gnu.org
:
bug#77103
; Package
guix-patches
.
(Tue, 18 Mar 2025 17:48:03 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
Jakob Kirsch <jakob.kirsch <at> web.de>
:
New bug report received and forwarded. Copy sent to
guix-patches <at> gnu.org
.
(Tue, 18 Mar 2025 17:48:04 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
When dealing with the glibc package, you will often see the following warning:
warning: ambiguous package specification `glibc'
warning: choosing glibc <at> 2.39 from gnu/packages/base.scm:915:2
This is due to the fact that Hurd glibc is exported. A simple fix is to declare it as a hidden-package.
* gnu/packages/base.scm: (glibc/hurd): Hide
Change-Id: I3785a2d35e1c9b4efa039dbba7f379ae052dc69a
---
gnu/packages/base.scm | 23 ++++++++++++-----------
1 file changed, 12 insertions(+), 11 deletions(-)
diff --git a/gnu/packages/base.scm b/gnu/packages/base.scm
index 4c96ffa1a4..e8d502de8d 100644
--- a/gnu/packages/base.scm
+++ b/gnu/packages/base.scm
@@ -1663,17 +1663,18 @@ (define-public which
(license gpl3+))) ; some files are under GPLv2+
(define-public glibc/hurd
- (package/inherit glibc
- (source
- (origin
- (inherit (package-source glibc))
- (patches
- (append (origin-patches (package-source glibc))
- (search-patches "glibc-hurd-pthread_setcancelstate.patch"
- "glibc-hurd64-fault.patch"
- "glibc-hurd64-intr-msg-clobber.patch"
- "glibc-hurd64-sgms-context.patch"
- "glibc-hurd64-gcc-14.2-tls-bug.patch")))))))
+ (hidden-package
+ (package/inherit glibc
+ (source
+ (origin
+ (inherit (package-source glibc))
+ (patches
+ (append (origin-patches (package-source glibc))
+ (search-patches "glibc-hurd-pthread_setcancelstate.patch"
+ "glibc-hurd64-fault.patch"
+ "glibc-hurd64-intr-msg-clobber.patch"
+ "glibc-hurd64-sgms-context.patch"
+ "glibc-hurd64-gcc-14.2-tls-bug.patch"))))))))
(define-public glibc/hurd-headers
(package/inherit glibc/hurd
base-commit: fa39695bbc0c5f79838cbca55d55eebd821a8efa
--
2.48.1
Information forwarded
to
guix-patches <at> gnu.org
:
bug#77103
; Package
guix-patches
.
(Mon, 30 Jun 2025 19:03:03 GMT)
Full text and
rfc822 format available.
Message #8 received at 77103 <at> debbugs.gnu.org (full text, mbox):
I find that `guix build glibc`, with or without version spec, currently
builds either glibc or glibc/hurd *at random*.
Information forwarded
to
janneke <at> gnu.org, yelninei <at> tutamail.com, guix-patches <at> gnu.org
:
bug#77103
; Package
guix-patches
.
(Fri, 22 Aug 2025 13:50:06 GMT)
Full text and
rfc822 format available.
Message #11 received at 77103 <at> debbugs.gnu.org (full text, mbox):
Hi,
CC: Hurd team. :-)
On Tue, 18 Mar 2025 at 18:46, Jakob Kirsch via Guix-patches via <guix-patches <at> gnu.org> wrote:
> When dealing with the glibc package, you will often see the following warning:
>
> warning: ambiguous package specification `glibc'
> warning: choosing glibc <at> 2.39 from gnu/packages/base.scm:915:2
>
> This is due to the fact that Hurd glibc is exported. A simple fix is to declare it as a hidden-package.
>
> * gnu/packages/base.scm: (glibc/hurd): Hide
>
> Change-Id: I3785a2d35e1c9b4efa039dbba7f379ae052dc69a
> ---
> gnu/packages/base.scm | 23 ++++++++++++-----------
> 1 file changed, 12 insertions(+), 11 deletions(-)
>
> diff --git a/gnu/packages/base.scm b/gnu/packages/base.scm
> index 4c96ffa1a4..e8d502de8d 100644
> --- a/gnu/packages/base.scm
> +++ b/gnu/packages/base.scm
> @@ -1663,17 +1663,18 @@ (define-public which
> (license gpl3+))) ; some files are under GPLv2+
>
> (define-public glibc/hurd
> - (package/inherit glibc
> - (source
> - (origin
> - (inherit (package-source glibc))
> - (patches
> - (append (origin-patches (package-source glibc))
> - (search-patches "glibc-hurd-pthread_setcancelstate.patch"
> - "glibc-hurd64-fault.patch"
> - "glibc-hurd64-intr-msg-clobber.patch"
> - "glibc-hurd64-sgms-context.patch"
> - "glibc-hurd64-gcc-14.2-tls-bug.patch")))))))
> + (hidden-package
> + (package/inherit glibc
> + (source
> + (origin
> + (inherit (package-source glibc))
> + (patches
> + (append (origin-patches (package-source glibc))
> + (search-patches "glibc-hurd-pthread_setcancelstate.patch"
> + "glibc-hurd64-fault.patch"
> + "glibc-hurd64-intr-msg-clobber.patch"
> + "glibc-hurd64-sgms-context.patch"
> + "glibc-hurd64-gcc-14.2-tls-bug.patch"))))))))
>
> (define-public glibc/hurd-headers
> (package/inherit glibc/hurd
>
> base-commit: fa39695bbc0c5f79838cbca55d55eebd821a8efa
> --
> 2.48.1
Hurd team, what do you think about this patch?
Cheers,
simon
Information forwarded
to
guix-patches <at> gnu.org
:
bug#77103
; Package
guix-patches
.
(Sat, 23 Aug 2025 13:18:02 GMT)
Full text and
rfc822 format available.
Message #14 received at 77103 <at> debbugs.gnu.org (full text, mbox):
Hi,
Aug 22, 2025, 13:50 by zimon.toutoune <at> gmail.com:
> Hi,
>
> CC: Hurd team. :-)
>
> Hurd team, what do you think about this patch?
>
Since the core-packages-team merge glibc/hurd is an alias for glibc.
See 72dbcff9377d693ba2fe7e8563d7e40de6e19765
I don't think this is an issue currently but it might become one again when additional patches are added to glibc/hurd
> Cheers,
> simon
>
>
Reply sent
to
Simon Tournier <zimon.toutoune <at> gmail.com>
:
You have taken responsibility.
(Mon, 25 Aug 2025 10:01:03 GMT)
Full text and
rfc822 format available.
Notification sent
to
Jakob Kirsch <jakob.kirsch <at> web.de>
:
bug acknowledged by developer.
(Mon, 25 Aug 2025 10:01:03 GMT)
Full text and
rfc822 format available.
Message #19 received at 77103-done <at> debbugs.gnu.org (full text, mbox):
Hi,
On Sat, 23 Aug 2025 at 15:16, yelninei--- via Guix-patches via <guix-patches <at> gnu.org> wrote:
> I don't think this is an issue currently but it might become one again
> when additional patches are added to glibc/hurd
Well, I propose to close this patch until the issue potentially shows up
again. :-)
Once the issue appears again, maybe open a Pull Request on Codeberg
referencing this past thread.
Feel free to reopen if I’m missing something.
Cheers,
simon
This bug report was last modified 24 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.