From: Joao Pedro de Omena Simas <joao.simas@usp.br>
To: help-guix@gnu.org
Subject: glibc-2.31 corrupted substitute and build from source failure
Date: Sat, 5 Sep 2020 00:19:51 +0000 [thread overview]
Message-ID: <CANfVqTNdc1O8fh9Vt7rvSRtXrO_ZYGbAveX-Zb49ZqHHEBcb6A@mail.gmail.com> (raw)
Hello,
I was trying to install gnuradio and I was getting some errors when trying
to include glibc-2.31's headers. I checked the contents of the header files
in the /include directory inside the
/gnu/store/fa6wj5bxkj5ll1d7292a70knmyl7a0cr-glibc-2.31/ and some of them
(e.g. aio.h) and they were really corrupted. I tried running guix build
--repair glibc and the problem persisted. Then I tried it again with
--no-substitutes and I got a build failure stating:
checking for gcc... gcc
checking for suffix of object files... configure: error: in
`/tmp/guix-build-glibc-2.31.drv-0/build':
configure: error: cannot compute suffix of object files: cannot compile
See `config.log' for more details
is there anything else I can do to solve this? I also tried to install
gnuradio with --with-input=glibc=glibc@2.30, but it seems some of the
dependencies explicitely require glibc 2.31
Sincerelly,
Joao
reply other threads:[~2020-09-05 0:34 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CANfVqTNdc1O8fh9Vt7rvSRtXrO_ZYGbAveX-Zb49ZqHHEBcb6A@mail.gmail.com \
--to=joao.simas@usp.br \
--cc=help-guix@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.
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).