From: Emmanuel Medernach <Emmanuel.Medernach@iphc.cnrs.fr>
To: Tobias Geerinckx-Rice <me@tobias.gr>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: Error using gcc with trivial-build-system
Date: Tue, 8 Nov 2022 15:48:34 +0100 [thread overview]
Message-ID: <4ca9d324-adc7-8553-ea08-c158cc1941d8@iphc.cnrs.fr> (raw)
In-Reply-To: <365d37dc93ae35ff965c7c4736b8a59d@tobias.gr>
Le 08/11/2022 à 15:10, Tobias Geerinckx-Rice a écrit :
> Hi Emmanuel!
>
> On 2022-11-08 11:23, Emmanuel Medernach wrote:
>> I have a local package with a compile script that
>> I need to add to our local GUIX packages.
>
> (Nitpick: Guix isn't a acronym. Never has been.)
>
>> I tried to use trivial-build-system with
>> gcc-toolchain input, all works well when I compile
>> it manually in a 'guix shell'
>
> Because ‘guix shell’ sets up a proper profile; quite unlike the
> trivial-build-system.
>
> Using trivial-build-system here *is* the bug. It's not a starter kit
> for building better things; it's for trivial packages that don't need
> building.
>
> Rather than waste your time fighting that fact, use the
> gnu-build-system. It is that starter kit.
>
> If your tarball doesn't provide some standard GNU things like
> ./configure or ‘make check’, that's quite common. You can simply
> (delete 'configure), set #:tests? #f, etc.
>
Thanks for your help, I will use the gnu-build-system and customize it
as you suggest.
About customizing I have another question, at the end of the build I
have messages like:
warning: collision encountered: ...
I would prefer to manage myself what is copied to the profile or what is
not and where, is it possible ?
Emmanuel
> Happy building,
>
> T G-R
>
> Sent from a Web browser. Excuse or enjoy my brevity.
next prev parent reply other threads:[~2022-11-08 14:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-08 10:23 Error using gcc with trivial-build-system Emmanuel Medernach
2022-11-08 10:45 ` Sergiu Ivanov
2022-11-08 10:58 ` Emmanuel Medernach
2022-11-08 11:39 ` Wojtek Kosior via
2022-11-08 13:01 ` Emmanuel Medernach
2022-11-08 14:10 ` Tobias Geerinckx-Rice
2022-11-08 14:48 ` Emmanuel Medernach [this message]
2022-11-08 21:16 ` zimoun
2022-11-09 7:18 ` Emmanuel Medernach
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=4ca9d324-adc7-8553-ea08-c158cc1941d8@iphc.cnrs.fr \
--to=emmanuel.medernach@iphc.cnrs.fr \
--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).