unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Anonymous_ <anonymousunderscore@riseup.net>
To: guix-devel@gnu.org
Subject: Possible error on glibc package specification
Date: Fri, 11 Dec 2020 06:34:12 -0300	[thread overview]
Message-ID: <effa2923-4537-0cd7-2dca-50bf34567ab8@riseup.net> (raw)


[-- Attachment #1.1.1: Type: text/plain, Size: 1065 bytes --]

I that even after installing glibc-2.31 gcc still cant build static 
binaries, I just used -static flag, which shows that libc.a is not 
present, Im just new in Guix then I do not know how to create packages 
or patches, but I believe the problem is around this part of package 
spec 
https://git.savannah.gnu.org/cgit/guix.git/tree/gnu/packages/base.scm#n851

I dont know Scheme at all, but those line around line 851 seems to be 
moving or not moving the statically linked correct, will probably can 
help when I learn how to debug package specifications, but Im sending 
this email because I think its worth to someone take a look. Since some 
applications relies on gcc being able to produce static binaries, 
another improvement can be to allow gcc produce static-pie by default.. 
Let me know what you all think.

I will probably get on IRC in a few days, I just dont get online because 
I had not time to configure Tor SASL authentication on freenode... For 
now i just I want to say that im enjoyng to use Guix :)

Regards, Anonymous_


[-- Attachment #1.1.2: OpenPGP_0x8E28A44555230AEC.asc --]
[-- Type: application/pgp-keys, Size: 3191 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]

             reply	other threads:[~2020-12-11 12:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-11  9:34 Anonymous_ [this message]
2020-12-11 12:50 ` Possible error on glibc package specification Tobias Geerinckx-Rice

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=effa2923-4537-0cd7-2dca-50bf34567ab8@riseup.net \
    --to=anonymousunderscore@riseup.net \
    --cc=guix-devel@gnu.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.
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).