From: julien lepiller <julien@lepiller.eu>
To: 30756@debbugs.gnu.org
Subject: bug#30756: gcc7 doesn't find stdlib.h
Date: Fri, 09 Mar 2018 13:10:58 +0100 [thread overview]
Message-ID: <fa5ec97a90a8f52f23fed2654d08078d@lepiller.eu> (raw)
Hi,
I'm trying to build a software that requires gcc>=7.2. Unfortunately,
the process crashes and ends with:
/gnu/store/a4vwdk8r6p6l2mnffz4yaqlr1z6z6w3r-gcc-7.3.0/include/c++/cstdlib:75:15:
fatal error: stdlib.h: No such file or directory.
What I'm trying to build is called emojicode, and the current version of
my package definition can be found here:
https://framagit.org/tyreunom/guix-more/commit/ca9a77ed4b0a3ae50590f8e8abb9175f42094560
next reply other threads:[~2018-03-09 12:12 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-09 12:10 julien lepiller [this message]
2018-03-09 12:42 ` bug#30756: gcc7 doesn't find stdlib.h Ludovic Courtès
2018-05-04 9:46 ` Giel van Schijndel
2018-05-04 12:43 ` Ludovic Courtès
2018-05-04 14:30 ` Giel van Schijndel
2018-05-04 15:07 ` Giel van Schijndel
2018-05-04 15:28 ` Ludovic Courtès
2018-05-04 16:03 ` Giel van Schijndel
2018-05-04 16:41 ` Mark H Weaver
2018-05-04 17:14 ` Mark H Weaver
2018-05-04 20:39 ` Ludovic Courtès
2018-05-04 21:36 ` Mark H Weaver
2018-05-07 10:12 ` Ludovic Courtès
2018-05-07 23:32 ` Mark H Weaver
2018-05-08 13:21 ` Ludovic Courtès
2019-10-22 16:26 ` bug#30756: GCC >= 6 '-isystem' and C_INCLUDE_PATH behavior changed, breaking #include_next Carl Dong
2019-12-14 14:23 ` bug#30756: Use {C,CPLUS,OBJC}_INCLUDE_PATH instead of CPATH Mark Wielaard
2020-01-17 10:23 ` bug#30756: GCC >= 6 '-isystem' and C_INCLUDE_PATH behavior changed, breaking Reza Housseini
2020-01-19 21:16 ` Ludovic Courtès
2020-01-20 3:25 ` Maxim Cournoyer
2020-01-20 8:56 ` Ludovic Courtès
2020-01-22 3:04 ` Maxim Cournoyer
2020-01-23 20:45 ` Ludovic Courtès
2020-02-03 9:00 ` Ludovic Courtès
2020-02-03 21:03 ` Marius Bakke
2020-02-04 11:28 ` Ludovic Courtès
2020-02-06 17:49 ` Ludovic Courtès
2020-02-07 3:39 ` Maxim Cournoyer
2020-02-07 11:00 ` Ludovic Courtès
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=fa5ec97a90a8f52f23fed2654d08078d@lepiller.eu \
--to=julien@lepiller.eu \
--cc=30756@debbugs.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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.