unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Emmanuel Medernach <Emmanuel.Medernach@iphc.cnrs.fr>
To: zimoun <zimon.toutoune@gmail.com>, Tobias Geerinckx-Rice <me@tobias.gr>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: Error using gcc with trivial-build-system
Date: Wed, 9 Nov 2022 08:18:17 +0100	[thread overview]
Message-ID: <16eb0d8c-6962-6003-247c-82cd8d4e847d@iphc.cnrs.fr> (raw)
In-Reply-To: <86tu39tadi.fsf@gmail.com>


Le 08/11/2022 à 22:16, zimoun a écrit :
> Hi,
>
> On Tue, 08 Nov 2022 at 15:48, Emmanuel Medernach <Emmanuel.Medernach@iphc.cnrs.fr> wrote:
>
>> About customizing I have another question, at the end of the build I
>> have messages like:
>>
>> warning: collision encountered: ...
> This collision is about?  What do you as inputs for your package
> definition?

It is about header files or binaries with the same name coming from my 
local package sources, I want to be sure either to only copy the one 
needed to the profile or not to copy it if it is only helper binaries.


>
>> I would prefer to manage myself what is copied to the profile or what is
>> not and where, is it possible ?
> You mean skip the automatic references, right?
>
I would like to copy only what has been compiled/installed in some 
directories and not other for instance.

Cheers,

Emmanuel

> Cheers,
> simon


      reply	other threads:[~2022-11-09  7:19 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
2022-11-08 21:16     ` zimoun
2022-11-09  7:18       ` Emmanuel Medernach [this message]

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=16eb0d8c-6962-6003-247c-82cd8d4e847d@iphc.cnrs.fr \
    --to=emmanuel.medernach@iphc.cnrs.fr \
    --cc=help-guix@gnu.org \
    --cc=me@tobias.gr \
    --cc=zimon.toutoune@gmail.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.
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).