all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Formbi <formbi@protonmail.com>
Cc: 40164@debbugs.gnu.org
Subject: [bug#40164] Fix for libgccjit
Date: Sun, 22 Mar 2020 21:54:06 +0100	[thread overview]
Message-ID: <87lfnst8k1.fsf@gnu.org> (raw)
In-Reply-To: <zQode-EomoU8GYz0NVEC1E-dBhMwLCRtt-LHk1FaBdeeAzlTsYdHrqvKiajgG5_9W4ht97afq-I5F4uac5cH7_zzY-pvcyJwe-q6jwCEPaE=@protonmail.com> (formbi@protonmail.com's message of "Sat, 21 Mar 2020 22:56:18 +0000")

Hi,

(+Cc bug.)

Formbi <formbi@protonmail.com> skribis:

>> I think this has no effect because this ‘native-search-paths’ is already
>> inherited from ‘gcc-9’, which ‘libgccjit’ inherits from.
>
> Nope, it does have an effect. I added "lib/gcc" to the original paths (and that was the needed thing).

In that case, could you (1) arrange to write the search path in a way
that reuses (package-native-search-paths gcc-9), and (2) add a comment
explaining why “lib/gcc” is needed (it looks unusual)?

Thanks in advance,
Ludo’.

  parent reply	other threads:[~2020-03-22 20:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-21 13:13 [bug#40164] Fix for libgccjit Formbi via Guix-patches via
2020-03-21 13:18 ` [bug#40164] information Formbi via Guix-patches via
2020-03-21 13:21 ` [bug#40164] a small correction Formbi via Guix-patches via
2020-03-21 14:48 ` [bug#40164] Fix for libgccjit Mathieu Othacehe
2020-03-21 22:32 ` Ludovic Courtès
     [not found]   ` <zQode-EomoU8GYz0NVEC1E-dBhMwLCRtt-LHk1FaBdeeAzlTsYdHrqvKiajgG5_9W4ht97afq-I5F4uac5cH7_zzY-pvcyJwe-q6jwCEPaE=@protonmail.com>
2020-03-22 20:54     ` Ludovic Courtès [this message]
2021-07-14 12:40       ` Maxim Cournoyer
2021-07-14 16:50         ` Maxim Cournoyer
2020-03-21 23:12 ` Formbi via Guix-patches via

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=87lfnst8k1.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=40164@debbugs.gnu.org \
    --cc=formbi@protonmail.com \
    /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.