From: "Ludovic Courtès" <ludo@gnu.org>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: reza.housseini@gmx.ch, 30756@debbugs.gnu.org,
Reza Housseini <reza.housseini@gmail.com>
Subject: bug#30756: GCC >= 6 '-isystem' and C_INCLUDE_PATH behavior changed, breaking
Date: Thu, 23 Jan 2020 21:45:54 +0100 [thread overview]
Message-ID: <87wo9hnbp9.fsf@gnu.org> (raw)
In-Reply-To: <878sm0kx8b.fsf@gmail.com> (Maxim Cournoyer's message of "Tue, 21 Jan 2020 22:04:36 -0500")
Hello!
Thanks for investigating.
Maxim Cournoyer <maxim.cournoyer@gmail.com> skribis:
> It'd be very cool to embed arbitrary logic such as sorting, filtering,
> or whatever else we need doing directly in a search path specification
> :-). Do you thing this could be done? Perhaps Gexps could be useful
> for this?
No, that sounds pretty unreasonable to me. :-)
However, I’m sure we should be able to sort things appropriately in
guix/build-system/gnu.scm and/or in ‘%final-inputs’, no?
‘%final-inputs’ order actually looks good:
--8<---------------cut here---------------start------------->8---
scheme@(gnu packages commencement)> (map car %final-inputs)
$2 = ("tar" "gzip" "bzip2" "xz" "file" "diffutils" "patch" "findutils" "gawk" "sed" "grep" "coreutils" "make" "bash" "ld-wrapper" "binutils" "gcc" "libc" "libc:static" "locales")
--8<---------------cut here---------------end--------------->8---
But then it breaks when we add everything:
--8<---------------cut here---------------start------------->8---
scheme@(guile-user)> (map car (bag-transitive-inputs (package->bag coreutils)))
$5 = ("source" "perl" "tar" "gzip" "bzip2" "xz" "file" "diffutils" "patch" "findutils" "gawk" "sed" "grep" "coreutils" "make" "bash" "ld-wrapper" "binutils" "gcc" "libc" "libc:static" "locales" "acl" "gmp" "libcap" "kernel-headers")
--8<---------------cut here---------------end--------------->8---
Here acl, gmp, and libcap should be before libc and all
(‘bag-transitive-inputs’ is used by ‘bag->derivation’.)
So I think we should arrange to have the right order in
‘bag->derivation’.
WDYT?
Ludo’.
next prev parent reply other threads:[~2020-01-23 20:47 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-09 12:10 bug#30756: gcc7 doesn't find stdlib.h julien lepiller
2018-03-09 12:42 ` 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 [this message]
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=87wo9hnbp9.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=30756@debbugs.gnu.org \
--cc=maxim.cournoyer@gmail.com \
--cc=reza.housseini@gmail.com \
--cc=reza.housseini@gmx.ch \
/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.