unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Thiago Jung Bauermann <bauermann@kolabnow.com>
To: Tobias Geerinckx-Rice <me@tobias.gr>
Cc: help-guix@gnu.org
Subject: Re: Build Mesa with a different toolchain version
Date: Thu, 03 Jun 2021 02:35:11 -0300	[thread overview]
Message-ID: <8177868.9RumMkXvVa@popigai> (raw)
In-Reply-To: <87sg20zfhu.fsf@nckx>

Em quarta-feira, 2 de junho de 2021, às 08:13:17 -03, Tobias Geerinckx-Rice 
escreveu:
> Two notes after a calming walk in the woods:

Always a good idea!

> Tobias Geerinckx-Rice 写道:
> 
> > no package has a ‘gcc-toolchain’ input.
> 
> Not true: 2 do.  I meant that ‘the toolchain’ used to build
> everything…
> 
> > It is not used internally by Guix.
> 
> …is not the "gcc-toolchain" package as such.

Thanks for the clarification.

> > (package (inherit gcc->gcc-10 mesa) …)
> 
> Just turn it around:
> 
>   (define-public mesa/gcc-10
>     (package
>       (inherit mesa)
>       (native-inputs
>         `(("gcc" ,gcc-10)
>           ,@(package-native-inputs mesa)))))

This worked (except for the mixed-toolchains issue):

(define-public mesa-10
  (package
    (inherit (package-with-c-toolchain mesa
                                       `(("toolchain" ,gcc-toolchain-10))))
    (name "mesa-10")))

-- 
Thanks,
Thiago




  reply	other threads:[~2021-06-03  5:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-02  0:46 Build Mesa with a different toolchain version Thiago Jung Bauermann
2021-06-02  1:53 ` Thiago Jung Bauermann
2021-06-02  9:44   ` Tobias Geerinckx-Rice
2021-06-02  9:22 ` Efraim Flashner
2021-06-03  5:14   ` Thiago Jung Bauermann
2021-06-02  9:42 ` Tobias Geerinckx-Rice
2021-06-02 11:13   ` Tobias Geerinckx-Rice
2021-06-03  5:35     ` Thiago Jung Bauermann [this message]
2021-06-03  5:17   ` Thiago Jung Bauermann

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=8177868.9RumMkXvVa@popigai \
    --to=bauermann@kolabnow.com \
    --cc=help-guix@gnu.org \
    --cc=me@tobias.gr \
    /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).